task-spec-writer

To turn vague project tasks into structured briefs, provide a task description and context to generate a canonical task brief with explicit goals, scope, and definition of done. This ensures work items are operationalized for reliable execution across product and engineering work.

A canonical task brief is a single, comprehensive description that captures intent, goals, scope, definition of done, and verification. It transforms ambiguous work items into actionable plans to enable reliable project execution and tracking.

You link RFC and ADR updates by attaching or referencing architecture decision records directly within the task brief when scope changes occur. This ensures durable architecture decisions are documented alongside the work items.

Yes, you can persist project decisions and follow-up notes for future sessions by saving durable decisions with memory.save. This retains context and preferences so ongoing work maintains continuity across different intervals.

The best way to write definition of done is to generate a comprehensive task brief that explicitly defines goals, scope, and verification criteria. This structured approach prevents ambiguity and provides clear completion targets for engineering work.

No, you do not need existing RFC or ADR documents to generate a task brief, but the skill can link or create them if architecture changes are required. You only need to provide a basic task description and relevant context.