ai-sdlc-claude

Engineering leadership

Read time: 5 minutes.

What this is

Your organisation already writes code at agent speed. This plugin makes planning, review, testing, release and maintenance run at the same speed while keeping every control objective you are accountable for: recorded human decisions at the gates, separation of duties, policies enforced as the agent acts, and an audit trail made of commits and pull requests.

Your two decisions

  1. Which human approval gates survive. With change management and compliance, list them: change sign-off, release authorization, protected paths (migrations, infrastructure, generated code), anything regulated. The platform team encodes each as a hook that allows, asks, or blocks, every time, for everyone. Everything not on the list runs at agent speed. Exceptions no longer route through weekly committees; they are recorded where they happen (an override in an artifact, a needs-human label, a dismissal with band tuning).
  2. Which play next. Plays are modular. docs/adoption-roadmap.md gives the dependency order; pick by your bottleneck: a review queue (AI review + gates), requirements churn (intent + spec), incident load (control bands), or throughput (parallel sessions + evals).

Your command

/sdlc:metrics. Weekly leading indicators for teams; monthly lagging indicators for you:

You want Indicator
Ideas reach engineering intact and fast intent → committed in hours; survival rate; spec edits after build starts falling
Less rework first-pass merges rising; plan/diff drift near zero
Review keeps up time to first review in minutes; review time per PR falling; defects escaped vs caught
Governance holds gate wait visible and short; violations reaching production at zero
Delivery DORA four keys from the pipeline
Reliability learns breach → intent in minutes; repeat incidents of the same class falling

What changes for people

Human attention moves to the gates: reviewing what the agent flagged instead of starting each stage from scratch. Engineers steer several sessions. Product owners review specs they did not write. Release managers authorise instead of executing. Security and compliance encode policy once instead of catching violations repeatedly.

What does not change

You remain accountable for every decision that requires judgment. The people who decide are named in the record, and the record is the repository.

This site is open source. Improve this page.