sdlc
claudeSoftware 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.
13 skills
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.
Plugin zz-core from marketplace zz-stack in zhixuan312/zz-stack. Commands read from the repo's manifest — 4 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
zz-authoringWhat every core command that turns a source into a written artifact shares — how the source is chosen from what the reader typed, and the writing rules the result is held to. Loaded by zz-tldr and zz-deck; never run on its own.
breakoutSpin up one named expert teammate for a bounded deep dialogue, keep that conversation out of the main thread, and close by writing the confirmed insights to the ZZ knowledge base. Widens a thin option space before a decision is made.
deckTurn something already written — a spec, a report, a changelog, a thread — into a slide deck that makes an argument, built on the house visual system. Not an outline of the source: a conclusion, the claims that carry it, and one composition per claim.
zz-handoverThe handover every flow ends with. Read one closed initiative — its documents, its telemetry, its refusals — decide what generalises beyond the team that hit it and what matters only to this team, mint the first kind immediately, and propose the second in one gated handover document.
zz-platformThe platform spine every flow's skills stand on: file tools, gates, documents, when a plugin is reached and how it is chosen, sources. Flow-agnostic — load once at the start of ANY flow on the ZZ platform, before the flow's own entry skill. Owned by the platform team; flows never duplicate these rul
zz-routerUse FIRST when the request is delivery work for your team on the ZZ platform — a new capability, a change to a service someone operates, or continuing work already under way. Picks the right installed flow (sdlc-flow, zz-plugin-eval) and follows it, loading it where a session may and telling the per
tldrCompress a long document, thread, or transcript down to what the reader actually needs to act on — the decisions, the open questions, and what changed, not a proportional summary of everything.
zz-coreconnects to: https://api.zz-stack.com/core/mcp
node "${CLAUDE_PLUGIN_ROOT}/scripts/zz-skill-report.mjs"
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.
13 skills
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
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
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.