claude-code-kit 0.52.0__tar.gz → 0.54.0__tar.gz

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "claude-kit",
       "source": "./",
       "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker): install CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json, then run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.",
-      "version": "0.52.0",
+      "version": "0.54.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.52.0",
+  "version": "0.54.0",
   "description": "Cookiecutter-style scaffolder for an autonomous Claude Code SDLC config (no app code, no Docker). `claude-kit init` asks ordered questions and installs CLAUDE.md + .claude/ (rules, the profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates with working memory and a self-improving learnings loop.",
   "author": {
     "name": "Arjunsingh Yadav",

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/CHANGELOG.md

@@ -4,6 +4,134 @@ All notable changes to claude-kit are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/), and the project uses
 [semantic versioning](https://semver.org/).
 
+## [0.54.0] — 2026-06-29
+
+**Safety, correctness, and capability hardening pass.** Two reviews (a fresh practical review and an
+external improvement brief) converged on a set of gaps; every premise was verified against the source
+before acting. No change to the core promise — configuration-only SDLC scaffolding for Claude Code, no
+application code, no Docker, stack-agnostic core, catalog-driven, evidence-backed gates, safe upgrades.
+**0 new agents/skills.**
+
+### Security
+
+- **Learning capture is privacy-hardened (still on by default).** `capture-learnings.sh` now excludes
+  secret-bearing files (`.env`, `*.pem`/`*.key`, `credentials.*`) from the changed-file list, redacts
+  leaked-credential value shapes (private keys, `AKIA…`, `sk_live_…`, Slack/GitHub tokens) from
+  anything handed to the background job, bounds the payload with env-overridable
+  `CLAUDE_KIT_CAPTURE_MAX_LINES` / `CLAUDE_KIT_CAPTURE_MAX_BYTES`, and instructs the job never to record
+  secrets/PII. `init` prints a privacy notice (and a jq-missing caveat); `doctor` warns while capture is
+  wired; the same caveat is documented in `SECURITY.md` and the project README.
+- **No raw slash-command argument interpolation.** `/claude-kit:init` no longer interpolates the
+  textually-substituted `$ARGUMENTS` into any executable shell block; the agent runs the CLI with the
+  user's arguments as separate, individually-quoted argv items. A CI test fails on `$ARGUMENTS` inside a
+  command's fenced code block.
+- **Git guards hardened** against global-option and refspec bypasses (`git -c …` / `git -C …`,
+  `+main`, refspec forms); manual-stdin guards no-op on a TTY.
+
+### Added
+
+- **Command discovery (`detect.py`).** `init`/`upgrade` inspect a populated target for unambiguous
+  package-manager signals and wire the real commands into `CLAUDE.md` — JavaScript (npm·pnpm·yarn·bun)
+  install + present `package.json` scripts, Python (uv·poetry·pdm·hatch) install. Fail-open and
+  conservative (an empty target is a no-op, preserving `init --dry-run` ≡ a real install).
+  `--detect-commands` / `--no-detect-commands` opt in/out; recorded in the stack snapshot.
+- **Transactional upgrade journal.** `upgrade` writes `.claude/config/upgrade-in-progress.json` before
+  mutating and clears it after the new baseline commits; combined with convergent render-and-compare, an
+  interrupted upgrade is finished and cleared by the next run. `doctor` warns while a journal is present;
+  it is gitignored. `merge_install` is not journaled.
+- **JSON Schema validation** for the catalog and persisted artifacts (`jsonschema` is an optional
+  `[schema]` extra; a no-op when absent). Wired into `validate --strict` and the catalog check.
+- **`--json` output** for `validate`, `doctor`, `diff`, `status`, `pipeline validate|status`, and
+  `init --dry-run` via a structured `report` module (human output unchanged).
+- **MCP pin freshness tooling** — an offline CI gate that fails on `@latest`/unpinned servers, plus a
+  scheduled workflow that opens a tracking issue when a pin falls behind the registry.
+
+### Changed
+
+- **`lint-fix.sh` scopes to changed files by default** (git diff vs HEAD + untracked), so a Stop hook
+  never reformats files the user didn't touch. `CLAUDE_KIT_AUTOFIX=1` restores whole-repo formatting;
+  falls back to whole-repo when git is unavailable.
+- **Planned CLI commands are hidden** from `--help` unless `CLAUDE_KIT_EXPERIMENTAL=1` (still marked
+  `[planned]`, still exit non-zero) so they can't be mistaken for working features.
+- **Skill/agent descriptions** front-load their triggers and fit the picker cap; a warn-only CI check
+  reports any that exceed it.
+
+### Docs
+
+- New `docs/KNOWN_LIMITATIONS.md` (guards are best-effort, not a security boundary; command discovery
+  scope; non-atomic first install; convergent/journalled upgrades) + a README "Who this is for" section
+  and reconciliation/reference fixes.
+
+## [0.53.0] — 2026-06-28
+
+**Adopt the verified wins from an exhaustive review of three GitHub orgs — `Netflix`, `aws`, and
+`apple`** (all **1,214** public repos: Netflix 234 · aws 549 · apple 431). Every repo was surveyed (34
+agents over every page across the three orgs — no repo skipped), candidates deep-read for license +
+transferable practice, and the shortlist **adversarially verified** against the live source. These orgs
+are overwhelmingly SDKs, CLIs, cloud-product code, and running services with nothing transferable to a
+config scaffolder — but the review surfaced a real **gap**: the kit had `agent-resilience` (the coding
+agent's own retries) yet **no service-level resilience rule at all**. **7 adoptions across the three
+orgs; 1 new rule (`resilience-engineering`), the rest extensions to existing files — 0 new
+agents/skills** (skill counts unchanged at 104/56/48; MCP fragments unchanged at 17; **core rules
+23 → 24**). Everything re-derived **in prose, never vendored**; all sources Apache-2.0 or MIT/Apache-2.0.
+
+A note on method: the per-repo deep-dive initially skipped several famous repos on "the source is a
+library/tool, not documentation" grounds — but the kit ships *prose*, so a Java library or a C++ database
+is a perfectly valid *source* for a re-derived discipline. The adversarial-verify pass (one skeptic per
+item, reading the live README + license) judged the **discipline**, not the artifact type, and confirmed
+all seven hold, are stack-agnostic, genuinely new, and permissively licensed.
+
+Rules:
+
+- **`resilience-engineering.md`** (NEW — the kit's first service-level resilience rule, explicitly
+  distinct from `agent-resilience.md`, which is about the coding agent's own machinery). Three sections:
+  (1) **stability patterns** at every remote-call boundary — timeout + deadline budget, retry with
+  budget/jitter, circuit breaker, bulkhead/isolation, backpressure, load shedding, graceful
+  degradation — plus **adaptive concurrency limiting** (TCP-congestion-control + Little's Law to find the
+  limit from latency instead of hand-tuning it, server- and client-side, with priority partitioning;
+  from the Apache-2.0 `Netflix/concurrency-limits`); (2) **distributed-time correctness** — never compare
+  raw wall-clocks across nodes; treat "now" as a `[earliest, latest]` interval and commit-wait for
+  cross-node ordering (from the MIT/Apache-2.0 `aws/clock-bound` + Google TrueTime); (3) **chaos
+  engineering** — steady-state hypothesis, vary real-world events, minimize blast radius with an automated
+  abort, prefer production, run continuously (from the Apache-2.0 `Netflix/chaosmonkey` + Principles of
+  Chaos).
+- **`devops-observability.md`** — a **failure-domain-aware progressive rollout** section: update one
+  failure domain (zone/region/rack/cell/shard) at a time to contain blast radius, accelerate in
+  exponential batches with a readiness gate between them, roll back newest-first to escape a bad revision
+  fastest, and pause-on-alarm automatically (from the Apache-2.0 `aws/zone-aware-controllers-for-k8s`).
+- **`testing.md`** — a **Deterministic Simulation Testing** section for concurrency/distributed-system
+  bugs: funnel all nondeterminism (clock, RNG, scheduling, IO, network) through injectable seams, drive
+  the system from a single seed in single-threaded virtual time so a failing run replays bit-for-bit, and
+  inject faults aggressively in-sim (the "buggify" idea); complements fuzzing + property-based testing
+  (from the Apache-2.0 `apple/foundationdb`).
+
+Skills:
+
+- **`spec-driven-development`** — a third proposal mode beyond full-spec and delta-spec: an **RFC track**
+  for one-way-door changes (public/cross-service APIs). Adds working-backwards artifacts (write the future
+  CHANGELOG/README first), a designated API **bar-raiser** with interface veto, a staged lifecycle
+  (feedback → final-comment → API sign-off → implementation planning), and separation of API approval from
+  implementation approval (from the Apache-2.0 `aws/aws-cdk-rfcs`).
+- **`security-and-hardening`** — a **Continuous Least-Privilege** section: least privilege is a decay
+  loop, not a one-time grant — periodically audit which grants/scopes/roles were *actually exercised* over
+  a trailing window, auto-revoke the unused, snapshot policies for fast rollback, and keep an exempt-list
+  for break-glass access (from the Apache-2.0 `Netflix/repokid`).
+
+Docs/counts: core rules **23 → 24** across `README.md` (5 anchors), `CLAUDE.md`, and
+`docs/architecture.md`; `agent-resilience.md` cross-links the new service-level rule (and vice versa); a
+new Influences row + depth blurb (kept to the latest three reviews — the microsoft 0.50 blurb rolls off).
+
+What we **did not** add (already covered, or fails the bar): `Netflix/chaosmonkey`-the-tool,
+`Netflix/dispatch` (archived incident-management *app* — covered by `incident-postmortem` +
+`incident-responder`), `Netflix/maestro` (a workflow-orchestration *platform*, like Airflow/Temporal —
+a tool to use, not a practice), `Netflix/security-bulletins` (disclosure output, covered by the security
+layer); the AWS service/SDK material — `aws-sam-cli`, `aws-pdk`, `aws-lakeformation-best-practices`,
+`aws-networking-best-practices`, `aws-sam-cli-pipeline-init-templates`, `device-storelibrary-cpp`,
+`mcp-proxy-for-aws` (AWS-IAM auth transport, not a tool-exposing MCP server); and `apple`'s
+`apple-root-program` (PKI/CA policy, no license), `batch-processing-gateway` (a Spark-on-K8s service), and
+`pkl-evolution` (a language-evolution RFC — redundant with the richer `aws-cdk-rfcs` RFC track adopted
+above).
+
 ## [0.52.0] — 2026-06-28
 
 **Adopt the verified wins from an exhaustive review of the entire `facebook` (Meta) GitHub org** (all

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/CLAUDE.md

@@ -20,9 +20,9 @@ distributed two ways from one source of truth:
 | `.claude-plugin/marketplace.json` | Marketplace entry so `/plugin marketplace add` works |
 | `agents/` | SDLC pipeline subagents (auto-discovered by the plugin); each carries a `tier:` field |
 | `skills/` | Agent skills (auto-discovered by the plugin); `skills/sdlc/` is the `/sdlc` entrypoint |
-| `commands/` | Slash commands: `/claude-kit:init`, `:sdlc`, `:status` (init prefers the pip CLI, falls back to `init.sh`; sdlc delegates to the `sdlc` skill) |
+| `commands/` | Slash commands: `/claude-kit:init`, `:sdlc`, `:status`, `:abort` (init prefers the pip CLI, falls back to `init.sh`; sdlc delegates to the `sdlc` skill; abort tears down an in-progress `/sdlc` run) |
 | `hooks/hooks.json` + `hooks/scripts/` | Event hooks (paths via `${CLAUDE_PLUGIN_ROOT}`) |
-| `rules/` | The 23-file stack-agnostic engineering rule set (scaffolded into `.claude/rules/`), including the agent-operation rules (reasoning, guardrails, resilience, goal-setting, human-in-the-loop, model-tiers, evals, tool-design — see `docs/agentic-patterns.md`) and the org-core rules `autonomy-levels` + `risk-classification` (see `docs/org-capabilities.md`) |
+| `rules/` | The 24-file stack-agnostic engineering rule set (scaffolded into `.claude/rules/`), including the agent-operation rules (reasoning, guardrails, resilience, goal-setting, human-in-the-loop, model-tiers, evals, tool-design — see `docs/agentic-patterns.md`), the service-level `resilience-engineering` rule, and the org-core rules `autonomy-levels` + `risk-classification` (see `docs/org-capabilities.md`) |
 | `catalog/` | **Data-driven registry** — `stacks.yaml` · `profiles.yaml` · `mcp.yaml` · `org.yaml`. The only thing that decides what `resolve()` installs. Adding a stack/profile/server/pack is a data change here. |
 | `templates/` | `CLAUDE.md`, `CLAUDE.stack.md.tmpl`, `README.claude-sdlc.md.tmpl`, `CONTINUITY.template.md`, `settings.json`, `artifacts/`, `agent-memory/` seed |
 | `templates/stacks/<kind>/<id>/` | Per-stack **overlay** content: `rules/` (+ `agents/` for DB stacks). **No application code, no Docker** — the only place stack-specific content lives. |
@@ -49,7 +49,7 @@ root are read directly by the plugin **and** bundled into the wheel (mapped to
    and is wired up via `catalog/stacks.yaml` — never leak it into the agnostic core, and never add
    application code or Docker anywhere.
 2. **Reference rules by their canonical filename** under `.claude/rules/…` (that's where they
-   land in a user project). The current core rule set is the 23 files in `rules/` (org policy/vibe
+   land in a user project). The current core rule set is the 24 files in `rules/` (org policy/vibe
    rules under `templates/org/rules/` install only in organization scope).
 3. **Plugin components live at the repo root**, never inside `.claude-plugin/` (only the
    manifest goes there).

claude_code_kit-0.52.0/README.md → claude_code_kit-0.54.0/PKG-INFO

@@ -1,3 +1,36 @@
+Metadata-Version: 2.4
+Name: claude-code-kit
+Version: 0.54.0
+Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
+Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
+Project-URL: Repository, https://github.com/ajyadav013/claude-kit
+Project-URL: Issues, https://github.com/ajyadav013/claude-kit/issues
+Author: Arjunsingh Yadav
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agentic,agents,automation,claude,claude-code,code-review,cookiecutter,fastapi,generator,orchestration,react,scaffold,sdlc,testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.9
+Requires-Dist: jinja2>=3.1
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: typer>=0.12
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == 'dev'
+Requires-Dist: jsonschema>=4.0; extra == 'dev'
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Requires-Dist: shellcheck-py>=0.10; extra == 'dev'
+Requires-Dist: twine>=5.0; extra == 'dev'
+Provides-Extra: schema
+Requires-Dist: jsonschema>=4.0; extra == 'schema'
+Description-Content-Type: text/markdown
+
 <div align="center">
 
 # claude-kit
@@ -36,14 +69,27 @@ advance until each phase's quality gate passes**. You drive it all with one comm
 **`/sdlc <your task>`**.
 
 It ships **no application code and needs no Docker** — only the rules, agents, skills, and gates that
-govern *how* the work gets done. Choose your stack, rigor, and team scope at `init`; everything else
-adapts.
+govern *how* the work gets done. (Some skills *help Claude write* your Dockerfiles, CI, or k8s manifests
+when you ask — but the scaffolder itself installs none.) Choose your stack, rigor, and team scope at
+`init`; everything else adapts.
 
 > Inspired by the autonomous-SDLC idea, rebuilt from the ground up **for Claude Code**, and kept small
 > by a **reuse-first** policy — see [what we adopted](#influences--what-we-adopted) and from where.
 
 ---
 
+## Who this is for
+
+**Use claude-kit if** you drive real repository changes with Claude Code and want a repeatable
+spec → review → test → security → PR workflow whose quality gates won't advance on an unproven verdict.
+
+**Skip it if** you want a small prompt pack, don't want project config written into your repo, or need a
+standalone runtime/daemon. claude-kit is **configuration for Claude Code**, not a separate runtime — and
+its guard hooks are convenience guardrails (they need `jq` + a POSIX shell and no-op without them), **not
+a hardened security boundary**. See [Known limitations](docs/KNOWN_LIMITATIONS.md).
+
+---
+
 ## Features
 
 The whole product at a glance — one line each. Expand **[Feature details](#feature-details)** (below
@@ -54,11 +100,11 @@ Quick start) for the full breakdown of any row.
 | 🔁 **Pipeline & quality gates** | Gate-enforced progression (zero open Critical/High/Medium to advance), per-profile gate sets, a fast-track for small changes, and an anti-sycophancy `devils-advocate` pass |
 | 🤖 **Agent roster** | **28** tiered agents + per-database overlays + **6** org personas, led by an Orchestrator that never writes code |
 | 🔍 **Self-verification & review** | RARV green-Verify (real commands, not imagined), blind parallel review, and read-only risk classification |
-| 📐 **Rules & skills** | **23** stack-agnostic core rules (incl. 8 agent-operation rules) + **104** context-activated skills (56 core + 48 stack-collection) |
+| 📐 **Rules & skills** | **24** stack-agnostic core rules (incl. 8 agent-operation rules) + **104** context-activated skills (56 core + 48 stack-collection) |
 | 🧱 **Stacks & overlays** | Stack-agnostic core + **10** overlay rule sets (React · FastAPI · Go · Postgres · Mongo) wired to your exact commands, incl. a full React design system |
 | 🎚️ **Profiles, scopes & org** | **3** rigor profiles · **3** scopes · **5** autonomy levels · **7** org packs + **10** policy rules |
 | 🧠 **Memory & learning** | Working memory across context compaction + a cost-aware learnings loop (`capture_mode`) so the same mistake isn't repeated |
-| 🛠️ **Hooks & guards** | **17** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
+| 🛠️ **Hooks & guards** | **18** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
 | 📦 **Distribution & lifecycle** | Plugin **and** pip from one source, **17** ready MCP fragments, and edit-preserving `upgrade` |
 | ♻️ **Reuse-first by design** | Adopt-only-the-new reviews, opt-in LLM/AI security (OWASP LLM Top 10), a worked example + self-test matrix |
 
@@ -248,7 +294,7 @@ need.
 
 <br>
 
-- **23 stack-agnostic core rules** in [`rules/`](rules/) — `mandatory-workflow`, `quality-gates`,
+- **24 stack-agnostic core rules** in [`rules/`](rules/) — `mandatory-workflow`, `quality-gates`,
   `rarv-cycle`, `continuity`, plus eight agent-operation rules and `autonomy-levels` +
   `risk-classification` (see [`docs/agentic-patterns.md`](docs/agentic-patterns.md)).
 - **104 on-demand skills** in [`skills/`](skills/) (56 core + 48 stack-collection) — spec-driven dev, planning, TDD, debugging, code
@@ -308,7 +354,7 @@ need.
 
 <br>
 
-- **17 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
+- **18 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
   `guard-secrets`, `guard-destructive-git`, `lint-fix`, `type-check`, and `validate-settings` run
   deterministically.
 - **Advisory, never-blocking warnings** — `warn-llm-io`, `warn-large-edits`, `warn-missing-tests`, and
@@ -407,7 +453,7 @@ owned gates, and the rule that **no gate passes on an unproven verdict**.
 | **[wshobson/agents](https://github.com/wshobson/agents)** & similar agent collections | Large libraries of individual subagent prompts you pick from | A **smaller, opinionated set wired into a sequenced pipeline with owned quality gates** — agents aren't a menu, they're stages that hand off and block on each other. Adopt-by-reuse, not by accumulation. |
 | **[GitHub spec-kit](https://github.com/github/spec-kit)** | A spec-driven workflow (constitution → spec → tasks → analyze) | The same coverage-gate idea (the `story-planner` 1f gate + `task-tracker-sync`) **absorbed into a broader** lifecycle that also covers review, security, build, test, release, and observability gates. Complementary, wider scope. |
 | **claude-flow / multi-agent runtimes** | Runtime orchestrators that *execute* swarms of agents | **Portable configuration**, not a running process — the orchestration is described in rules the host (Claude Code) executes. No daemon, no lock-in, no app code. |
-| **dotfiles / `CLAUDE.md` starters** | A single rules file or settings snippet | A **catalog-driven generator**: resolves your stack/profile/scope into the right subset of 23 rules, 28 agents, 104 skills, gates, and hooks, kept **upgradeable** (`claude-kit upgrade` preserves your edits via owner + checksum). |
+| **dotfiles / `CLAUDE.md` starters** | A single rules file or settings snippet | A **catalog-driven generator**: resolves your stack/profile/scope into the right subset of 24 rules, 28 agents, 104 skills, gates, and hooks, kept **upgradeable** (`claude-kit upgrade` preserves your edits via owner + checksum). |
 
 **Choose claude-kit when** you want a consistent, reviewable, **gate-enforced** autonomous-SDLC setup
 that's the same across every repo and stack, installs in seconds, ships nothing you have to run, and
@@ -490,6 +536,7 @@ non-duplicative gaps**, minimally and catalog-wired.
 | **[microsoft](https://github.com/microsoft) org review** (all 8,147 repos) | OWASP Agentic Top-10 (ASI01–ASI10) agent threats; agent-aware evals (multi-judge panels, multi-turn degradation, tool-vs-response grading); validator-in-the-loop + Medprompt prompting; sandbox policy schema & layered prompt-injection defense; approval-gate implementation; security-lint layer & SBOM; operationalized GenAI red-teaming; priority-based prompt pruning; quantified-lines PR sizing; first-party MCP servers | Extensions across `agent-guardrails` (ASI01–ASI10 + sandbox policy + injection layers), `evals` (§3 panels, §8 multi-turn), `reasoning-techniques`, `human-in-the-loop`, `linting-and-formatting`, `threat-model`, `security-and-hardening` (SBOM), `context-engineering`, `code-review-and-quality` + 4 MCP fragments (Azure · Azure DevOps · MS Learn · Wassette) — **0 new agents/skills/rules** (from agent-governance-toolkit · mxc · llmail-inject-challenge · lost_in_conversation · llm-as-judge · EvalsforAgentsInterop · promptbase · dsl-copilot · agents-humanoversight · PyRIT · eslint-plugin-sdl · sbom-tool · vscode-prompt-tsx · PullRequestQuantifier) | `0.50.0` |
 | **[google](https://github.com/google) org review** (all 2,881 repos) | Reproducible-build verification & source-level missing-patch detection; secure-by-construction injection defense; archive-extraction & ReDoS hardening; multi-party authorization / breakglass; coverage-guided & continuous fuzzing; parameterized + semantic-equality + parallel/flaky testing; compile-time logic-bug & license-header lint layers + deterministic block sorting; multi-window burn-rate alerting & log rate-limiting; long-document extraction; prompt-as-code; statistical browser benchmarking; durable atomic writes; record-replay API testing; first-party SecOps MCP servers | Prose extensions across `security-and-hardening` (reproducible-build · missing-patch · secure-by-construction · archive · ReDoS), `human-in-the-loop` (MPA/breakglass), `testing` (fuzzing · parameterized · semantic-equality · parallel/flaky), `linting-and-formatting` (logic-bug + license-header layers · block sorting), `devops-observability` (burn-rate · log rate-limit), `context-engineering` (long-doc extraction), `reasoning-techniques` (prompt-as-code), `performance-optimization` (statistical benchmarking), `tool-design` (durable atomic writes), `api-integration` (record-replay) + **4 first-party SecOps MCP fragments** (Chronicle SIEM · GTI · SCC · SOAR) — **0 new agents/skills/rules** (from oss-rebuild · vanir · safe-active-record/mug · safearchive · re2 · building-secure-and-reliable-systems · patrick · go-cmp · atheris/honggfuzz/clusterfuzzlite · gtest-parallel · error-prone · addlicense · keep-sorted · prometheus-slo-burn · flogger · langextract · dotprompt · tachometer · renameio · test-server · mcp-security) | `0.51.0` |
 | **[facebook](https://github.com/facebook) (Meta) org review** (all 168 repos) | Interprocedural taint / data-flow security analysis (source→sink across functions); continuous A/B performance-regression CI gate; defense-in-depth agent-sandbox enforcement (argument validation + OS-level backstop) | Prose extensions to `linting-and-formatting` (taint/data-flow layer), `devops-observability` (perf-regression gate), `agent-guardrails` (§4 layered sandbox enforcement) — **0 new agents/skills/rules** (from pyre-check/Pysa · mariana-trench · FAI-PEP · mcpguard-dynamic; the org is mostly libraries/frameworks, so the verify pass *dropped* the rest — `DNE-TaaC`, `mbt`, plus already-covered `infer`/`mariana-trench`-as-tool, `fbt`, `memlab`, …) | `0.52.0` |
+| **[Netflix](https://github.com/Netflix) · [aws](https://github.com/aws) · [apple](https://github.com/apple) org review** (all **1,214** repos) | Service-level resilience the kit lacked entirely — stability patterns (timeout/retry-budget/circuit-breaker/bulkhead) + adaptive concurrency limiting, chaos engineering, and bounded-clock distributed time; failure-domain-aware progressive rollout; deterministic simulation testing; a formal RFC process (working-backwards + API bar-raiser); continuous usage-based least-privilege | The **new `resilience-engineering` rule** (chaos + stability patterns + bounded clocks, from `Netflix/concurrency-limits` · `Netflix/chaosmonkey` · `aws/clock-bound`); plus prose extensions to `devops-observability` (failure-domain rollout, from `aws/zone-aware-controllers-for-k8s`), `testing` (deterministic simulation testing, from `apple/foundationdb`), `spec-driven-development` (RFC track, from `aws/aws-cdk-rfcs`), and `security-and-hardening` (continuous least-privilege, from `Netflix/repokid`) — **1 new rule, 0 new agents/skills** (the orgs are overwhelmingly SDKs/CLIs/services, so the survey kept only 7 of 1,214) | `0.53.0` |
 
 > Each adoption is detailed in the [CHANGELOG](CHANGELOG.md) — including, for every review, what we
 > deliberately **did not** add because the kit already covered it.
@@ -499,21 +546,6 @@ non-duplicative gaps**, minimally and catalog-wired.
 
 <br>
 
-**🟦 microsoft org review → agentic-AI hardening (0.50.0).** We reviewed **all 8,147 repos** in the
-Microsoft org (165 survey agents over every page → deep-dive the top candidates → adversarially verify
-the shortlist). The vast majority — SDKs, samples, Azure-product code, ML infra, OS/editor — carried
-nothing transferable, and the verify pass *dropped* two plausible picks (`ToolTalk`, whose
-ground-truth-sequence grading contradicts `evals`' "grade outcomes, not paths"; and `prompty`, an
-LLM-app product, not an SDLC practice). Eighteen survived — all **prose extensions to existing files**,
-zero new agents/skills/rules: the OWASP **Agentic Top-10 (ASI01–ASI10)** mapping, a sandbox **policy
-schema**, and layered prompt-injection defense in `agent-guardrails`; agent-aware evals (multi-judge
-panels in §3, multi-turn degradation in §8) in `evals`; validator-in-the-loop + Medprompt in
-`reasoning-techniques`; approval-gate implementation in `human-in-the-loop`; a security-lint layer in
-`linting-and-formatting`; operationalized GenAI red-teaming in `threat-model`; SBOM generation in
-`security-and-hardening`; priority-based prompt pruning in `context-engineering`; quantified-lines PR
-sizing in `code-review-and-quality`; and **4 first-party MCP fragments** (Azure · Azure DevOps · MS
-Learn · Wassette).
-
 **🔴 google org review → 21 hardening & testing patterns (0.51.0).** We reviewed **all 2,881 repos** in
 the Google org (60 survey agents over every page → deep-dive the top ~300 candidates → adversarially
 verify the shortlist). The vast majority — Android/Kotlin, C++ libraries, ML frameworks, language
@@ -550,6 +582,27 @@ to cancel environment noise, gate on the relative delta) in `devops-observabilit
 **defense-in-depth agent-sandbox enforcement** (argument-validation layer + OS-level eBPF/seccomp backstop
 *below* the existing declarative policy) in `agent-guardrails` §4 (from `mcpguard-dynamic`).
 
+**⬛🟧 Netflix · aws · apple org review → resilience engineering & more (0.53.0).** We reviewed **all
+1,214 repos** across the three orgs (34 survey agents over every page → deep-dive the candidates →
+adversarially verify the shortlist). The orgs are overwhelmingly SDKs, CLIs, cloud-product code, and
+running services — almost nothing transferable to a config scaffolder — and the verify pass scrutinized
+each survivor against the live README + license. **Seven** genuine, stack-agnostic, permissively-licensed
+disciplines survived. The biggest finding was a real **gap**: the kit had `agent-resilience` (the coding
+agent's own retries) but **no service-level resilience rule at all**, so this review adds the kit's
+**first new rule in many releases — `resilience-engineering`**: stability patterns
+(timeout/retry-budget/circuit-breaker/bulkhead/load-shedding/fallback) + **adaptive concurrency limiting**
+(TCP-congestion-control + Little's Law, from `Netflix/concurrency-limits`), **chaos engineering**
+(steady-state hypothesis, blast-radius control, automated abort, from `Netflix/chaosmonkey`), and
+**bounded-clock distributed time** (timestamps as `[earliest, latest]` + commit-wait, from
+`aws/clock-bound`). The other four are prose extensions to existing files: **failure-domain-aware
+progressive rollout** (one zone/region/cell at a time, exponential batches, reverse-order rollback) in
+`devops-observability` (from `aws/zone-aware-controllers-for-k8s`); **deterministic simulation testing**
+(single-seed control of all nondeterminism + in-sim fault injection) in `testing` (from
+`apple/foundationdb`); a formal **RFC track** for one-way-door API changes (working-backwards artifacts +
+API bar-raiser + staged sign-off) in `spec-driven-development` (from `aws/aws-cdk-rfcs`); and
+**continuous, usage-based least-privilege** (audit exercised grants → auto-revoke the unused → versioned
+rollback) in `security-and-hardening` (from `Netflix/repokid`).
+
 </details>
 
 > **Comparing claude-kit to native subagents / Agent Teams, agent collections, spec-kit, or
@@ -603,7 +656,7 @@ to cancel environment noise, gate on the relative delta) in `devops-observabilit
 
 ## Rules & skills
 
-**Rules** ([`rules/`](rules/)) are the 23 stack-agnostic contracts every agent obeys — the
+**Rules** ([`rules/`](rules/)) are the 24 stack-agnostic contracts every agent obeys — the
 `mandatory-workflow` pipeline, `quality-gates`, `rarv-cycle`, `continuity`, `documentation`,
 `testing`, the eight agent-operation rules (`reasoning-techniques`, `agent-guardrails`,
 `agent-resilience`, `goal-setting-and-monitoring`, `human-in-the-loop`, `model-tiers`, `evals`,
@@ -754,7 +807,7 @@ build attestations** for supply-chain provenance. Report vulnerabilities private
 ```
 claude-kit/
 ├── .claude-plugin/        plugin.json + marketplace.json
-├── agents/                28 SDLC agents          rules/        23 engineering rules
+├── agents/                28 SDLC agents          rules/        24 engineering rules
 ├── skills/                on-demand skills        templates/    CLAUDE.md, settings, artifacts, memory seeds
 ├── commands/              /claude-kit:* commands  hooks/        hooks.json + scripts/
 ├── catalog/         stacks·profiles·mcp·org       templates/stacks/  per-stack overlay rules + agents

claude_code_kit-0.52.0/PKG-INFO → claude_code_kit-0.54.0/README.md

@@ -1,33 +1,3 @@
-Metadata-Version: 2.4
-Name: claude-code-kit
-Version: 0.52.0
-Summary: Cookiecutter-style scaffolder for an autonomous Claude Code SDLC configuration (no app code, no Docker). Asks ordered questions and installs CLAUDE.md + .claude/ (rules, the chosen profile's agents/skills, hooks, artifact templates) + optional .mcp.json; run /sdlc to drive spec → review → build → test → security → ship through profile-aware quality gates, working memory, and a self-improving learnings loop.
-Project-URL: Homepage, https://github.com/ajyadav013/claude-kit
-Project-URL: Repository, https://github.com/ajyadav013/claude-kit
-Project-URL: Issues, https://github.com/ajyadav013/claude-kit/issues
-Author: Arjunsingh Yadav
-License-Expression: MIT
-License-File: LICENSE
-Keywords: agentic,agents,automation,claude,claude-code,code-review,cookiecutter,fastapi,generator,orchestration,react,scaffold,sdlc,testing
-Classifier: Development Status :: 4 - Beta
-Classifier: Environment :: Console
-Classifier: Intended Audience :: Developers
-Classifier: Programming Language :: Python :: 3
-Classifier: Topic :: Software Development
-Classifier: Topic :: Software Development :: Quality Assurance
-Requires-Python: >=3.9
-Requires-Dist: jinja2>=3.1
-Requires-Dist: pyyaml>=6.0
-Requires-Dist: typer>=0.12
-Provides-Extra: dev
-Requires-Dist: build>=1.2; extra == 'dev'
-Requires-Dist: mypy>=1.10; extra == 'dev'
-Requires-Dist: pytest>=8.0; extra == 'dev'
-Requires-Dist: ruff>=0.6; extra == 'dev'
-Requires-Dist: shellcheck-py>=0.10; extra == 'dev'
-Requires-Dist: twine>=5.0; extra == 'dev'
-Description-Content-Type: text/markdown
-
 <div align="center">
 
 # claude-kit
@@ -66,14 +36,27 @@ advance until each phase's quality gate passes**. You drive it all with one comm
 **`/sdlc <your task>`**.
 
 It ships **no application code and needs no Docker** — only the rules, agents, skills, and gates that
-govern *how* the work gets done. Choose your stack, rigor, and team scope at `init`; everything else
-adapts.
+govern *how* the work gets done. (Some skills *help Claude write* your Dockerfiles, CI, or k8s manifests
+when you ask — but the scaffolder itself installs none.) Choose your stack, rigor, and team scope at
+`init`; everything else adapts.
 
 > Inspired by the autonomous-SDLC idea, rebuilt from the ground up **for Claude Code**, and kept small
 > by a **reuse-first** policy — see [what we adopted](#influences--what-we-adopted) and from where.
 
 ---
 
+## Who this is for
+
+**Use claude-kit if** you drive real repository changes with Claude Code and want a repeatable
+spec → review → test → security → PR workflow whose quality gates won't advance on an unproven verdict.
+
+**Skip it if** you want a small prompt pack, don't want project config written into your repo, or need a
+standalone runtime/daemon. claude-kit is **configuration for Claude Code**, not a separate runtime — and
+its guard hooks are convenience guardrails (they need `jq` + a POSIX shell and no-op without them), **not
+a hardened security boundary**. See [Known limitations](docs/KNOWN_LIMITATIONS.md).
+
+---
+
 ## Features
 
 The whole product at a glance — one line each. Expand **[Feature details](#feature-details)** (below
@@ -84,11 +67,11 @@ Quick start) for the full breakdown of any row.
 | 🔁 **Pipeline & quality gates** | Gate-enforced progression (zero open Critical/High/Medium to advance), per-profile gate sets, a fast-track for small changes, and an anti-sycophancy `devils-advocate` pass |
 | 🤖 **Agent roster** | **28** tiered agents + per-database overlays + **6** org personas, led by an Orchestrator that never writes code |
 | 🔍 **Self-verification & review** | RARV green-Verify (real commands, not imagined), blind parallel review, and read-only risk classification |
-| 📐 **Rules & skills** | **23** stack-agnostic core rules (incl. 8 agent-operation rules) + **104** context-activated skills (56 core + 48 stack-collection) |
+| 📐 **Rules & skills** | **24** stack-agnostic core rules (incl. 8 agent-operation rules) + **104** context-activated skills (56 core + 48 stack-collection) |
 | 🧱 **Stacks & overlays** | Stack-agnostic core + **10** overlay rule sets (React · FastAPI · Go · Postgres · Mongo) wired to your exact commands, incl. a full React design system |
 | 🎚️ **Profiles, scopes & org** | **3** rigor profiles · **3** scopes · **5** autonomy levels · **7** org packs + **10** policy rules |
 | 🧠 **Memory & learning** | Working memory across context compaction + a cost-aware learnings loop (`capture_mode`) so the same mistake isn't repeated |
-| 🛠️ **Hooks & guards** | **17** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
+| 🛠️ **Hooks & guards** | **18** event hooks — blocking safety guards vs. advisory warnings — that no-op gracefully without `jq` |
 | 📦 **Distribution & lifecycle** | Plugin **and** pip from one source, **17** ready MCP fragments, and edit-preserving `upgrade` |
 | ♻️ **Reuse-first by design** | Adopt-only-the-new reviews, opt-in LLM/AI security (OWASP LLM Top 10), a worked example + self-test matrix |
 
@@ -278,7 +261,7 @@ need.
 
 <br>
 
-- **23 stack-agnostic core rules** in [`rules/`](rules/) — `mandatory-workflow`, `quality-gates`,
+- **24 stack-agnostic core rules** in [`rules/`](rules/) — `mandatory-workflow`, `quality-gates`,
   `rarv-cycle`, `continuity`, plus eight agent-operation rules and `autonomy-levels` +
   `risk-classification` (see [`docs/agentic-patterns.md`](docs/agentic-patterns.md)).
 - **104 on-demand skills** in [`skills/`](skills/) (56 core + 48 stack-collection) — spec-driven dev, planning, TDD, debugging, code
@@ -338,7 +321,7 @@ need.
 
 <br>
 
-- **17 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
+- **18 event hook scripts** in [`hooks/`](hooks/) enforce the pipeline outside the model —
   `guard-secrets`, `guard-destructive-git`, `lint-fix`, `type-check`, and `validate-settings` run
   deterministically.
 - **Advisory, never-blocking warnings** — `warn-llm-io`, `warn-large-edits`, `warn-missing-tests`, and
@@ -437,7 +420,7 @@ owned gates, and the rule that **no gate passes on an unproven verdict**.
 | **[wshobson/agents](https://github.com/wshobson/agents)** & similar agent collections | Large libraries of individual subagent prompts you pick from | A **smaller, opinionated set wired into a sequenced pipeline with owned quality gates** — agents aren't a menu, they're stages that hand off and block on each other. Adopt-by-reuse, not by accumulation. |
 | **[GitHub spec-kit](https://github.com/github/spec-kit)** | A spec-driven workflow (constitution → spec → tasks → analyze) | The same coverage-gate idea (the `story-planner` 1f gate + `task-tracker-sync`) **absorbed into a broader** lifecycle that also covers review, security, build, test, release, and observability gates. Complementary, wider scope. |
 | **claude-flow / multi-agent runtimes** | Runtime orchestrators that *execute* swarms of agents | **Portable configuration**, not a running process — the orchestration is described in rules the host (Claude Code) executes. No daemon, no lock-in, no app code. |
-| **dotfiles / `CLAUDE.md` starters** | A single rules file or settings snippet | A **catalog-driven generator**: resolves your stack/profile/scope into the right subset of 23 rules, 28 agents, 104 skills, gates, and hooks, kept **upgradeable** (`claude-kit upgrade` preserves your edits via owner + checksum). |
+| **dotfiles / `CLAUDE.md` starters** | A single rules file or settings snippet | A **catalog-driven generator**: resolves your stack/profile/scope into the right subset of 24 rules, 28 agents, 104 skills, gates, and hooks, kept **upgradeable** (`claude-kit upgrade` preserves your edits via owner + checksum). |
 
 **Choose claude-kit when** you want a consistent, reviewable, **gate-enforced** autonomous-SDLC setup
 that's the same across every repo and stack, installs in seconds, ships nothing you have to run, and
@@ -520,6 +503,7 @@ non-duplicative gaps**, minimally and catalog-wired.
 | **[microsoft](https://github.com/microsoft) org review** (all 8,147 repos) | OWASP Agentic Top-10 (ASI01–ASI10) agent threats; agent-aware evals (multi-judge panels, multi-turn degradation, tool-vs-response grading); validator-in-the-loop + Medprompt prompting; sandbox policy schema & layered prompt-injection defense; approval-gate implementation; security-lint layer & SBOM; operationalized GenAI red-teaming; priority-based prompt pruning; quantified-lines PR sizing; first-party MCP servers | Extensions across `agent-guardrails` (ASI01–ASI10 + sandbox policy + injection layers), `evals` (§3 panels, §8 multi-turn), `reasoning-techniques`, `human-in-the-loop`, `linting-and-formatting`, `threat-model`, `security-and-hardening` (SBOM), `context-engineering`, `code-review-and-quality` + 4 MCP fragments (Azure · Azure DevOps · MS Learn · Wassette) — **0 new agents/skills/rules** (from agent-governance-toolkit · mxc · llmail-inject-challenge · lost_in_conversation · llm-as-judge · EvalsforAgentsInterop · promptbase · dsl-copilot · agents-humanoversight · PyRIT · eslint-plugin-sdl · sbom-tool · vscode-prompt-tsx · PullRequestQuantifier) | `0.50.0` |
 | **[google](https://github.com/google) org review** (all 2,881 repos) | Reproducible-build verification & source-level missing-patch detection; secure-by-construction injection defense; archive-extraction & ReDoS hardening; multi-party authorization / breakglass; coverage-guided & continuous fuzzing; parameterized + semantic-equality + parallel/flaky testing; compile-time logic-bug & license-header lint layers + deterministic block sorting; multi-window burn-rate alerting & log rate-limiting; long-document extraction; prompt-as-code; statistical browser benchmarking; durable atomic writes; record-replay API testing; first-party SecOps MCP servers | Prose extensions across `security-and-hardening` (reproducible-build · missing-patch · secure-by-construction · archive · ReDoS), `human-in-the-loop` (MPA/breakglass), `testing` (fuzzing · parameterized · semantic-equality · parallel/flaky), `linting-and-formatting` (logic-bug + license-header layers · block sorting), `devops-observability` (burn-rate · log rate-limit), `context-engineering` (long-doc extraction), `reasoning-techniques` (prompt-as-code), `performance-optimization` (statistical benchmarking), `tool-design` (durable atomic writes), `api-integration` (record-replay) + **4 first-party SecOps MCP fragments** (Chronicle SIEM · GTI · SCC · SOAR) — **0 new agents/skills/rules** (from oss-rebuild · vanir · safe-active-record/mug · safearchive · re2 · building-secure-and-reliable-systems · patrick · go-cmp · atheris/honggfuzz/clusterfuzzlite · gtest-parallel · error-prone · addlicense · keep-sorted · prometheus-slo-burn · flogger · langextract · dotprompt · tachometer · renameio · test-server · mcp-security) | `0.51.0` |
 | **[facebook](https://github.com/facebook) (Meta) org review** (all 168 repos) | Interprocedural taint / data-flow security analysis (source→sink across functions); continuous A/B performance-regression CI gate; defense-in-depth agent-sandbox enforcement (argument validation + OS-level backstop) | Prose extensions to `linting-and-formatting` (taint/data-flow layer), `devops-observability` (perf-regression gate), `agent-guardrails` (§4 layered sandbox enforcement) — **0 new agents/skills/rules** (from pyre-check/Pysa · mariana-trench · FAI-PEP · mcpguard-dynamic; the org is mostly libraries/frameworks, so the verify pass *dropped* the rest — `DNE-TaaC`, `mbt`, plus already-covered `infer`/`mariana-trench`-as-tool, `fbt`, `memlab`, …) | `0.52.0` |
+| **[Netflix](https://github.com/Netflix) · [aws](https://github.com/aws) · [apple](https://github.com/apple) org review** (all **1,214** repos) | Service-level resilience the kit lacked entirely — stability patterns (timeout/retry-budget/circuit-breaker/bulkhead) + adaptive concurrency limiting, chaos engineering, and bounded-clock distributed time; failure-domain-aware progressive rollout; deterministic simulation testing; a formal RFC process (working-backwards + API bar-raiser); continuous usage-based least-privilege | The **new `resilience-engineering` rule** (chaos + stability patterns + bounded clocks, from `Netflix/concurrency-limits` · `Netflix/chaosmonkey` · `aws/clock-bound`); plus prose extensions to `devops-observability` (failure-domain rollout, from `aws/zone-aware-controllers-for-k8s`), `testing` (deterministic simulation testing, from `apple/foundationdb`), `spec-driven-development` (RFC track, from `aws/aws-cdk-rfcs`), and `security-and-hardening` (continuous least-privilege, from `Netflix/repokid`) — **1 new rule, 0 new agents/skills** (the orgs are overwhelmingly SDKs/CLIs/services, so the survey kept only 7 of 1,214) | `0.53.0` |
 
 > Each adoption is detailed in the [CHANGELOG](CHANGELOG.md) — including, for every review, what we
 > deliberately **did not** add because the kit already covered it.
@@ -529,21 +513,6 @@ non-duplicative gaps**, minimally and catalog-wired.
 
 <br>
 
-**🟦 microsoft org review → agentic-AI hardening (0.50.0).** We reviewed **all 8,147 repos** in the
-Microsoft org (165 survey agents over every page → deep-dive the top candidates → adversarially verify
-the shortlist). The vast majority — SDKs, samples, Azure-product code, ML infra, OS/editor — carried
-nothing transferable, and the verify pass *dropped* two plausible picks (`ToolTalk`, whose
-ground-truth-sequence grading contradicts `evals`' "grade outcomes, not paths"; and `prompty`, an
-LLM-app product, not an SDLC practice). Eighteen survived — all **prose extensions to existing files**,
-zero new agents/skills/rules: the OWASP **Agentic Top-10 (ASI01–ASI10)** mapping, a sandbox **policy
-schema**, and layered prompt-injection defense in `agent-guardrails`; agent-aware evals (multi-judge
-panels in §3, multi-turn degradation in §8) in `evals`; validator-in-the-loop + Medprompt in
-`reasoning-techniques`; approval-gate implementation in `human-in-the-loop`; a security-lint layer in
-`linting-and-formatting`; operationalized GenAI red-teaming in `threat-model`; SBOM generation in
-`security-and-hardening`; priority-based prompt pruning in `context-engineering`; quantified-lines PR
-sizing in `code-review-and-quality`; and **4 first-party MCP fragments** (Azure · Azure DevOps · MS
-Learn · Wassette).
-
 **🔴 google org review → 21 hardening & testing patterns (0.51.0).** We reviewed **all 2,881 repos** in
 the Google org (60 survey agents over every page → deep-dive the top ~300 candidates → adversarially
 verify the shortlist). The vast majority — Android/Kotlin, C++ libraries, ML frameworks, language
@@ -580,6 +549,27 @@ to cancel environment noise, gate on the relative delta) in `devops-observabilit
 **defense-in-depth agent-sandbox enforcement** (argument-validation layer + OS-level eBPF/seccomp backstop
 *below* the existing declarative policy) in `agent-guardrails` §4 (from `mcpguard-dynamic`).
 
+**⬛🟧 Netflix · aws · apple org review → resilience engineering & more (0.53.0).** We reviewed **all
+1,214 repos** across the three orgs (34 survey agents over every page → deep-dive the candidates →
+adversarially verify the shortlist). The orgs are overwhelmingly SDKs, CLIs, cloud-product code, and
+running services — almost nothing transferable to a config scaffolder — and the verify pass scrutinized
+each survivor against the live README + license. **Seven** genuine, stack-agnostic, permissively-licensed
+disciplines survived. The biggest finding was a real **gap**: the kit had `agent-resilience` (the coding
+agent's own retries) but **no service-level resilience rule at all**, so this review adds the kit's
+**first new rule in many releases — `resilience-engineering`**: stability patterns
+(timeout/retry-budget/circuit-breaker/bulkhead/load-shedding/fallback) + **adaptive concurrency limiting**
+(TCP-congestion-control + Little's Law, from `Netflix/concurrency-limits`), **chaos engineering**
+(steady-state hypothesis, blast-radius control, automated abort, from `Netflix/chaosmonkey`), and
+**bounded-clock distributed time** (timestamps as `[earliest, latest]` + commit-wait, from
+`aws/clock-bound`). The other four are prose extensions to existing files: **failure-domain-aware
+progressive rollout** (one zone/region/cell at a time, exponential batches, reverse-order rollback) in
+`devops-observability` (from `aws/zone-aware-controllers-for-k8s`); **deterministic simulation testing**
+(single-seed control of all nondeterminism + in-sim fault injection) in `testing` (from
+`apple/foundationdb`); a formal **RFC track** for one-way-door API changes (working-backwards artifacts +
+API bar-raiser + staged sign-off) in `spec-driven-development` (from `aws/aws-cdk-rfcs`); and
+**continuous, usage-based least-privilege** (audit exercised grants → auto-revoke the unused → versioned
+rollback) in `security-and-hardening` (from `Netflix/repokid`).
+
 </details>
 
 > **Comparing claude-kit to native subagents / Agent Teams, agent collections, spec-kit, or
@@ -633,7 +623,7 @@ to cancel environment noise, gate on the relative delta) in `devops-observabilit
 
 ## Rules & skills
 
-**Rules** ([`rules/`](rules/)) are the 23 stack-agnostic contracts every agent obeys — the
+**Rules** ([`rules/`](rules/)) are the 24 stack-agnostic contracts every agent obeys — the
 `mandatory-workflow` pipeline, `quality-gates`, `rarv-cycle`, `continuity`, `documentation`,
 `testing`, the eight agent-operation rules (`reasoning-techniques`, `agent-guardrails`,
 `agent-resilience`, `goal-setting-and-monitoring`, `human-in-the-loop`, `model-tiers`, `evals`,
@@ -784,7 +774,7 @@ build attestations** for supply-chain provenance. Report vulnerabilities private
 ```
 claude-kit/
 ├── .claude-plugin/        plugin.json + marketplace.json
-├── agents/                28 SDLC agents          rules/        23 engineering rules
+├── agents/                28 SDLC agents          rules/        24 engineering rules
 ├── skills/                on-demand skills        templates/    CLAUDE.md, settings, artifacts, memory seeds
 ├── commands/              /claude-kit:* commands  hooks/        hooks.json + scripts/
 ├── catalog/         stacks·profiles·mcp·org       templates/stacks/  per-stack overlay rules + agents

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/devils-advocate.md

@@ -1,6 +1,6 @@
 ---
 name: devils-advocate
-description: Anti-sycophancy adversarial reviewer. Invoked to critique a plan/spec before approval (standard+), and whenever a parallel review or test-coverage gate reaches a unanimous PASS. Assumes the work is guilty and hunts for what everyone else missed. Gates the pipeline — the artifact is not final until this agent returns CONFIRMED.
+description: Anti-sycophancy adversarial reviewer. Critiques a plan/spec before approval, and when a gate reaches unanimous PASS. Gates the pipeline — the artifact is not final until it returns CONFIRMED.
 tools: Read, Glob, Grep, Bash, SendMessage
 permissionMode: plan
 model: opus

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/devops-engineer.md

@@ -1,6 +1,6 @@
 ---
 name: devops-engineer
-description: Delivery & operability agent. Owns the CI pipeline, build & packaging, release/rollback, environment & secret configuration, database migrations, and the local developer experience for any stack. Container-optional — works whether the project ships as containers, plain processes, managed services, or serverless.
+description: Delivery & operability agent. Owns the CI pipeline, build & packaging, release/rollback, environment & secrets, database migrations, and local dev experience for any stack. Container-optional.
 tools: Read, Write, Edit, Bash, Glob, Grep
 permissionMode: acceptEdits
 model: sonnet

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/incident-responder.md

@@ -1,6 +1,6 @@
 ---
 name: incident-responder
-description: Production incident commander. Use when prod is broken — errors spiking, a latency/availability breach, a dependency down, or a bad deploy. Triages severity, gathers signals (health, logs, metrics, error tracking), drives mitigation (rollback/flag) FIRST, then root cause. Coordinates; routes code fixes to the dev lane.
+description: Production incident commander. Use when prod is broken — errors spiking, latency breach, dependency down, bad deploy. Triages severity, gathers signals, drives mitigation (rollback/flag) FIRST, then root cause.
 tools: Read, Glob, Grep, Bash, SendMessage
 permissionMode: plan
 model: sonnet

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/policy-validator.md

@@ -1,6 +1,6 @@
 ---
 name: policy-validator
-description: Security sub-scanner. Validates that required security policies are enforced — CORS allowlist, rate limiting on auth endpoints, secure session-cookie flags, security headers, input validation at boundaries, and the authz dependency chain. PASS/FAIL per policy with remediation. Reports only.
+description: Security sub-scanner. Validates required security policies — CORS allowlist, auth-endpoint rate limiting, secure session cookies, security headers, input validation, authz chain. PASS/FAIL. Reports only.
 tools: Read, Glob, Grep, Bash, SendMessage
 permissionMode: plan
 model: sonnet

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/security-reviewer.md

@@ -1,6 +1,6 @@
 ---
 name: security-reviewer
-description: "Security stage coordinator. Runs at Phase 5.4 (after test-coverage VERIFIED, before DevOps). Dispatches four sub-scanners in parallel — secret-scanner, dependency-scanner, owasp-reviewer, policy-validator — aggregates findings by severity, and owns the Security Clear gate. Read-only: routes fixes through the Orchestrator's defect loop."
+description: Security stage coordinator. Runs at Phase 5.4 (after test-coverage VERIFIED, before DevOps). Dispatches four sub-scanners in parallel — secret, dependency, owasp, policy — and owns the Security Clear gate.
 tools: Agent, Read, Glob, Grep, Bash, SendMessage
 permissionMode: plan
 model: sonnet

{claude_code_kit-0.52.0 → claude_code_kit-0.54.0}/agents/senior-frontend-dev.md

@@ -1,6 +1,6 @@
 ---
 name: senior-frontend-dev
-description: Senior frontend developer agent. Handles UI/UX, component architecture, API integration, client state management, routing, unit testing, performance, security, and E2E testing. Stack-agnostic — adapts to the project's frontend framework, type system, build tool, and testing setup.
+description: Senior frontend developer agent handling UI/UX, component architecture, API integration, client state, routing, testing, and performance. Stack-agnostic — adapts to the project's framework and build tool.
 tools: Read, Write, Edit, Bash, Glob, Grep
 permissionMode: acceptEdits
 model: sonnet