What problem does it solve?
Teams often jump from a vague business idea straight into code or feature specs, producing misaligned implementations, happy-path-only stories, and duplicated platform work. This Skill enforces a structured App Spec — domain model, identity model, ROI-backed workflows, gap analysis, and phased rollout — before any feature spec or code exists.
Core Features & Use Cases
- Phased spec authoring: Guides a staff-PM persona through business context, ubiquitous-language glossary, domain model, identity model, workflows with measurable ROI, user stories with failure paths, and platform gap analysis scored in atomic commits.
- Adversarial quality gates: Dispatches fresh-context DDD challenger subagents and architect checkpoints after each section to catch terminology drift, missing invariants, overengineering, and cross-story conflicts.
- Review mode: Audits an existing App Spec against every section checklist and returns severity-ranked findings.
- Use Case: A product lead says "define business requirements for a partner portal" and receives a complete App Spec with glossary, identity decision tree, 3-7 ROI-backed workflows, gap matrix, and a phased rollout ready for decomposition into feature specs.
Quick Start
Ask the agent to create an app spec for your product idea, providing the app name and a short description of the business need.