implementation-plan

Generate codebase-aware technical implementation plans from approved feature specifications.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tsmes/conaro --skill implementation-plan-tsmes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/tsmes/conaro/tree/main/.claude/skills/implementation-plan
Command: npx skills add https://github.com/tsmes/conaro --skill implementation-plan-tsmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved feature specification into an actionable build plan is error-prone: developers guess at architecture, miss requirements, or create tasks that cannot be committed independently. This Skill produces a structured, codebase-aware implementation plan with ordered tasks, file-level detail, and full requirements traceability. ## Core Features & Use Cases - Spec-Driven Planning: Reads an approved specification from .claude/plans/ and refuses to proceed if the spec is missing, incomplete, or contradictory, flagging issues instead of guessing. - Parallel Codebase Investigation: Uses sub-agents to inspect interfaces, types, test patterns, and module boundaries before making technical decisions. - Ordered Task Breakdown: Produces independently committable tasks with files to change, approach notes, verification steps, and dependencies, plus a mandatory requirements coverage table. - Use Case: After approving a spec for a new application review workflow, run this Skill to get a plan saved to .claude/plans/review-workflow-plan.md that a developer or agent can implement task by task. ## Quick Start Create an implementation plan from the approved feature spec in .claude/plans and save it as a plan file.

Frequently Asked Questions about implementation-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an implementation plan from a feature specification?▼

Place the approved spec in .claude/plans/ and invoke the implementation-plan skill. It reads the spec, investigates the affected code areas with sub-agents, confirms technical decisions with you, then writes an ordered task breakdown to .claude/plans/[feature-name]-plan.md.

What should a technical implementation plan include?▼

A plan should include technical decisions with rationale, ordered tasks listing files to create or modify, approach notes without full code, verification steps, task dependencies, and a requirements coverage table mapping every spec requirement to at least one task.

What happens if the feature spec is incomplete or ambiguous?▼

The skill stops and flags the specific issue rather than guessing. It directs you to complete the specification first using the feature-spec skill before any planning or task breakdown begins.

Does the implementation plan contain actual code?▼

No. The plan uses file paths, function and component names, change descriptions, and pseudo-code only for non-obvious logic. Full code is written during the implementation phase, not during planning.

When should I not use a spec-driven implementation plan?▼

Skip it for trivial one-file changes or exploratory prototypes where task ordering and requirements traceability add overhead without value. It is designed for multi-task features that touch several areas of a codebase.