ai-sdlc-claude

Start here (5 minutes, no meeting required)

What this is, in plain words

Your organisation uses Claude to write code much faster than before. The steps around the code, gathering requirements, designing, planning, reviewing, testing, releasing, and reacting to incidents, still ran at meeting speed. This plugin makes those steps run at the same speed without removing the people who decide.

It does that with three ideas:

  1. Every step ends by saving one short file into the code repository. An idea becomes intent.md. A design becomes spec.md. An implementation plan becomes plan.md. Code becomes a pull request. A production problem becomes a new intent.md. The file is the hand-over; nobody has to forward anything.
  2. Claude writes the files; a named person accepts them. Accepting is a one-click merge. Claude cannot accept its own work, approve a pull request, or release to production.
  3. Rules are enforced automatically while Claude works, not discovered in a review weeks later. Policy text (security, compliance, brand, UX) is applied as Claude writes; hard rules (protected files, secrets, production releases) are blocked by scripts called hooks.

The loop

  idea, ticket or incident
        │
  1 PLAN      anyone + Claude  →  intent.md        product owner accepts
  2 DESIGN    Claude           →  spec.md          product owner accepts (concerns flagged for policy owners)
  3 BUILD     engineer + Claude→  plan.md, code    engineer accepts the plan; hooks guard the build
  4 TEST      Claude proves it →  test output      attached to the pull request
  5 DEPLOY    Claude reviews   →  findings         code owner approves; release manager authorises production
  6 MAINTAIN  a script watches →  new intent.md    service owner triages, and the loop continues

Find your page

If you are… Read Time
Anyone with an idea or a problem to report roles/originator.md 3 min
A product owner / product manager roles/product-owner.md 8 min
A developer roles/engineer.md 10 min
QA / test engineer roles/qa.md 8 min
A tech lead or architect roles/tech-lead.md 8 min
A platform / DevOps engineer roles/platform-engineer.md 15 min
Security, compliance, brand, UX or another policy owner roles/security-compliance.md 8 min
A release manager roles/release-manager.md 8 min
A service owner or on-call engineer roles/service-owner.md 8 min
Engineering leadership roles/leadership.md 5 min

Each page is self-contained: what you do, exactly which commands to type, what you will see, what only you can decide, and what you never have to do. If a word is unfamiliar, see the glossary. To see a whole change go round the loop once, read the walkthrough.

What changes for you, and what does not

Stays the same Changes
You are accountable for decisions in your area You review what Claude produced instead of producing it from scratch
Approvals are recorded and auditable They are recorded as merges and approvals in the repository, not in meeting minutes
Policies apply They apply while the work is done, and are blocked automatically where they must hold
Production needs a human’s authorization The authorization is one recorded action, and nothing can bypass it

Where things are

This site is open source. Improve this page.