design-phase

This Skill automates extraction of user stories from an approved PRD, then attaches inline architecture notes (API endpoints, database models, key files, patterns) directly to each story file. It spawns an Architect agent to annotate stories with technical guidance in under 30 seconds, bridging requirements and implementation.

Yes. After annotation, a Project Manager agent creates a detailed execution plan that breaks down stories into tasks, assigns them to domain agents, and organizes them into parallel waves with dependencies—ready for immediate implementation.

Provide an approved PRD file path, project folder location, complexity level, available tools, and scope. The Skill reads the PRD, extracts and annotates user stories enforcing granularity guidelines, and outputs story files, architecture notes, and a structured execution plan.

Architecture annotations target 50–100 lines of concise, inline notes delivered in approximately 30 seconds, avoiding lengthy separate design documents. This keeps the workflow efficient and focused on actionable technical guidance.

Initiate the design phase immediately after your PRD passes a vibe-check and receives approval. It bridges approved requirements and development readiness by automating story extraction, technical annotation, and execution planning.

Yes. The Skill enforces CRITICAL story granularity guidelines to ensure consistent, implementable user stories and maintains inline architecture annotations throughout each story file.