What problem does it solve?
It prevents costly implementation pivots by challenging a specification and plan from both product strategy and engineering risk perspectives before any build work starts.
Core Features & Use Cases
- Dual-Lens Critical Review: Assesses problem validation, user value, alternatives, edge cases, and success measurement using a Product Lens, then evaluates architecture, failure modes, security/privacy, performance, testing, and operational readiness using an Engineering Lens.
- Extension Hook Integration: Detects and runs configured pre-critique hooks (from .specify/extensions.yml) to enrich context while respecting optional vs mandatory execution rules.
- Structured, Actionable Output: Generates a critique report in FEATURE_DIR/critiques/critique-{timestamp}.md using the critique-template structure, including severity classification (🎯 Must-Address, 💡 Recommendation, 🤔 Question) and a findings summary table.
- Safe Guardrails for Artifacts: Enforces STRICTLY READ-ONLY behavior for existing spec/plan artifacts and only creates new critique output files, with suggested spec/plan edits provided for optional follow-up.
Quick Start
Run speckit-critique-run from the skill entry command context so it reads spec.md and plan.md, loads constitution guidance if present, and produces a timestamped critique report for review.
