Why is this skill necessary before starting implementation?

It provides a structured bridge that prevents scope creep and ensures that developers have a clear, testable roadmap before writing code.

Where does this skill sit in the development lifecycle?

It is the fourth stage of a six-phase workflow: Research, Discussion, Specification, Planning (this skill), Implementation, and Review.

What is the primary input for the Technical Planning skill?

This skill uses the validated specification file located in 'docs/workflow/specification/{topic}.md' as its sole source of truth to ensure consistency.

Can I choose different formats for my implementation plan?

Yes, the skill allows you to select from various output adapters defined in the workflow's reference documentation.

Does this skill generate source code?

No, it focuses on the 'How'—defining phases, tasks, and acceptance criteria. The actual coding happens in the subsequent Implementation phase.

Technical Planning Architect

Name: Technical Planning Architect
Author: leeovery

byleeovery

•

Productivity & Workflow

Transforms technical specifications into structured, actionable implementation plans with phases, tasks, and acceptance criteria.

About

The Technical Planning skill bridges the gap between high-level documentation and actual coding by acting as a technical architect and product owner. It extracts requirements from existing specifications to create a detailed roadmap that organizes work into logical phases and concrete tasks. This ensures that every step of the implementation is grounded in the project's source of truth, facilitating a strict test-driven development (TDD) workflow and reducing the risk of architectural drift or missed requirements during the build phase.

Key Features

Generates detailed tasks with clear, verifiable acceptance criteria.
1 GitHub stars
Ensures plans are strictly derived from the validated specification source of truth.
Converts specifications into phased implementation roadmaps automatically.
Maintains a standardized directory structure for project documentation.
Supports multiple output formats tailored to different project management needs.

Use Cases

Standardizing documentation workflows to ensure consistent planning across different development teams.
Breaking down a software architecture into small, manageable tasks for a TDD implementation.
Developing a step-by-step roadmap for a complex feature after the specification is approved.

About

Key Features

Generates detailed tasks with clear, verifiable acceptance criteria.
1 GitHub stars
Ensures plans are strictly derived from the validated specification source of truth.
Converts specifications into phased implementation roadmaps automatically.
Maintains a standardized directory structure for project documentation.
Supports multiple output formats tailored to different project management needs.

Use Cases

Standardizing documentation workflows to ensure consistent planning across different development teams.
Breaking down a software architecture into small, manageable tasks for a TDD implementation.
Developing a step-by-step roadmap for a complex feature after the specification is approved.