feature-planner

Feature planning transforms functional requests into structured development plans using story decomposition, prioritization, and S/M/L/XL sizing. It generates atomized stories with file targets, dependencies, and standardized templates for sprint execution.

Adversarial review in feature planning critically evaluates a generated plan to find gaps, feasibility issues, bad decoupling, and missing edge cases. It is needed when finalizing a plan for sprint execution to ensure robustness before development begins.

Story decomposition breaks software design requirements into prioritized epics and atomized stories using strict quality rules. It requires imperative titles, acceptance criteria, patterns, dependencies, and S/M/L/XL sizing to ensure execution readiness.

Executive synthesis creates a leadership-friendly summary from a feature plan including objectives, scope, prioritized risks, effort distribution, and external dependencies. It provides the high-level context needed for stakeholder alignment.

Feature planning supports iterating after feedback by scanning existing codebase conventions to identify constraints and risks. It applies structured discovery to refine plans and ensure new stories align with established patterns during adversarial review.

Automated story decomposition requires strict template compliance and YAML frontmatter to function. Its limitation is the reliance on accurate initial discovery; if constraints or missing edge cases are not caught during adversarial review, sprint execution readiness is compromised.