plan

Decompose architecture into milestones, epics, and tasks with dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill plan-gudzenkov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill plan-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose architecture into milestones, epics, and tasks to convert complex designs into an actionable backlog and roadmap.

Core Features & Use Cases

  • Roadmap generation: structure architecture into milestones, phases, and release targets.
  • Epic and task decomposition: create atomic tasks with clear acceptance criteria and sequencing.
  • Traceability: connect requirements to architecture components, epics, and individual tasks to support verification and delivery planning.
  • Use Case: turn a software architecture doc into a runnable plan with ROADMAP.md and BACKLOG.md to guide development.

Quick Start

Provide architecture context and run the plan skill to generate ROADMAP.md and BACKLOG.md ready for execution.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I convert software architecture into a project roadmap and backlog?

You convert architecture into a structured project plan by decomposing designs into milestones, epics, and atomic tasks. The output includes ROADMAP.md and BACKLOG.md files with clear sequencing and explicit dependencies for execution.

What is ADR-based hierarchy for breaking down project milestones and epics?

ADR-based hierarchy is a structured decomposition approach that enforces traceability from requirements to deliverables. It connects architecture components to epics and individual tasks, ensuring clear sequencing and atomic backlog item granularity for delivery planning.

How do I create an actionable backlog from an architecture document?

You create an actionable backlog by decomposing architecture into atomic tasks with clear acceptance criteria. This generates a BACKLOG.md file that ensures traceability between requirements, architecture components, epics, and individual tasks for execution.

Can I generate traceability from requirements to deliverables for engineering projects?

Yes, you can generate traceability from requirements to deliverables by applying an ADR-based hierarchy. This connects architecture components to epics and individual tasks, supporting verification and structured delivery planning for engineering projects.

Does the plan generation process support dependency mapping for backlog tasks?

Yes, the plan generation process supports dependency mapping by producing BACKLOG.md with explicit dependencies. It structures architecture into milestones and atomic tasks, ensuring clear sequencing and traceability across the project roadmap.