arc-planning

Transform specifications into a DAG of epics and features with dependency validation.

6|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/GregoryHo/arcforge --skill arc-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arc-planning
Source: https://github.com/GregoryHo/arcforge/tree/main/skills/arc-planning
Command: npx skills add https://github.com/GregoryHo/arcforge --skill arc-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of converting complex specifications into a structured, executable plan, ensuring traceability and preventing scope creep.

Core Features & Use Cases

  • Specification Breakdown: Converts high-level specs into epics and features.
  • Dependency Mapping: Automatically derives and validates task dependencies.
  • Traceability: Maintains a strict 1:1 mapping between requirements and features.
  • Use Case: When given a new feature requirement document, this Skill will generate a detailed breakdown of epics and features, including their dependencies, ready for the development team.

Quick Start

Use the arc-planning skill to break down the specifications found in specs/spec.xml.

Frequently Asked Questions about arc-planning

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

FAQPage Schema
How do I break down software specifications into executable tasks?▼

To break down software specifications into executable tasks, this Skill transforms high-level specs into a structured Directed Acyclic Graph (DAG) of epics and features with automatically derived dependencies.

What is a DAG in dependency management for task breakdown?▼

A DAG in dependency management is a Directed Acyclic Graph that structures epics and features in a strict sequence. It enforces 1:1 traceability between requirements and tasks while validating against circular dependencies.

How do I prevent circular dependencies when mapping task dependencies?▼

To prevent circular dependencies during task mapping, this Skill validates all references automatically before outputting the final plan. It ensures the generated DAG structure contains no circular dependency loops.

Can I maintain traceability between requirements and features automatically?▼

Yes, you can maintain traceability automatically. This Skill enforces a strict 1:1 mapping between original specifications and generated features, ensuring full traceability throughout the development lifecycle.

What is the best way to convert a spec document into a development plan?▼

The best way to convert a spec document into a development plan is using automated breakdown to generate a dag.yaml file alongside structured epic and feature directories, ensuring all references are valid.

Does this specification breakdown tool work without external dependencies?▼

Yes, this specification breakdown tool works without external dependencies. It operates independently to parse specifications and output structured epic and feature directories along with a dag.yaml file.