| name | write-tech-spec |
| description | Draft a technical implementation spec from product requirements and codebase evidence. |
Write Tech Spec
Use when the user asks for a technical spec, implementation plan, architecture note, or product-spec-to-engineering breakdown.
Workflow
- Read the product requirements or issue context.
- Scout the relevant code paths, APIs, tests, and constraints.
- Propose the smallest architecture that satisfies the requirements.
- Identify data model, API, UI, migration, compatibility, and security implications.
- Define implementation phases and verification gates.
Rules
- Ground the spec in existing code evidence; cite paths where possible.
- Prefer incremental, reversible changes.
- Do not over-design speculative extension points.
- Surface open questions and risky trade-offs explicitly.
Output
# Technical Spec: <title>
## Context
## Existing Code Evidence
## Proposed Design
## Implementation Plan
## Testing / Verification
## Migration / Compatibility
## Security / Privacy
## Risks
## Open Questions