How does it handle task tracking during the planning phase?

The skill uses a systematic TaskCreate and TaskUpdate pattern, allowing users to follow the progression from context reading to final state updates.

What is the main purpose of the dev:plan skill?

It automates the creation of a technical implementation roadmap, ensuring that every feature has a clear, actionable plan before any coding begins.

Where does this skill store the generated plans?

Plans are saved as Markdown files within the docs/specs/ directory of your project, typically using a kebab-case naming convention for easy reference.

Why does the plan include test specifications?

The skill follows development best practices by ensuring tests are defined upfront, providing a clear definition of done before implementation starts.

Does this skill require any previous steps to be completed?

Yes, it is designed as Phase 4 of a workflow. It reads from .claude/data/.dev-workflow-state.json and requires architectural decisions to be finalized first.

Dev Implementation Planner

Name: Dev Implementation Planner
Author: atournayre

byatournayre

•

Productivity & Workflow

Generates structured, actionable implementation plans in Markdown based on architectural decisions and feature requirements.

The Dev Implementation Planner is a specialized workflow skill designed to automate Phase 4 of the development cycle by transforming architectural concepts into a concrete roadmap. It reads project context from workflow state files to create detailed, step-by-step implementation specifications within your docs/specs/ directory. By mandating that tests be defined before coding and ensuring every task is actionable, this skill bridges the gap between high-level design and code production, providing a clear and standardized path for developers or AI agents to follow.

Key Features

01Integration with .dev-workflow-state.json for context-aware planning

02Standardized documentation storage in project-specific directories

038 GitHub stars

04Automated generation of detailed implementation specs in Markdown format

05Structured task management with real-time progression tracking

06Requirements-first approach ensuring tests are specified before implementation

Use Cases

01Preparing structured task lists for AI agents to execute in subsequent coding phases

02Enforcing project-specific documentation standards for new feature developments

03Converting high-level architectural decisions into a sequenced coding roadmap

Key Features

01Integration with .dev-workflow-state.json for context-aware planning

02Standardized documentation storage in project-specific directories

038 GitHub stars

04Automated generation of detailed implementation specs in Markdown format

05Structured task management with real-time progression tracking

06Requirements-first approach ensuring tests are specified before implementation

Use Cases

01Preparing structured task lists for AI agents to execute in subsequent coding phases

02Enforcing project-specific documentation standards for new feature developments

03Converting high-level architectural decisions into a sequenced coding roadmap