菜单
Run full feature-spec→feature-requirements→feature-validation→feature-tests→slice-test-red pipeline for a feature folder
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | run-spec-workflow |
| description | Run full feature-spec→feature-requirements→feature-validation→feature-tests→slice-test-red pipeline for a feature folder |
Thin orchestrator. Runs the spec chain from /feature-spec through to
/slice-test-red in strict order for a given slice, producing all five
markdown spec files and the red C# outside-in test class.
The /to-prd step is not run automatically — a prd.md must already
exist in the slice folder before this pipeline starts. If it does not, stop
and tell the user to run /to-prd first.
/run-spec-workflow with a slice name or folder argument.<slice>".Do not trigger on requests to run a single step. Those are invoked directly
(/feature-spec, /slice-test-red, etc.).
Before starting:
specs/features/<aggregate>/<NNNN>_<slice>/prd.md exists.
If absent, stop: "prd.md is missing — run /to-prd first, then re-run
/run-spec-workflow."CLAUDE.md and agent_docs/spec_workflow.md to confirm the slice
path and aggregate name.| Step | Skill | Produces |
|---|---|---|
| 1 | /feature-spec | plan.md |
| 2 | /feature-requirements | requirements.md |
| 3 | /feature-validation | validation.md |
| 4 | /feature-tests | tests.md |
| 5 | /slice-test-red | <Slice>OutsideInTests.cs (verified RED) |
Each step must complete successfully before the next begins. If a step fails or reports a problem, halt the pipeline and surface the issue to the user — do not skip ahead.
After a successful run, the slice folder contains:
specs/features/<aggregate>/<NNNN>_<slice>/
├── prd.md (pre-existing)
├── plan.md (step 1)
├── requirements.md (step 2)
├── validation.md (step 3)
├── tests.md (step 4)
└── implement.md (written by step 5)
tests/...IntegrationTests/Features/<Aggregate>/<NNNN>_<slice>/
└── <Slice>OutsideInTests.cs (step 5 — verified RED)
The final artifact is the C# <Slice>OutsideInTests.cs class, which is the
RED acceptance gate. Implementation begins after this pipeline completes.
Report to the user:
specs/features/<aggregate>/<NNNN>_<slice>/.<Slice>OutsideInTests.cs is written and verified RED (include the failure
mode: build error / 404 / assertion).implement.md has been written to the slice folder.implement.md into
a new session to start.prd.md is absent.dotnet build or dotnet test directly (that is delegated to
/slice-test-red in step 5).specs/roadmap.md (owned by /to-prd).This skill should be used when the user wants to generate requirements.md for a slice. Trigger when the user invokes /feature-requirements, says "formalize the requirements", or asks for the F/N traceability after plan.md exists. Reads prd.md and plan.md. Produces requirements.md only — formal functional (F) and non-functional (N) requirements with IDs that the validation and tests phases trace back to.
This skill should be used when the user wants to generate tests.md for a slice. Trigger when the user invokes /feature-tests, says "write outside-in test spec", or asks to describe the slice-level integration test in markdown form before any code is written. Use only after prd.md, plan.md, requirements.md, validation.md exist. Produces markdown specification only; does not write C# code.
This skill should be used when the user wants to generate validation.md for a slice. Trigger when the user invokes /feature-validation, says "write the validation checklist", or asks for manual scenarios after requirements.md exists. Reads prd.md, plan.md, requirements.md. Produces validation.md with manual scenarios and code review checklist.
This skill should be used when the user wants to generate the executable C# outside-in test for a slice from its tests.md specification. Trigger when the user invokes /slice-test-red, says "generate the red test", "write the outside-in C# test", or asks to translate tests.md into a runnable xUnit test class. Use only after tests.md exists. Reads tests.md plus architectural context, writes <Slice>OutsideInTests.cs, runs dotnet test, and verifies the test is RED.
This skill should be used when the user references slice spec work, mentions a slice folder (specs/features/...), asks "what's next" on a slice, or invokes the spec chain. It auto-loads the architectural context, inspects the current slice folder, determines which stage the slice is in, and advises which command to run next. This skill advises only; it does not write spec files itself.
Structure Flutter apps using layered architecture (UI / Logic / Data) with feature-first file organization. Use when creating new features, designing the project folder structure, adding repositories, services, view models (or cubits/providers/notifiers), wiring dependency injection, or deciding which layer owns a piece of logic. State management agnostic.