writing-plans

To generate an implementation plan from a feature spec, use this skill to translate specifications into actionable step-by-step engineering plans. It maps exact file paths and decomposes multi-step feature work into bite-sized TDD execution steps with expected outcomes.

Task decomposition for test-driven development planning breaks down feature specs into atomic actions spanning two to five minutes. It enforces bite-sized TDD execution steps by defining explicit failing tests, expected outcomes, implementation snippets, and verification commands.

You break down multi-step feature work by mapping exact file paths to be created or modified, which decides task boundaries. This file-structure driven approach produces deterministic plan documents containing minimal code blocks and run commands with no placeholders.

Yes, implementation planning works for independent subsystems by checking if the spec spans them and recommending splits into separate plans. This ensures each plan produces working, testable software on its own with clear boundaries for file edits and tests.

The best way to coordinate file edits, tests, and documentation before coding is generating a buildable TDD-oriented plan. It requires a strict plan header format and a fully fill-in-complete workflow, ensuring the agent coordinates changes with clear boundaries.

You need an agentic workflow for developer documentation and test planning when starting from a spec and code changes have not started yet. It applies to multi-step feature work where the agent must coordinate file edits and execution without wasting time on guesswork.