implementation-planning

Transform design documents into test-first implementation plans with traceability matrices.

33|Updated Jan 5, 2026

Search Tags:#workflow #tdd #traceability #task-decomposition #implementation-planning #plan-verification #exarchos

Ready to run

npx skills add https://github.com/lvlup-sw/exarchos --skill implementation-planning-lvlup-sw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/implementation-planning
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill implementation-planning-lvlup-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts design documents into deterministic, test-first implementation plans so teams and agents do not ship production code without tests and every design requirement is traced to actionable tasks.

Core Features & Use Cases

TDD-first decomposition: Break designs into 2–5 minute tasks that begin with a failing test and include expected failure reasons.
Spec traceability & verification: Auto-generate a traceability matrix, enforce DR-N provenance, and run deterministic verification via orchestration actions.
Parallelization & phase transitions: Detect independent task groups for parallel worktrees, update workflow state, and manage revision loops with guards.
Use case: Convert an existing docs/designs/<feature>.md into docs/plans/YYYY-MM-DD-<feature>.md with tasks, traceability, and plan-review gating.

Quick Start

Run the plan command on an existing design to produce a TDD-aligned implementation plan and traceability matrix.

Frequently Asked Questions about implementation-planning

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

FAQPage Schema

How do I convert a design document into a TDD implementation plan?▼

To convert a design document into a TDD implementation plan, apply the planning skill to your feature design file. It decomposes technical sections into 2–5 minute failing-test-first tasks and generates a traceability matrix mapping DR-N requirements.

What is test-first task decomposition for technical designs?▼

Test-first task decomposition breaks technical design sections into granular 2–5 minute tasks. Each task begins with a failing test and includes expected failure reasons, ensuring no production code ships without corresponding tests.

How do I generate a spec traceability matrix from feature requirements?▼

Generate a spec traceability matrix by transforming design files into implementation plans. The process enforces DR-N provenance, mapping each design requirement to actionable tasks and running deterministic verification checks via orchestration.

Can I identify parallel task groups for independent worktrees from a design file?▼

Yes, the planning workflow detects independent task groups within a design document suitable for parallel worktrees. It manages phase transitions, updates workflow state, and handles revision loops with guardrails.

Do I need an existing design document to create an implementation plan?▼

Yes, you need an existing design document file to use as input. The tool transforms existing feature or refactor design files into implementation plans, outputting a dated plan file with tasks and plan-review gating.

What are the limitations of automated plan verification for refactoring designs?▼

Automated plan verification relies on deterministic checks via orchestration actions. While it enforces failing-test-first TDD and guardrails for revision loops, complex or ambiguous design documents lacking clear DR-N requirements may limit verification accuracy.