write-tech-spec
write-tech-spec
Translate approved product intent into an implementation plan that fits the existing codebase. This is a local shared skill; wrappers may provide exact inputs and output paths that take precedence.
Decide and research
Use it when work spans modules, has architectural tradeoffs, needs a migration or rollout plan, or benefits from review before implementation. Skip it for straightforward fixes, small refactors, and narrow UI changes with no technical ambiguity. Prefer a product spec first; an end-to-end prototype can be a better precedent when the implementation is still uncertain.
Before drafting, read the product spec when present and inspect the actual repository. Identify current behavior, relevant files/types/entry points, data or control flow, ownership boundaries, dependencies, risks, and validation constraints. Do not infer architecture that can be read from code.