megaplan-epic

Orchestrate multi-sprint workflows by decomposing projects into sequential megaplan milestones.

97|8|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/peteromallet/arnold --skill megaplan-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: megaplan-epic
Source: https://github.com/peteromallet/arnold/tree/main/megaplan/data/_codex_skills/megaplan-epic
Command: npx skills add https://github.com/peteromallet/arnold --skill megaplan-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you execute work that is too large for a single sprint by turning it into an ordered series of full megaplan runs, with persisted state and clear failure semantics between milestones.

Core Features & Use Cases

  • Multi-sprint decomposition: break a project into milestone-sized megaplans that each produce written artifacts for downstream milestones.
  • Stateful orchestration via chain spec: use a chain.yaml to define base branch, optional seed plan, milestone order, and per-milestone rubric knobs (profile, robustness, depth, vendor).
  • Failure and escalation handling: control what happens when a milestone fails (abort, skip, or retry) and ensure progress can be resumed without losing completed milestones.
  • Unattended runs for long work: support cloud chain mode so the workflow can continue across terminal sessions.

Quick Start

Create a chain.yaml spec for your milestones and then run megaplan chain start --spec with the path to that spec.

Frequently Asked Questions about megaplan-epic

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

FAQPage Schema
How do I orchestrate multi-sprint software workflows with state persistence and failure handling?

Multi-sprint workflow orchestration is achieved by decomposing large projects into a sequential chain of milestones using a YAML spec, enforcing deterministic ordering, state persistence, and explicit failure semantics between dependent megaplan runs.

What is a milestone chain spec and how does it manage software planning dependencies?

A milestone chain spec is a YAML file defining base branch, optional seed plan, milestone order, and per-milestone rubric knobs like profile, robustness, depth, and vendor. It ensures each milestone produces written artifacts required by downstream dependencies.

How do I start running a megaplan milestone chain from a YAML spec?

To start a chain, create a chain.yaml defining your milestones and rubric configuration, then execute the chain driver with the start command and pass the path to your spec file to initiate deterministic progression.

Can I resume multi-sprint workflow progress after a milestone failure without losing completed artifacts?

Yes, state persistence allows the chain driver to resume progress deterministically. Explicit on_failure and on_escalate policies define whether to abort, skip, or retry a failed milestone while preserving completed milestone artifacts.

Does cloud automation support unattended workflow orchestration for long-running software plans?

Cloud chain mode supports unattended workflow orchestration, allowing multi-sprint megaplan chains to continue executing across disconnected terminal sessions for long-running software planning and execution tasks.

What are the limitations of using a sequential milestone chain for multi-sprint project decomposition?

Milestone chains enforce sequential ordering, meaning downstream milestones strictly depend on upstream written artifacts. This rigid dependency structure limits parallel execution and requires comprehensive rubric configuration for each independent milestone.