Draft or update functional product contracts in spec.md from approved ideas.
npx skills add https://github.com/bdemarzo/ai-workflows --skill spec-create-bdemarzo
Please help me install this Agent Skill. Skill: spec-create Source: https://github.com/bdemarzo/ai-workflows/tree/main/skills/spec-create Command: npx skills add https://github.com/bdemarzo/ai-workflows --skill spec-create-bdemarzo
It helps you convert an approved idea into a precise, user-visible functional product contract so planning and engineering can proceed with clarity instead of ambiguity.
Use the spec-create skill to draft or update ./docs/workflows/{slug}/spec.md from an approved idea so the result is ready for spec-review.
High-intent search queries and answers about installing and using this skill.
To write a functional product spec from an approved idea, draft a user-visible product contract in spec.md that defines correctness and acceptance criteria while omitting implementation mechanics. This creates a self-contained functional contract ready for planning.
A functional contract defines user-visible product requirements and acceptance behavior, whereas an implementation plan details sequencing and technical mechanics. Separating the spec from the plan ensures engineering proceeds with clarity on expected outcomes rather than build steps.
To document enhancement deltas in an existing spec, update the functional contract to capture Current, Changed, and Preserved behaviors. You must define clear acceptance criteria for both the enhancement delta and potential regressions to maintain source consistency.
Structure a workflow dossier spec by creating or updating ./docs/workflows/{slug}/spec.md in place. Enforce the exact H1 format and keep the spec self-contained for planning by deriving the slug and preserving dossier slug relationships.
Yes, you can update spec.md to incorporate accepted spec-review outcomes. Refining the existing contract preserves dossier slug relationships and contract-source consistency while ensuring the functional product contract remains accurate for the Product Manager operator.
You should exclude implementation mechanics from a product spec whenever drafting or updating the functional contract. The spec must contain only user-visible correctness and acceptance criteria, intentionally omitting technical sequencing to separate requirements from the plan.
taichuyDefine API contracts as the single source of truth for oRPC layers.
pradeepmouliGenerate spec.md files with user stories and acceptance criteria from natural language.
roycolumbia-codeGenerate AI-SPEC.md design contracts and orchestrate workflow tasks.
rhussGenerate formal executable specifications from clear requirements via spec-kit.
