Implementation Planner

Implementation Planner

Transform a tech-agnostic feature specification into a codebase-specific implementation plan. This skill is designed to be used with Claude Code, where the repo is available as context.

Input

This skill expects a feature specification as input, typically produced by the feature-refiner skill. The input should contain:

• Title: Name of the feature
• Description: 2-3 sentences on what the feature does and why
• Acceptance Criteria: A list of specific, testable criteria

If the input is missing any of these, ask the user to provide them before proceeding.

Process Overview

1. Receive the feature spec — Parse the title, description, and acceptance criteria
2. Explore the codebase — Understand the repo's structure, tech stack, patterns, and conventions
3. Identify the relevant code — Find the files, components, and modules that the feature will touch
4. Map criteria to code changes — Determine what needs to change or be created for each acceptance criterion
5. Detect risks and dependencies — Surface anything that could block or complicate implementation
6. Produce the plan — Write a structured, actionable implementation plan

Step 1: Receive the Feature Spec

Parse the provided feature spec. Echo it back in a summary to confirm understanding.

If the spec is ambiguous or seems incomplete, ask clarifying questions before exploring the codebase.

Step 2: Explore the Codebase

Examine the repository to understand:

• Project structure: Directory layout, entry points, configuration files
• Tech stack: Languages, frameworks, libraries, build tools
• Patterns and conventions: How existing features are structured (routing, state management, data access, API patterns, component structure, naming conventions, test patterns)
• Relevant existing code: Files and modules that relate to the feature being planned

Focus your exploration on areas relevant to the feature. Don't map the entire repo — just what matters.