oh-my-speckit

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.

Execute the implementation plan by processing and executing all tasks defined in tasks.md. Use after /speckit.tasks to actually build the feature following TDD approach.

Execute the implementation planning workflow using the plan template to generate design artifacts. Use after /speckit.clarify to create technical architecture and implementation plan.

Conduct market and competitive research for a clarified feature spec. Use after /speckit.clarify to gather external context before evaluation.

Create or update the feature specification from a natural language feature description. Use when defining WHAT a feature should do before any design or implementation work.

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts. Use after /speckit.plan to break down implementation into executable tasks.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts. Use when you want to create GitHub issues from your tasks.md.