Convert approved briefs into testable acceptance scenarios in spec.md files.
npx skills add https://github.com/bernajaber/pi-product-system --skill specify-bernajaber
Please help me install this Agent Skill. Skill: specify Source: https://github.com/bernajaber/pi-product-system/tree/main/skills/specify Command: npx skills add https://github.com/bernajaber/pi-product-system --skill specify-bernajaber
Converts an approved Gate 1 brief into a precise, internal specification of acceptance scenarios so downstream agents (plan, build, test) have clear, testable requirements and do not rely on assumptions.
Convert the approved brief at .pi/specs/<feature>/brief.md into .pi/specs/<feature>/spec.md containing clear, independently testable acceptance scenarios and update the workflow state to proceed to planning.
High-intent search queries and answers about installing and using this skill.
To convert a product brief into testable acceptance scenarios, you apply this Skill to an approved brief.md file, generating a spec.md document with structured, independently testable user-behavior scenarios.
The best way to structure acceptance scenarios for automated testing is to define user-focused behaviors that include empty states, error cases, and boundary conditions, ensuring each scenario is independently testable.
You manage workflow state transitions by updating the workflow-state.json file, setting the currentPhase to plan after generating the internal specification from the approved brief.
You need to generate acceptance scenarios from a brief after discovery approves it for a new feature, ensuring downstream build and test pipelines have clear requirements rather than relying on assumptions.
Yes, this specification process requires a Gate 1 approved brief located at .pi/specs/<feature>/brief.md to correctly produce the internal spec.md file for downstream planning.
Acceptance scenarios should include empty state, error cases, and boundary conditions alongside the primary user-focused behaviors to ensure comprehensive test coverage for the feature.
bernajaberConduct deep conversational interviews to extract product requirements and produce a brief document.
oxhagolliDecompose approved plans into independent parallel work streams for subagents.
aaronbassettGenerates a Markdown-ready constitution input for /speckit.constitution from project characteristics.
Ocean326Create PRDs, FRs, NFRs, epics, and user stories from a project brief.
