Is the generated plan compatible with automated implementation?

Absolutely. The plan is designed to be actionable with specific file paths and granular tasks that Claude or a developer can follow to complete the feature.

How does the skill handle testing requirements?

It explicitly defines both unit and integration tests within the implementation plan, ensuring that testing criteria are established before the coding phase begins.

What is the primary output of the architect:plan skill?

The skill generates a comprehensive markdown file in the docs/specs/ directory containing the feature context, architecture components, ASCII diagrams, and a step-by-step implementation checklist.

Can I use this skill without completing previous workflow phases?

The skill requires data from .dev-workflow-state.json to function correctly. If preceding phases (clarification and architecture) are missing, it will prompt the user or exit in automatic mode.

Does this skill integrate with Claude Code's built-in tasks?

Yes, in interactive mode, it utilizes the TaskCreate and TaskUpdate tools to manage the planning process as a series of trackable sub-tasks.

Implementation Planner

Name: Implementation Planner
Author: atournayre

byatournayre

0•

Productividad y Flujo de Trabajo

Generates comprehensive, actionable implementation plans and technical specifications based on architectural decisions.

The Implementation Planner is a specialized skill for Claude Code designed to handle Phase 4 of the development workflow. It transforms high-level architectural designs into granular, executable roadmaps by reading project context and prior decision logs. This skill automates the creation of structured markdown documentation in the docs/specs/ directory, featuring component maps, ASCII flow diagrams, and step-by-step task lists. By formalizing implementation details and testing requirements before a single line of code is written, it ensures structural integrity and provides a clear audit trail for complex software features.

Características Principales

01Seamless integration with Claude Code's task management system for tracking progress

02Contextual awareness via .dev-workflow-state.json to ensure architectural alignment

03Automated creation of detailed technical specifications in markdown format

04Generation of ASCII flow diagrams and component responsibility tables

05Pre-definition of unit and integration testing requirements to guide development

060 GitHub stars

Casos de Uso

01Bridging the gap between high-level design and active coding in AI-assisted workflows

02Standardizing technical documentation and specification formats across a codebase

03Translating complex architectural designs into granular, file-specific development tasks

Características Principales

01Seamless integration with Claude Code's task management system for tracking progress

02Contextual awareness via .dev-workflow-state.json to ensure architectural alignment

03Automated creation of detailed technical specifications in markdown format

04Generation of ASCII flow diagrams and component responsibility tables

05Pre-definition of unit and integration testing requirements to guide development

060 GitHub stars

Casos de Uso

01Bridging the gap between high-level design and active coding in AI-assisted workflows

02Standardizing technical documentation and specification formats across a codebase

03Translating complex architectural designs into granular, file-specific development tasks