claude

sdlc

Software delivery: explore the ground, agree a spec, audit it, plan it, audit that, build it, review the code, then close it and hand it to zz-handover.

0 on GitHubby ZZ Stackv0.102.0+da06d61bMITupdated 4 days ago
/

Plugin sdlc from marketplace zz-stack in zhixuan312/zz-stack. Commands read from the repo's manifest — 4 days ago.

What it installs

Skills (13)

  • sdlc-audit-criteria

    The eleven prose failure modes every sdlc audit applies, the evidence shapes a finding must take, and the JSON a round returns. Loaded by sdlc-spec-audit and sdlc-plan-audit; never run on its own.

  • sdlc-execute

    Build what the approved plan describes — one subagent per task, one wave of tasks with disjoint ownership at a time, each making its task's contract true and its plan-authored checks pass. Main agent orchestrates and stays accountable for the sequence; the work itself is dispatched.

  • sdlc-explore

    Ground a raw idea before anyone designs it — capture the brain dump, fan out parallel workers across this system, the outside world and the ZZ knowledge base, wait for all of them, then synthesise one explore.md (Background · Current state · Rough direction). Main agent, with the fan-out dispatched.

  • flow

    Run the SDLC Agent flow for your team.

  • sdlc-investigate

    Answer one specific question about material inside this system — code, config, specs, data, documents — with grounded file:line citations and calibrated confidence. Read-only. Dispatched by sdlc-explore, one question per worker.

  • sdlc-method

    How every SDLC skill runs — which stages a subagent executes and which the main agent must keep, what to hand a worker, and how to judge what it returns. Read this before running any sdlc-* skill.

  • sdlc-plan-audit

    Audit plan.md — the eleven prose failure modes plus the plan's own contract: AC traceability, task contracts, checks that compile, the format the executor depends on, dependency order and ownership, the walking skeleton, the full-suite gate. Read-only. Dispatched, one round at a time; how many is ro

  • sdlc-plan

    Turn an approved spec into a contract-first, human-executable plan at <initiative>/plan.md — build phases, tasks with contracts and technical acceptance criteria traced to the spec's business ACs, and a full-suite gate. Main agent only; never dispatched.

  • sdlc-recall

    Search the ZZ knowledge base for what earlier work already decided or learned about a question, read the nodes that matter, and report what it means for the decision in front of someone. Read-only. Dispatched by sdlc-explore, one topic per worker.

  • sdlc-research

    Answer one question about the world outside this system — prior art, a standard, how others solved the same shape of problem — with cited external sources and honest confidence. Read-only. Dispatched by sdlc-explore, one question per worker.

  • sdlc-review

    Verify what was built before it ships — first the evidence that every accepted criterion holds, established by running, then a bounded defect sweep in rounds the platform routes to a stop. The sweep is dispatched, one round at a time, because a reviewer who did not write the code is the point; the e

  • sdlc-spec-audit

    Audit spec.md — the eleven prose failure modes plus the spec's own contract: eight components, FR-to-AC traceability, the deliverable contract, frozen values inlined, scope exhaustive. Read-only. Dispatched, one round at a time; how many is routed by evidence.

  • sdlc-spec

    Open the option space with the person, close it to confirmed decisions, and write the agreement at <initiative>/spec.md — what ships, why it is worth building, and what "done" means. Brainstorm and spec are one skill because they are one conversation. Main agent only.

View source on GitHub

More from zhixuan312/zz-stack

All 4 plugins →

Measure a whole plugin by what its real runs did, then — for plugins this team owns — release an authorized improvement and judge it on real use.

9 skills · 1 MCP server

0

zz-core

claude

REQUIRED — ZZ platform baseline for your team — identity, your team's documents and knowledge, the gates, and where each piece of work stands. Required by everything else.

7 skills · 1 MCP server · hooks

0

zz-access

claude

REQUIRED — Access, yours and everybody's: your platform token and the setup for whichever client you work in — plus, if your role carries them, the people and teams behind them. One door; the tools you are offered are the ones your role can execute.

5 skills · 1 MCP server

0

Maintain sdlc?

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 plugins4 plugins