Spec Writer Skill

Intent

Use this skill to turn a rough repo change, feature idea, cleanup effort, or migration into a numbered spec folder with practical planning documents. The goal is to create a working spec package that another engineer can pick up and execute without guessing what the work means.

Use When

• The user wants a new spec for a repo change, feature, refactor, migration, or workflow
• A project needs structured requirements.md, plan.md, and tasks.md documents
• The repo already uses numbered spec folders and new work should follow that pattern
• The request is large enough that ad hoc notes would be too loose

Do Not Use When

• The change is tiny and does not need formal planning
• The repo has no spec workflow and the user only wants direct implementation
• The user wants a README, assessment, or changelog instead of an execution spec
• The available context is too thin to produce honest requirements and next steps