Spec-Kit (10 commands) · PM-Skills (37 product:* skills) · Spec-Driven Workflow · 3T Matrix (Tools × Techniques × Templates per ADLC stage) Real case study: command-center (CC-001 … CC-032)
What is Spec-Driven PM?
Spec-Driven Development is the discipline of writing the SPEC first (what success looks like, in testable form), CLARIFYING ambiguity before committing to code, PLANNING the work as discrete tasks, then IMPLEMENTING — with retrospective learning fed back into the next cycle. The ADLC framework makes this concrete: 10 /speckit.* commands drive the spec lifecycle; 37 product:* PM-Skills cover the strategy / discovery / writing / planning / analysis tasks; 8 templates standardise outputs; and the 3T Matrix maps every tool / technique / template to the ADLC stage it serves.
📋Specify/speckit.specify
→
❓Clarify/speckit.clarify
→
📐Plan/speckit.plan
→
✅Tasks/speckit.tasks
→
🛠️Implement/speckit.implement
→
🔁Retrospect/speckit.retrospective
The 5 ADLC stages
Stage🔍 DiscoverExplore codebase + history · Search docs · Onboard