What problem does it solve? Turning raw requirements from Confluence pages, specs, or user requests into a structured, validated task breakdown is time-consuming and error-prone, often leaving gaps discovered only during implementation. ## Core Features & Use Cases - Requirements Extraction: Gathers functional, non-functional, business rule, integration, and security requirements from Confluence documents or direct user input with clarifying questions. - Task Decomposition: Breaks each requirement into backend tasks (entities, repositories, services, controllers, DTOs), frontend tasks (components, state, API integration), and testing tasks. - Completeness Validation: Runs a checklist covering happy paths, error cases, edge cases, security, and performance, then produces a gap analysis. - Use Case: Paste a Confluence feature spec for user authentication and receive a numbered requirements document saved to tasks/TASK-001/ with a full task breakdown and identified gaps, ready to hand off to design or planning. ## Quick Start Ask the assistant to analyze the requirements from your Confluence page and break the feature down into actionable tasks.