epic▌

Architectural planning prompt for translating product requirements into modular, scalable technical specifications. \n \n Generates comprehensive Epic Architecture Specifications in Markdown, including system diagrams, feature lists, and technology stack recommendations \n Enforces domain-driven design patterns with Docker containerization, TypeScript/Next.js, Turborepo monorepos, tRPC APIs, and Stack Auth authentication \n Produces Mermaid diagrams spanning user, application, service, data, and

Structure epics as testable hypotheses with explicit assumptions, lightweight experiments, and measurable success criteria. \n \n Uses an if/then format to articulate the action, target persona, expected outcome, and validation method, making product assumptions explicit before committing to full build-out \n Emphasizes \"tiny acts of discovery\" experiments (prototypes, concierge tests, landing pages) that validate hypotheses in days or weeks, not months \n Defines falsifiable success criteria

Break down large epics into vertical-slice user stories using Humanizing Work's 9 splitting patterns. \n \n Guides product managers through sequential pattern application (workflow steps, CRUD operations, business rules, data variations, UI methods, major effort, simple/complex, performance deferral, and spikes) to identify which pattern fits \n Validates epics against INVEST criteria before splitting to ensure stories are independent, negotiable, valuable, estimable, and testable \n Generates e

ln-210-epic-coordinator

Structured prompt for generating Epic-level Product Requirements Documents with consistent output format. \n \n Guides product managers through a standardized PRD structure covering goals, user personas, journeys, functional and non-functional requirements, success metrics, and scope boundaries \n Outputs markdown-formatted PRDs saved to a consistent directory path ( /docs/ways-of-work/plan/{epic-name}/epic.md ) for use as single source of truth \n Includes built-in prompting for clarifying ques