planning-patterns_skill

Overview

This skill generates executable, TDD-first implementation plans broken into single-action steps so a developer with zero context can complete work without asking questions. It enforces a strict header, context references, validation levels, and a save-and-index workflow so plans are discoverable and actionable. Use cc10x-router for all development and task creation steps.

How this skill works

The skill produces a complete plan document with an exact file-by-file task list, one-action steps (2–5 minutes each), test code snippets, run commands, expected outputs, and commit instructions. It includes context references (file:line), risk assessment, testing matrix, ADR guidance, and mandatory save/update steps that write the plan to docs/plans and update in-memory context files so follow-up execution tasks can be created.

When to use it

• Creating a single-pass implementation plan for a new feature or bug fix
• Handing off work to engineers unfamiliar with the codebase
• When you must enforce TDD, frequent commits, and small-step progress
• Producing auditable plans that must be saved and indexed for later execution
• Preparing multi-phase work that needs explicit risk and validation mapping

Best practices

• Write every step as a specific action (no vague instructions) and keep steps 2–5 minutes each
• Begin each plan with the required header referencing design docs and goal/architecture/tech stack
• Include exact file paths and line references in Context References so nothing is assumed
• Attach explicit test commands, expected outputs, and validation level per task
• Save the plan to docs/plans and update the activeContext and progress memory files immediately
• Use cc10x-router for creating execution tasks and task dependencies after saving the plan

Example use cases

• Add a new API endpoint: full plan with tests, implementation, lint/tsc checks, and integration steps
• Fix user registration validation: failing-test-first steps, minimal implementation, edge-case tests, and commit history
• Migrate a utility module: ADR decision, phased tasks, risk table, and integration tests
• Introduce an auth flow: high-risk plan with validation matrix and manual walkthrough steps
• Create a UI component: component tests, rendering checks, and accessibility validation