writing-plans

To convert a written specification into an executable implementation plan, use this skill to enforce plan templates, validate frontmatter, and generate deterministic, step-by-step tasks aligned with TDD practices.

Yes, you can automatically generate documentation update tasks and integration plans. The skill structures staged design and testing tasks across sprint cycles to ensure mandatory documentation updates are included.

You create TDD-ready task plans for large software epics by processing written specifications of varying sizes. The skill breaks down large features into deterministic, bite-sized, step-by-step planning tasks.

The best way to structure staged design and testing tasks is by applying deterministic task granularity and plan-template enforcement. This approach transforms specifications into structured, executable implementation plans.

Yes, writing-plans operates without external dependencies or plugins. It functions independently to fulfill frontmatter validation and plan-template enforcement directly from your written specification.

You should avoid automated task-planning tools if your project lacks a written specification or does not require staged design, testing, and documentation tasks across sprint cycles.