HOW · PM execution toolkit (Spec-Kit · PM-Skills · 3T Matrix) · Audience: PO / PM / engineer · Part of the ADLC lifecycle docs: WHAT (/adlc) · WITH-WHAT (/adlc) · HOW (/pm-toolkit)
AI agents work the sprint; 1 HITL manager reviews; no 10-person delivery org required
CTO
Architectural rigour built in
Every design decision lands in an ADR (Architecture Decision Record) — no whiteboard-only choices
/speckit.plan + /speckit.tasks produce dependency-ordered task lists engineers start Build with a clear brief
3T Matrix maps every tool / technique / template to the ADLC stage — no ad-hoc prompting
92 hooks enforce coding discipline and Principle-I governance at tool-call level — not advisory
CFO
Predictable spend, traceable value
FOCUS 1.2+ cost attribution from day one — CFO sees per-feature AWS spend, not a lump-sum invoice
Spec-Kit produces acceptance checklists before code is written — catches scope-creep at design, not invoice
192 commands × avg 45 min workflow = 8,640 hours of codified team knowledge on tap (NZD efficiency)
Infracost estimate gate before every terraform apply — no cost surprises from unreviewed infra changes
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.
Stage🔍 DiscoverExplore codebase + history · Search docs · OnboardProduct Owner aligns backlog to real user needs before a line of code is written — no wasted sprint budget.
Stage📐 DesignPlan project · Develop tech specs · Define architectureCloud Architect locks decisions in ADRs. Engineers start Build with a clear brief, not a blank page.
Stage🛠️ BuildImplement code · Write tests · Create commits / PRsEngineers ship tested, governed code. QA inherits a checklist, not a guess. CISO gets shift-left security evidence.
Stage🚀 DeployAutomate CI/CD · Configure envs · Manage deploymentsPlatform Engineer ships infra in minutes, not weeks. CFO sees FOCUS-tagged cost attribution from day one.
Stage📊 Support & ScaleDebug errors · Refactor at scale · Monitor usageSRE resolves incidents faster with AI runbooks. COO tracks DORA metrics and capacity trends in one dashboard.
Stage📦 DeprecateUsage-floor check · Blast-radius analysis · Data archival · Evidence preservationLegal and compliance teams get a signed decommission plan before resources are removed — audit trail preserved.
Why executive teams adopt this
One language across every product. CFO, CISO, Platform Engineer, and SRE all navigate the same 6-stage map — no translation layer between the boardroom and the sprint board.
Every decision leaves a traceable record. Spec-Kit commands produce ADRs, checklists, and task lists that double as audit evidence for APRA CPS 234 and ISO 27001.
37 PM playbooks, never a blank page. Strategy, discovery, pricing, pre-mortem, retro — each is a paste-and-run template proven across 5 enterprise products.
Governed velocity, not just speed. The 3T Matrix maps tools, techniques, and templates to each stage so teams move fast without skipping the compliance checkpoints that matter to the board.