spec-writer
Writes a task's spec — the one document an AI coder (Codex, a coder subagent) builds from without asking — then has it checked by a fresh agent that reads it as that coder. Use whenever a task's code is about to be handed to another executor and its scope is agreed - «напиши спеку», «спека задачи», «оформи в спеку», «write the spec», «spec for the coder», after a scope approval and before any code is delegated; also when a coder stopped on a gap and the spec needs a fix. Not for a design doc people read to decide (a plan, a proposal, a schema diff for review), not for code the session writes itself right now with nothing left to decide.
Original · translation did not pass checksTarget: Office & team collaboration. Automatically collected · unverified.
Use with Claude Code
A guide for this combination is not available yet, and compatibility has not been verified.
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
Choose an AI tool with documented instructions, or save the resource and request a guide after the page loads.
Read the author’s documentation ↗