Phase 11 Multi-Persona Product Review. Evaluates final product from 10 different professional perspectives to ensure real-world readiness. Triggered after Phase 10 Quality Score passes (>= 80).
MANDATORY workflow for GitHub Speckit projects. Enforces Spec-First → Clarify → Research → Evaluate → Design → Plan → TDD → Review, with optional Constitution and quality checks. Activates when working in projects with .github/speckit/ directory.
Spawn parallel worker terminals to execute multi-domain tasks concurrently. Use when 3+ independent tasks span 2+ domains (frontend, backend, testing, security, etc.)
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. Use to identify inconsistencies before implementation.
Generate a custom checklist for the current feature based on user requirements. Checklists are "unit tests for requirements" - they validate quality, clarity, and completeness of requirements in a given domain.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. Use after /speckit.specify to resolve ambiguities before research and evaluation.
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync. Use when starting a new Speckit project or updating project principles.
Evaluate feature spec against market research to identify features to add, remove, or modify. Use after /speckit.research to finalize spec before design.