Workflow Spec Command
Manually enter Stage A (Spec + Meta-Validation) workflow.
Subcommands
create
Start Stage A spec creation process.
Process:
- Research existing docs/specs/code
- Create initial spec document
- Run meta-testing automatically
- Iterate based on results
- Ready for finalize
Output location:
- If
openspec/exists:openspec/changes/[feature]/proposal.md - Otherwise:
docs/specs/[feature].md
validate
Run meta-tests on current spec (if in Stage A).
Meta-testing:
- Auto-generated PoC tests
- Manual validation questions
- Complexity checks
- Feasibility validation
finalize
Finalize current spec and transition to Stage B.
Process:
- Verify meta-tests passed
- Create final spec document (design.md)
- Transition to Stage B for implementation
- Or prompt: "Ready to implement (Stage B)?"
Example Usage
User: /workflow:create-workflow-spec create "Payment processing"
→ Starting Stage A: Spec Creation
Research phase:
- Reading existing code...
- Checking for related specs...
Creating initial spec:
openspec/changes/payment-processing/proposal.md
[Spec draft created]
Running meta-tests:
✓ Auto PoC: Stripe API connection
✓ Auto PoC: Test payment creation
? Manual: Webhook security?
? Manual: Error handling strategy?
[Iterate based on feedback]
User: /workflow:create-workflow-spec finalize
→ Finalizing spec:
openspec/changes/payment-processing/design.md
✅ Spec finalized
Ready to implement (Stage B)? [Y/n]
See block-a-spec-validation skill for full workflow details.