writing-plans

To create an implementation plan, this skill generates structured Markdown documents at docs/plans/YYYY-MM-DD-<feature-name>.md. It produces end-to-end task definitions covering scope, artifacts, tests, and commit strategy for incremental execution in zero-context environments.

The best way to document multi-step tasks is using structured Markdown plans with frontmatter metadata. This skill generates zero-context briefs detailing files touched, tests to write, and execution steps, ensuring team alignment and accelerated delivery.

You generate zero-context briefs by following a task-structure format that defines each execution step. This skill produces Markdown plans containing testable steps, artifact definitions, and commit strategies so engineers can execute tasks without additional context.

Yes, structured task planning works for software projects requiring testable steps. This skill creates comprehensive implementation plans that document scope, define multi-step tasks, specify tests to write, and outline commit strategies in a Markdown format.

Software implementation planning requires a frontmatter with name and description fields. The skill outputs a Markdown plan file at docs/plans/YYYY-MM-DD-<feature-name>.md, following a structured task-organization format for incremental execution tracking.