Verified:GitHub

program-planning

Decompose large briefs into program plans and bounded initiatives with dependency-aware planning waves.

1|Updated Mar 7, 2026

Search Tags:#initiatives #project-management #docs-generation #epic-refinement #program-planning #planning-waves #open-source-workflow

Ready to run

npx skills add https://github.com/WASD6570/crypto-monitor --skill program-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: program-planning
Source: https://github.com/WASD6570/crypto-monitor/tree/main/.agents/skills/program-planning
Command: npx skills add https://github.com/WASD6570/crypto-monitor --skill program-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a large brief into program docs, one or more bounded initiatives, and dependency-aware epic-refinement waves

Core Features & Use Cases

Ingest a long, dense brief that spans multiple services, contracts, and rollout tracks
Produce a program-level view plus bounded initiatives when needed, with clear boundaries and handoffs
Break down initiatives into feature slices, platform tracks, and cross-cutting concerns; identify dependencies and risks; plan safe execution waves
Output artifacts under docs/specs/, initiatives/, plans/epics/ and provide seeds for program-refining

Quick Start

Feed me a long brief and I will produce a program-level plan with bounded initiatives and an initial epic-waves handoff.

Frequently Asked Questions about program-planning

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

FAQPage Schema

How do I break down a large project brief into actionable initiatives and epics?▼

Large brief decomposition splits dense documents into bounded initiatives and dependency-aware epic-refinement waves. It processes lengthy briefs spanning multiple services and rollout tracks to produce structured program plans with clear boundaries and handoffs.

What is dependency-aware program planning for multi-service rollouts?▼

Dependency-aware program planning identifies cross-cutting concerns, platform tracks, and feature slices to sequence safe execution waves. It maps dependencies and risks across multiple services and contracts to enable organized, multi-initiative roadmaps.

Can I use program planning for lengthy briefs spanning multiple contracts and rollout tracks?▼

Program planning is designed specifically for lengthy, dense briefs spanning multiple services, contracts, and rollout tracks. It produces a program-level view plus bounded initiatives with clear boundaries and handoffs for complex, multi-track rollouts.

How do I generate program docs and epic specifications from a long brief?▼

Generating program docs from a long brief produces output artifacts mapped to docs/specs/, initiatives/, and plans/epics/ directories. It also provides program-refining seeds to iterate on the initial epic-waves handoff for structured planning.

What is the best way to plan safe execution waves for cross-cutting platform tracks?▼

Planning safe execution waves breaks down initiatives into feature slices and platform tracks while identifying dependencies and risks. It sequences the work into bounded waves that account for cross-cutting concerns and enable organized, multi-initiative roadmaps.

When should I not use multi-initiative roadmap decomposition for project planning?▼

Multi-initiative roadmap decomposition is not suited for small, single-service briefs or projects with minimal cross-track dependencies. It targets lengthy, dense briefs requiring bounded initiatives, dependency-aware epic refinement, and organized rollout tracks across multiple services.