ros/spec-kit
1
0
Fork 0
mirror of https://github.com/github/spec-kit.git synced 2026-04-02 10:43:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
6eb15a7a3ee201d1e3743e5f0d92173b1503f9e6
spec-kit/templates/critique-template.md
Arun Kumar Thiagarajan 6eb15a7a3e feat: add 5 gstack-inspired lifecycle commands (critique, review, qa, ship, retro) 
Add 5 new core command templates inspired by Garry Tan's GStack to complete
the spec-driven development lifecycle:

- /speckit.critique: Dual-lens product + engineering review before implementation
- /speckit.review: Staff-level code review (correctness, security, performance)
- /speckit.qa: Systematic QA testing (browser-driven and CLI modes)
- /speckit.ship: Release automation (pre-flight, changelog, CI, PR creation)
- /speckit.retro: Sprint retrospective with metrics and improvement suggestions

Each command includes:
- Command template in templates/commands/
- Output report template in templates/
- Extension hook support (before_*/after_*)
- YAML frontmatter with prerequisite scripts

Updated README.md workflow from 6 to 11 steps and added CHANGELOG entry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-04-01 11:22:57 +05:30

3.5 KiB
Raw Blame History

Critique Report: [FEATURE NAME]

Date: [DATE] Feature: [Link to spec.md] Plan: [Link to plan.md] Verdict: [✅ PROCEED / ⚠️ PROCEED WITH UPDATES / 🛑 RETHINK]

Executive Summary

[One-paragraph assessment of the spec and plan quality, key strengths, and primary concerns from both product and engineering perspectives.]

Product Lens Findings 🎯

Problem Validation

ID Severity Finding Suggestion
P1 🎯/💡/🤔 [finding] [suggestion]

User Value Assessment

ID Severity Finding Suggestion
P2 🎯/💡/🤔 [finding] [suggestion]

Alternative Approaches

ID Severity Finding Suggestion
P3 🎯/💡/🤔 [finding] [suggestion]

Edge Cases & UX

ID Severity Finding Suggestion
P4 🎯/💡/🤔 [finding] [suggestion]

Success Measurement

ID Severity Finding Suggestion
P5 🎯/💡/🤔 [finding] [suggestion]

Engineering Lens Findings 🔧

Architecture Soundness

ID Severity Finding Suggestion
E1 🎯/💡/🤔 [finding] [suggestion]

Failure Mode Analysis

ID Severity Finding Suggestion
E2 🎯/💡/🤔 [finding] [suggestion]

Security & Privacy

ID Severity Finding Suggestion
E3 🎯/💡/🤔 [finding] [suggestion]

Performance & Scalability

ID Severity Finding Suggestion
E4 🎯/💡/🤔 [finding] [suggestion]

Testing Strategy

ID Severity Finding Suggestion
E5 🎯/💡/🤔 [finding] [suggestion]

Operational Readiness

ID Severity Finding Suggestion
E6 🎯/💡/🤔 [finding] [suggestion]

Dependencies & Integration

ID Severity Finding Suggestion
E7 🎯/💡/🤔 [finding] [suggestion]

Cross-Lens Insights 🔗

Items where both product and engineering perspectives converge:

ID Finding Product Impact Engineering Impact Suggestion
X1 [finding] [product concern] [engineering concern] [unified suggestion]

Findings Summary

Metric Count
🎯 Must-Address [count]
💡 Recommendations [count]
🤔 Questions [count]
Product findings [count]
Engineering findings [count]
Cross-lens findings [count]

Recommended Actions

🎯 Must-Address (Before Proceeding)

  1. [ID]: [Action with specific file and change description]

💡 Recommendations (Strongly Suggested)

  1. [ID]: [Action]

🤔 Questions (Need Stakeholder Input)

  1. [ID]: [Question requiring clarification]

Severity Legend:

  • 🎯 Must-Address: Blocks proceeding to implementation
  • 💡 Recommendation: Strongly suggested improvement
  • 🤔 Question: Needs stakeholder input to resolve

Generated by /speckit.critique — Dual-lens strategic and technical review for spec-driven development.