25 lines
981 B
Markdown
25 lines
981 B
Markdown
---
|
|
name: spec-pipeline
|
|
description: "Executes the full dev-to-docs pipeline: Developer -> Tester -> Writer."
|
|
---
|
|
|
|
## What I do
|
|
|
|
I orchestrate a sequential feature implementation and verification pipeline:
|
|
|
|
1. **Architect**: Explores codebase, asks clarifying questions, and drafts the spec. \*_Waits for user approval before handoff._
|
|
2. **Developer**: Implements the feature based on the spec.
|
|
3. **Tester**: Runs full unit test suites; repairs failures if found.
|
|
4. **Writer**: Updates README and API docs based on verified code.
|
|
|
|
## Execution Rules
|
|
|
|
- **Architect Gate**: Stop after Phase 3 and wait for user approval on the spec before calling `@developer`.
|
|
- Stop and ask the user for clarification if any step fails or is ambiguous.
|
|
- Use `@` mentions to trigger subagents sequentially.
|
|
- Pass context from each completed stage to the next stage
|
|
|
|
## When to use me
|
|
|
|
Invoke me when you are ready to begin a new feature/fix or when the Architect has finished a specification.
|