product-specification

Create shaped, time-boxed engineering specifications with boundaries and risk logs.

37|5|Updated Nov 18, 2025

Search Tags:#specification #user-stories #acceptance-criteria #backbone

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill product-specification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-specification
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/product-specification
Command: npx skills add https://github.com/BellaBe/lean-os --skill product-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert prioritized features into shaped pitches, with boundaries and risks.

Core Features & Use Cases

Shape the Work: fixed time, scope boundaries
User Story Map: backbone and walking skeleton
Definition of Ready: acceptance criteria

Quick Start

Provide user stories; returns shaped pitch.

Frequently Asked Questions about product-specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a shaped specification for engineering handoff?▼

A shaped specification is a bounded, time-boxed pitch that defines problem, solution, core flow, and risks for engineers. This Skill converts prioritized features into shaped specs by applying fixed appetite, explicit scope boundaries, and rabbit hole identification—turning requirements into engineering-ready documents ready for sprint or Shape Up workflows.

What should I include in acceptance criteria for user stories?▼

Acceptance criteria define what done looks like for each user story. This Skill structures criteria within the shaped pitch framework, mapping user story backbones to acceptance conditions, ensuring engineers know boundaries and edge cases before building.

How do I identify and document risks in a specification?▼

Risk logging in shaped specs captures rabbit holes, no-gos, and technical unknowns before handoff. This Skill guides you to document risks explicitly in the specification template, preventing scope creep and helping engineers anticipate blockers during implementation.

Can I use shaped specifications in fixed-time, variable-scope projects?▼

Yes. Shaped specifications apply directly to fixed-time, variable-scope workflows by setting a hard appetite ceiling and adjusting scope within that boundary. This Skill structures specs to enforce time-boxing while keeping scope flexible, aligning with both Shape Up and sprint-based planning.

What is a user story backbone and why does it matter?▼

A user story backbone is a walking skeleton—the core user journey stripped to essentials. This Skill uses the backbone to map acceptance criteria and define scope boundaries, ensuring stakeholders and engineers agree on the minimum viable flow before detailed implementation.

How do I communicate appetite and scope boundaries to stakeholders?▼

Shaped pitches communicate appetite (time/resources budgeted) and scope boundaries (what's in, what's out) in a structured format. This Skill generates Problem, Current State, Evidence, Solution, and Rabbit Hole sections that make trade-offs and constraints visible to all parties before engineering starts.