What problem does it solve? Turning a raw requirements document into an actionable version development plan is error-prone: embedded field-level changes get missed, tasks get fragmented by page or API, and delivery batches lack clear acceptance criteria. This Skill enforces a coverage-first workflow that scans the full document, confirms nothing is missed, then produces cohesive tasks, testable waves, effort estimates, and team assignments. ## Core Features & Use Cases - Coverage-verified requirements extraction: Combines marker scanning, requirements-table reading, and full-text review to catch embedded and scattered changes, then waits for user confirmation before proceeding. - Cohesive task and wave planning: Merges changes into independently testable task candidates with anti-fragmentation checks, then organizes them into waves with test scope, prerequisites, and completion criteria. - Effort estimation and team assignment: Produces role-based effort tables and assignment plans that respect reuse chains, scattered-change groups, and wave boundaries. - Use Case: Given a PRD for version 2.3 and a team of five, generate a requirements list, a task/wave breakdown with creation-order slugs, and an effort plan saved under doc/2.3/ for downstream task creation. ## Quick Start Ask the AI to generate a version development plan from your requirements document by providing the document path, version number, and team composition.
