claude

sdlc-factory

An optional software factory over the sdlc change loop: a spec-writer, a builder, code, security and test reviewers, and an approver run a change's spec, plan, build and review, behind the same human gates. Install it only where you want agents to do that; sdlc works the same without it.

0 on GitHubby James Faeldonv1.7.0MITupdated todayworkflow
/

Plugin sdlc-factory from marketplace sdlc in faeldon/sdlc. Commands read from the repo's manifest — today.

What it installs

Skills (3)

  • eval

    Replay the factory's reviewers on the diffs that let real bugs through — every escaped bug the register and the Close commits trace to a change — and score which reviewer would have caught each, against the last eval, after one approval of the agent runs it takes. Use when a reviewer's prompt, a mod

  • review

    Review code no change touches — the paths the base branch's [review] sensitive lists, else the least recently changed files, or the paths named — with the factory's code and security reviewers, and after one approval of the agent runs it takes, write what they find as proposed [bug] entries in a rep

  • spec

    Have the factory's spec-writer agent draft a Tier 2 change's spec.md from its intent, show the draft, and after one approval write it and advance the change to stage design — the factory's stand-in for /sdlc:spec. Use from the change's own worktree, after /sdlc:intent, when the repo has sdlc-factory

Subagents (8)

  • approver

    Reads one change's spec, plan, diff, every review round and notes.md after the factory's last round, and recommends READY or ESCALATE with the reasons, for the person who decides at /sdlc:ship. Spawned by /sdlc-factory:build. It recommends only — it never merges, commits or approves anything into ma

  • builder

    Plans and implements one change in its own worktree, from its approved spec (or a Tier 1 intent's Approach), test first, in small slices, then reworks it from the reviewers' findings. Spawned and resumed by /sdlc-factory:build. Never commits, pushes or merges; /sdlc:ship makes the one commit.

  • reviewer-behaviour

    Runs one change the way a person would check it worked — the repo's gate and the end-to-end path its spec describes — and returns a VERDICT with what ran, what it printed and its exit, each failure as a CHANGE line. Spawned by /sdlc-factory:build in parallel with the other reviewers. Not for judging

  • reviewer-code

    Reviews one change's uncommitted diff for correctness against its spec, readability, architecture and cost, and returns a VERDICT with each required change as a CHANGE line. Spawned by /sdlc-factory:build in parallel with the other reviewers. Not for security depth or test strategy, which have revie

  • reviewer-security

    Reviews one change's uncommitted diff for exploitable security issues, starting from its trust boundaries, and returns a VERDICT with each required fix as a CHANGE line. Spawned by /sdlc-factory:build in parallel with the other reviewers. Not for general code quality or test coverage, and never edit

  • reviewer-test

    Reviews whether one change's tests prove its spec's requirements, can fail, and cover the edge cases the spec names, and returns a VERDICT with each missing or weak test as a CHANGE line. Spawned by /sdlc-factory:build in parallel with the other reviewers. Not for code style or security, and it writ

  • spec-writer

    Drafts a Tier 2 change's spec.md from its intent, inside the repo's invariants, with numbered checkable requirements. Spawned by /sdlc-factory:spec, which shows the draft to a person before anything is written. Not for writing code, plans or reviews.

  • verifier

    Checks each CHANGE line one review round of a factory build asked for against the code, and returns each as KEPT or DROPPED with why, so the builder reworks only what is real. Spawned by /sdlc-factory:build after a round's reviews and before any rework. Not for reviewing the change itself, which the

View source on GitHub

More from faeldon/sdlc

All 2 plugins →

sdlc

claude

The AI-native SDLC as a change pipeline: numbered intent/spec/plan artifacts under work/, tier-sized overhead, and a human gate at every stage that writes. Repo-agnostic mechanism; each repo supplies its own policy, commands and templates through .sdlc/config.toml.

15 skills · 1 agent

0

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.

5 skills · 16 commands · 4 agents · hooks

Imbad0202/academic-research-skills 56,698

Maintain sdlc-factory?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins