Why
SpecFact already has a generate test-prompt workflow for creating tests using IDE copilots. Extending this to generate CLI behavior scenarios means every new feature ships with end-user validation from day one — without developers manually writing YAML. This makes the "patterns + anti-patterns as first-class artifacts" vision operationally sustainable.
What Changes
- NEW: Prompt template in
resources/prompts/ generating scenario YAML, anti-pattern catalog, and Markdown acceptance tests
- EXTEND:
specfact generate test-prompt workflow to detect CLI commands and offer scenario template
- EXTEND: OpenSpec convention requiring scenario files for CLI command changes
- EXTEND: Documentation with copilot-driven scenario authoring workflow
Acceptance Criteria
Blocked by: #279 (cli-val-01). Soft dependency: #283 (cli-val-05) for enforcement.
OpenSpec Change Proposal: cli-val-06-copilot-test-generation
Why
SpecFact already has a
generate test-promptworkflow for creating tests using IDE copilots. Extending this to generate CLI behavior scenarios means every new feature ships with end-user validation from day one — without developers manually writing YAML. This makes the "patterns + anti-patterns as first-class artifacts" vision operationally sustainable.What Changes
resources/prompts/generating scenario YAML, anti-pattern catalog, and Markdown acceptance testsspecfact generate test-promptworkflow to detect CLI commands and offer scenario templateAcceptance Criteria
generate test-promptdetects CLI commands and offers scenario templateBlocked by: #279 (cli-val-01). Soft dependency: #283 (cli-val-05) for enforcement.
OpenSpec Change Proposal: cli-val-06-copilot-test-generation