milestone-decomposition

Decompose project milestones into ordered, verifiable feature entries.

Updated Apr 9, 2026

Search Tags:#planning #strategy #decomposition #dependency #milestone #feature-list

Ready to run

npx skills add https://github.com/ldmrepo/agent-harness --skill milestone-decomposition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: milestone-decomposition
Source: https://github.com/ldmrepo/agent-harness/tree/main/template/.claude/skills/milestone-decomposition
Command: npx skills add https://github.com/ldmrepo/agent-harness --skill milestone-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

High‑level milestones are difficult to translate into concrete, testable work items, causing planning delays and ambiguous scope.

Core Features & Use Cases

Analyzes a milestone’s goal and success criteria to identify required capabilities.
Maps each capability to a structured feature entry with metadata such as priority, risk, and verification type.
Orders the generated features by dependency, validates schema compliance, and ensures the total count stays within defined limits.
Use case: During project kickoff, feed the upcoming milestone and the system automatically produces a ready‑to‑implement feature list for the coding cycle.

Quick Start

Ask the skill to break down the next milestone into a prioritized feature list.

Frequently Asked Questions about milestone-decomposition

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

FAQPage Schema

How do I decompose project milestones into actionable feature lists?▼

Yes, you can generate verifiable feature items from existing project goals during re-planning phases. Supplying milestone definitions and existing feature lists allows the decomposition process to validate schema compliance and respect dependency limits automatically.

How do I map milestone dependencies to a prioritized feature list?▼

Mapping milestone dependencies involves ordering generated features by their relationships and scope limits. The resulting feature list enforces dependency sequences, ensuring each prioritized JSON feature entry is bounded and ready for the planner, coder, and reviewer workflow.

Can I generate verifiable feature items from existing project goals?▼

What inputs do I need to break down a milestone into testable work items?▼

Breaking down a milestone requires milestone definitions, project goals, and existing feature lists as primary inputs. Optional state files can also be provided to ensure the generated feature entries respect dependency and scope limits accurately.

Does strategic planning decomposition enforce limits on generated feature counts?▼

Strategic planning decomposition validates schema compliance and ensures the total count of generated features stays within defined limits. This prevents ambiguous scope by bounding the feature list entries during the milestone creation phase.