claude-code-kit 0.56.0__tar.gz → 0.57.0__tar.gz

{claude_code_kit-0.56.0 → claude_code_kit-0.57.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.56.0",
+      "version": "0.57.0",
       "license": "MIT",
       "keywords": ["sdlc", "agents", "orchestration", "quality-gates", "workflow", "scaffold", "cookiecutter"]
     }

{claude_code_kit-0.56.0 → claude_code_kit-0.57.0}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-kit",
-  "version": "0.56.0",
+  "version": "0.57.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.56.0 → claude_code_kit-0.57.0}/CHANGELOG.md

@@ -4,6 +4,53 @@ 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.57.0] — 2026-07-03
+
+**Adoption & hardening — release automation, honest docs, and a credibility pass.** No new
+capability and no change to the core promise: configuration-only SDLC scaffolding for Claude Code, no
+application code, no Docker, stack-agnostic core, catalog-driven. This release closes the gap between
+"published to PyPI" and "tagged/released on GitHub," adds an honest release + road-to-1.0 policy, audits
+the skill surface, and tightens the README so every claim is verifiable. **0 new agents/skills/rules;
+`catalog.resolve()` and `catalog/*.yaml` untouched.**
+
+### Added
+
+- **Automated git tag + GitHub Release on publish.** `publish.yml` gains a `github-release` job that,
+  after a successful PyPI publish, creates the `vX.Y.Z` tag and a GitHub Release whose body is that
+  version's `CHANGELOG.md` section. Idempotent (a re-run over an already-released version is a no-op) and
+  downstream of `publish` (a Release is only cut once the wheel is actually on PyPI).
+- **`scripts/backfill-releases.sh` (`--dry-run`).** One-off, idempotent backfill that retroactively
+  creates the tag + Release for past versions that shipped via merge-to-main before the automation
+  existed. Anchors each tag to the commit that introduced that version into `pyproject.toml` (git
+  pickaxe), and skips — with a warning — any version whose release commit can't be located.
+- **[`docs/RELEASE-POLICY.md`](docs/RELEASE-POLICY.md).** Versioning, latest-only support, the
+  five-place version bump + CHANGELOG, and the publish/tag/Release automation, in one place.
+- **[`docs/launch/road-to-1.0.md`](docs/launch/road-to-1.0.md).** An honest, verifiable list of what
+  stands between the current `4 - Beta` and 1.0 (stack coverage, enforcement honesty, hook portability,
+  evidence base, export fidelity, API stability). The Development Status classifier stays `4 - Beta`.
+- **[`docs/skill-audit.md`](docs/skill-audit.md).** Core-vs-collection classification, the per-profile
+  install footprint (agents/skills/rules + an on-disk token estimate), and the finding that the
+  `enterprise` profile's `skills: all` installs every collection skill regardless of the chosen stack.
+  Documents and recommends; changes no profile (skills load on demand, so this is selection, not
+  always-resident context).
+- **Launch-prep assets under `docs/launch/`** (owner checklists, not code): `github-about.md`,
+  `demo-script.md`, `directory-submission.md`, `awesome-prs.md`, `posts.md`, and `seed-issues.md`.
+
+### Changed
+
+- **README credibility pass.** Strengthened the anti-sycophancy / evidence framing and added a
+  "What loads into your context" per-profile table (agents/skills/rules), so the footprint is explicit
+  before install. Counts remain pinned by `scripts/check_docs_consistency.py`.
+
+### Not adopted (deliberately)
+
+- **No version-parity CI addition** — `scripts/check_docs_consistency.py::check_versions()` already
+  enforces parity across the four manifests, `SECURITY.md`, and the latest CHANGELOG heading.
+- **No `profiles.yaml` change** for the `skills: all` finding — flagged and recommended in the audit;
+  any opt-in must stay a catalog/config change with no `resolve()` branching (golden rule #6).
+- **Development Status stays `4 - Beta`** — the classifier is not flipped until the road-to-1.0 gaps
+  are met.
+
 ## [0.56.0] — 2026-07-01
 
 **`export` command — carry the config to Cursor / VS Code / GitHub Copilot.** A teammate who works in

{claude_code_kit-0.56.0 → claude_code_kit-0.57.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-code-kit
-Version: 0.56.0
+Version: 0.57.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
@@ -43,6 +43,12 @@ assumed, or partial-output "it works" is itself an auto-Critical finding — so
 checks actually ran. A Cookiecutter-style scaffolder, installed as **configuration only — no
 application code, no Docker.**
 
+<!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
+     Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
+     The recording replays the genuine run already in examples/real-run/ (the devils-advocate catching a
+     Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
+     Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -363,6 +369,26 @@ need.
   compliance, production-data) install only in organization scope (see
   [`docs/org-capabilities.md`](docs/org-capabilities.md)).
 
+**What loads into your context** — the profile you pick decides how much lands in `.claude/`. Measured
+on a React + FastAPI + PostgreSQL project, individual scope:
+
+| Profile | Agents | Skills | Rules |
+|---------|-------:|-------:|------:|
+| `lean` | 8 | 14 | 35 |
+| `standard` (default) | 26 | 42 | 35 |
+| `enterprise` | 31 | 104 | 35 |
+
+- **Rules are profile-independent** — every profile installs the same 24 core rules + the selected
+  stack's overlays (11 for this stack = 35); rigor changes the *agents and gates*, not the rule set.
+- **Skills activate on demand** — they are installed and available, then pulled into context by task
+  relevance, not all held resident at once. The count is what's on disk, not a fixed context tax.
+- **Counts include stack overlays** — the numbers above already fold in the chosen stack (e.g. the
+  Postgres overlay adds 3 agents, which is why `enterprise` shows 31 against a 28-agent core roster). A
+  different stack shifts them by a few.
+- **`enterprise` installs the whole skill collection** (`skills: all`) — all 104 skills, including
+  collection skills for stacks you didn't select. That's disk/selection footprint, not always-resident
+  context, but if you want a tighter install prefer `standard`. See [`docs/skill-audit.md`](docs/skill-audit.md).
+
 </details>
 
 <details>

{claude_code_kit-0.56.0 → claude_code_kit-0.57.0}/README.md

@@ -10,6 +10,12 @@ assumed, or partial-output "it works" is itself an auto-Critical finding — so
 checks actually ran. A Cookiecutter-style scaffolder, installed as **configuration only — no
 application code, no Docker.**
 
+<!-- DEMO PLACEHOLDER — a 60–90s terminal capture of a gated `/sdlc` run belongs here once recorded.
+     Shot list, timing, and which real assets to show: docs/launch/demo-script.md.
+     The recording replays the genuine run already in examples/real-run/ (the devils-advocate catching a
+     Medium bug a unanimous review missed, and the gate refusing to advance until it was fixed).
+     Until the GIF exists, that folder IS the evidence — linked from "How it works" and "The pipeline" below. -->
+
 [![PyPI](https://img.shields.io/pypi/v/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![Python](https://img.shields.io/pypi/pyversions/claude-code-kit.svg)](https://pypi.org/project/claude-code-kit/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -330,6 +336,26 @@ need.
   compliance, production-data) install only in organization scope (see
   [`docs/org-capabilities.md`](docs/org-capabilities.md)).
 
+**What loads into your context** — the profile you pick decides how much lands in `.claude/`. Measured
+on a React + FastAPI + PostgreSQL project, individual scope:
+
+| Profile | Agents | Skills | Rules |
+|---------|-------:|-------:|------:|
+| `lean` | 8 | 14 | 35 |
+| `standard` (default) | 26 | 42 | 35 |
+| `enterprise` | 31 | 104 | 35 |
+
+- **Rules are profile-independent** — every profile installs the same 24 core rules + the selected
+  stack's overlays (11 for this stack = 35); rigor changes the *agents and gates*, not the rule set.
+- **Skills activate on demand** — they are installed and available, then pulled into context by task
+  relevance, not all held resident at once. The count is what's on disk, not a fixed context tax.
+- **Counts include stack overlays** — the numbers above already fold in the chosen stack (e.g. the
+  Postgres overlay adds 3 agents, which is why `enterprise` shows 31 against a 28-agent core roster). A
+  different stack shifts them by a few.
+- **`enterprise` installs the whole skill collection** (`skills: all`) — all 104 skills, including
+  collection skills for stacks you didn't select. That's disk/selection footprint, not always-resident
+  context, but if you want a tighter install prefer `standard`. See [`docs/skill-audit.md`](docs/skill-audit.md).
+
 </details>
 
 <details>

claude_code_kit-0.57.0/docs/RELEASE-POLICY.md

@@ -0,0 +1,92 @@
+# Release Policy
+
+This document describes claude-kit's versioning, release, and support policy.
+
+## Versioning
+
+claude-kit follows [Semantic Versioning](https://semver.org/) (SemVer).
+
+**Pre-1.0 stability:** The project is currently pre-1.0 (Development Status :: 4 - Beta). During
+the 0.x phase, minor version increments (e.g., 0.56.0 → 0.57.0) may introduce behavior changes or
+breaking changes. Breaking changes are always called out explicitly in the CHANGELOG.
+
+Once the project reaches 1.0.0, the standard SemVer contract will apply: breaking changes only in
+major versions, backwards-compatible features in minor versions, and fixes in patch versions.
+
+## Supported Versions
+
+**Only the latest released version receives fixes.** There is no long-term-support (LTS) branch or
+backport policy. When a new version is released, the previous version is no longer supported.
+
+This policy mirrors the project's [SECURITY.md](../SECURITY.md) stance: security fixes are
+published only for the latest release.
+
+## What Is in a Release
+
+Every release includes:
+
+- A version bump in **all five** of the following files (enforced by CI):
+  - `pyproject.toml`
+  - `.claude-plugin/plugin.json`
+  - `.claude-plugin/marketplace.json` (the marketplace entry)
+  - `src/claude_kit/__init__.py` (`__version__`)
+  - `SECURITY.md` (the "Supported Versions" table)
+- A new section in `CHANGELOG.md` following [Keep a Changelog](https://keepachangelog.com/)
+  format, with a dated heading matching the new version
+- A "Not adopted (deliberately)" note in the CHANGELOG entry, documenting what was reviewed but
+  intentionally excluded from the kit
+
+A CI check (`scripts/check_docs_consistency.py`) enforces version parity across all five locations
+and verifies that the latest CHANGELOG heading matches the current version.
+
+## Release Process
+
+1. **Bump the version** in all five files listed above.
+2. **Update CHANGELOG.md** with a new section for the release, including the date and the
+   "Not adopted" note.
+3. **Merge to main.** Once the pull request is merged:
+   - `.github/workflows/publish.yml` automatically checks whether the version in `pyproject.toml`
+     is newer than the latest version on PyPI.
+   - If the version is new, the workflow publishes the package to PyPI and creates:
+     - A git tag `vX.Y.Z`
+     - A GitHub Release whose body is the new version's CHANGELOG section
+
+No manual PyPI upload or tag creation is required. As of version 0.57.0, the workflow handles both
+PyPI publishing and GitHub Release creation in a single run.
+
+## Publishing and Provenance
+
+Releases are published to [PyPI](https://pypi.org/project/claude-code-kit/) via **OIDC Trusted
+Publishing** (no long-lived token) with **PEP 740 build attestations** for provenance verification.
+
+The workflow is version-gated: it only publishes when the version in `pyproject.toml` is newer than
+the latest version on PyPI.
+
+## Pre-1.0 Stability Caveat
+
+Because the project is pre-1.0, minor version updates may include:
+
+- Changes to the SDLC agent protocols or quality gates
+- Modifications to the catalog schema or resolution behavior
+- Removal or renaming of skills, agents, or rules
+- Breaking changes to the CLI interface
+
+Always review the CHANGELOG before upgrading. Breaking changes are explicitly called out.
+
+## Release Cadence
+
+Releases are shipped **when ready**. There is no fixed calendar schedule.
+
+Many minor releases are driven by **reuse-first adoption reviews** — surveys of external projects
+or organizations (e.g., Alibaba, Microsoft, Google) that result in new overlay rules, skills, or
+agents being added to the kit.
+
+## Reporting Issues
+
+- **Feature requests and regressions:** Open a [GitHub issue](https://github.com/ajyadav013/claude-kit/issues).
+- **Security vulnerabilities:** Follow the [SECURITY.md](../SECURITY.md) policy (private reporting via GitHub).
+
+---
+
+**License:** MIT © Arjunsingh Yadav  
+**Repository:** [github.com/ajyadav013/claude-kit](https://github.com/ajyadav013/claude-kit)

claude_code_kit-0.57.0/docs/launch/awesome-prs.md

@@ -0,0 +1,118 @@
+# Awesome List Submission Guide
+
+This document provides ready-to-submit entries for relevant awesome lists. All submissions should be made by the project owner following each list's contribution guidelines.
+
+## Priority Order
+
+1. **hesreallyhim/awesome-claude-code** (~47.8k stars, active) — highest visibility
+2. **VoltAgent/awesome-claude-code-subagents** (~22.7k stars, active) — relevant category
+3. **ComposioHQ/awesome-claude-plugins** (stale, ~2 months no activity) — optional, deprioritized
+
+---
+
+## hesreallyhim/awesome-claude-code
+
+**Target:** [hesreallyhim/awesome-claude-code](https://github.com/hesreallyhim/awesome-claude-code) (~47.8k stars, active)
+
+**Method:** Submit via **ISSUE FORM** (NOT a pull request)
+- Path: `issues/new?template=recommend-resource.yml`
+- Full URL: https://github.com/hesreallyhim/awesome-claude-code/issues/new?template=recommend-resource.yml
+
+**Category:** Infrastructure & DevOps
+
+**Ready Copy:**
+
+*Description (204 characters, within 10-500 constraint):*
+```
+An autonomous, stack-agnostic SDLC for Claude Code, shipped as a plugin and a pip scaffolder, that enforces quality gates and independent reviewer agents including an anti-sycophancy devils-advocate gate.
+```
+
+*Resource URL:*
+```
+https://github.com/ajyadav013/claude-kit
+```
+
+**Etiquette:**
+- Use the issue form fields exactly as provided
+- No emoji in description
+- Non-promotional language (already honored above)
+- Wait for maintainer review before follow-up
+
+---
+
+## VoltAgent/awesome-claude-code-subagents
+
+**Target:** [VoltAgent/awesome-claude-code-subagents](https://github.com/VoltAgent/awesome-claude-code-subagents) (~22.7k stars, active)
+
+**Method:** Submit a **PULL REQUEST**
+- File to edit: `categories/09-meta-orchestration/README.md`
+- Add one bullet line in the appropriate section
+
+**Category:** Meta Orchestration
+
+**Ready Copy:**
+
+*One-line bullet (vendor-neutral):*
+```markdown
+- [**claude-kit**](https://github.com/ajyadav013/claude-kit) - Autonomous stack-agnostic SDLC for Claude Code (plugin + pip scaffolder) with quality gates and independent reviewer agents, including an anti-sycophancy devils-advocate gate.
+```
+
+**Etiquette:**
+- Follow the repository's CONTRIBUTING.md guidelines
+- One entry per PR
+- Ensure the bullet follows the existing format in the category
+- Provide a clear PR title: "Add claude-kit to Meta Orchestration"
+- Keep the description factual and non-promotional
+
+---
+
+## ComposioHQ/awesome-claude-plugins
+
+**Target:** [ComposioHQ/awesome-claude-plugins](https://github.com/ComposioHQ/awesome-claude-plugins) (stale, ~2 months no activity)
+
+**Status:** Optional, deprioritized due to inactivity
+
+**Method:** If submitting, likely a **PULL REQUEST** (check CONTRIBUTING.md)
+
+**Ready Copy:**
+
+*Suggested bullet:*
+```markdown
+- [**claude-kit**](https://github.com/ajyadav013/claude-kit) - Stack-agnostic autonomous SDLC plugin with quality gates, reviewer agents, and anti-sycophancy devils-advocate verification.
+```
+
+**Etiquette:**
+- Check repository activity before submitting
+- Review CONTRIBUTING.md if it exists
+- Consider waiting for signs of active maintenance before submitting
+
+---
+
+## General Submission Etiquette
+
+1. **Follow each list's CONTRIBUTING guidelines** — some require issues, others PRs
+2. **One entry per submission** — do not batch multiple resources
+3. **Factual, non-promotional descriptions** — let the features speak for themselves
+4. **No emoji** in descriptions unless the list explicitly uses them
+5. **Respect maintainer time** — wait for review, do not ping or rush
+6. **Verify links** before submitting
+7. **Check star counts and activity** — prioritize active, high-visibility lists
+
+---
+
+## Verification Checklist
+
+Before submitting to any list:
+
+- [ ] Repository is MIT-licensed (verified)
+- [ ] GitHub URL is correct: https://github.com/ajyadav013/claude-kit
+- [ ] PyPI package exists: https://pypi.org/project/claude-code-kit/
+- [ ] Description is factual and non-promotional
+- [ ] Character count is within constraints (where applicable)
+- [ ] Submission method matches the list's requirements (issue vs PR)
+- [ ] Target file path is correct (for PRs)
+- [ ] Category is appropriate for the resource
+
+---
+
+*Last updated: 2026-07-03*

claude_code_kit-0.57.0/docs/launch/demo-script.md

@@ -0,0 +1,71 @@
+# Demo Script — 60–90s terminal capture
+
+**Goal:** After 90 seconds, a viewer should believe: *"this is real, gated, and catches what a rubber-stamp review misses."* The devils-advocate catching a Medium bug a unanimous panel missed is the emotional peak.
+
+Everything below is grounded in the genuine captured run in `examples/real-run/` (Go `net/http` `DELETE /tasks/{id}`). Do not script anything that did not happen — quote the committed artifacts.
+
+## Constraints
+
+- **Runtime:** 60–90 seconds total (90s hard cap)
+- **Format:** Terminal capture (asciinema/asciicast, or any `.cast` → GIF/mp4 recorder)
+- **Dimensions:** 1280×720 minimum; readable font (14–16pt monospace)
+- **Audio:** Not required; use on-screen captions for narration
+- **Authenticity:** Replay the existing `examples/real-run/cast/gate-checks.cast` (genuine gate checks: 7 tests, 85.2% coverage) plus the committed artifact text under `run-artifacts/`. Do NOT re-run live or fabricate screens. Every displayed line must come from a file in `examples/real-run/`.
+
+## Shot list
+
+Windows below sum to 90s (the hard cap); trim in post to land in the 60–90s band.
+
+| # | Time | On-screen action | Caption |
+|---|------|------------------|---------|
+| **1** | 0:00–0:08 | Show the plugin install one-liner in a Claude Code session: `/plugin marketplace add ajyadav013/claude-kit` → `/plugin install claude-kit@claude-kit` → confirmation message. (Alternative: `pip install claude-code-kit`.) | "Install as a Claude Code plugin (or `pip install claude-code-kit`)." |
+| **2** | 0:08–0:18 | Run `/sdlc Add DELETE /tasks/{id} to a Go net/http task API`. Show the command executing and the pipeline launching from the first gate (`spec-complete`). | "One command drives spec → review → build → test → security → ship." |
+| **3** | 0:18–0:35 | Show the recorded gate state: `spec-complete` ✓, `em-approved` ✓, `code-review` ✓, `build-green` ✓, `test-coverage` ✓, `security-clear` ✓ — with the four reviewer verdicts underneath (code-review PASS, em APPROVED, security CLEAR, acceptance ACCEPT, from `run-artifacts/devils-advocate.txt` line 3). Then note the kit spawns the devils-advocate because that pass was unanimous. | "Four reviewers return a unanimous pass — so the kit spawns a devils-advocate." |
+| **4** | 0:35–0:50 | Show the devils-advocate excerpt from `run-artifacts/devils-advocate.txt`: the FINDING 1 [Medium] server.go:25 id-aliasing summary (`strconv.Atoi` accepts `+`, leading zeros, arbitrary zero-padding, so `"01"`, `"+1"`, `"%2B1"`, `"00000000001"` are all treated as id 1 and DELETE it) plus the raw-socket reproduction (`DELETE /tasks/01 -> HTTP/1.1 204 No Content (task 1 deleted)`). Highlight `VERDICT: OVERTURNED` and `FINDINGS: critical=0 high=0 medium=1 low=1`. | "Devils-advocate attacks over a raw TCP socket. Finds a Medium: /tasks/01 deletes task 1." |
+| **5** | 0:50–1:00 | Show the gate refusal verbatim from `run-artifacts/gate-refused.txt`: `FAIL  cannot close 'contract-clear': medium=1 open finding(s) must be resolved first`. | "Gate REFUSES to advance: an open Medium blocks it, per quality-gates.md." |
+| **6** | 1:00–1:15 | Show a one-line fix being applied (caption note: "reject non-canonical ids, server.go:25"), then the re-verification excerpt from `run-artifacts/defect-loop-reverify.txt`: `WIRE DELETE /tasks/01 -> "HTTP/1.1 400 Bad Request"` … `VERDICT: UPHELD`, `FINDINGS: critical=0 high=0 medium=0 low=1`. | "Fix + mux-level regression test. Re-verify over the raw wire. UPHELD." |
+| **7** | 1:15–1:25 | Replay `cast/gate-checks.cast` (gate checks running green): `build` → `vet` → `gofmt` → `test` → `coverage: 85.2% of statements`. Show the green output. | "Gate checks pass: 7 tests, 85.2% coverage." |
+| **8** | 1:25–1:30 | Show the final recorded state from `captured-bundle/state/pipeline-snapshot.json`: `last_gate_passed: contract-clear`, `open_findings: {critical:0, high:0, medium:0, low:1}`. | "Ship-ready — no open Critical/High/Medium. Gates backed by real command output." |
+
+Notes on fidelity:
+
+- Shot 3 lists the seven real gate keys from `pipeline-snapshot.json`'s `gate_evidence` (`spec-complete`, `em-approved`, `code-review`, `build-green`, `test-coverage`, `security-clear`, `contract-clear`). "Acceptance" is a **reviewer verdict** (ACCEPT), not a pipeline gate — show it as a verdict, not a gate row.
+- `pipeline status` (`run-artifacts/pipeline-status.txt`) prints `task / profile / scope / mode / stage / last gate passed / open findings / next`; it does **not** print a "spawning devils-advocate" line. Convey the unanimity → devils-advocate spawn via a caption, not by inventing terminal output.
+- The `-race` clean claim is supported by `run-artifacts/defect-loop-reverify.txt` ("`go test -race` clean (7/7)") and `run-artifacts/test-race.txt`; include it only if you show that source.
+
+## Assets to use
+
+All material exists in `examples/real-run/`:
+
+1. **Asciicast of gate checks:** `cast/gate-checks.cast` (replay with `asciinema play`, or convert to GIF/mp4 via `agg`/`svg-term`/`asciinema-player`). Static render: `cast/gate-checks.svg`.
+2. **Devils-advocate verdict:** `run-artifacts/devils-advocate.txt` (excerpt: finding summary + raw-socket reproduction + `VERDICT: OVERTURNED`).
+3. **Gate refusal:** `run-artifacts/gate-refused.txt` (`FAIL  cannot close 'contract-clear': medium=1 open finding(s) …`).
+4. **Re-verification verdict:** `run-artifacts/defect-loop-reverify.txt` (excerpt: fix verified over the raw wire + `VERDICT: UPHELD`).
+5. **Pipeline state:** `captured-bundle/state/pipeline-snapshot.json` (source for the `pipeline status` view; `last_gate_passed: contract-clear`, `open_findings: {…, low:1}` after the fix). Human-readable form: `run-artifacts/pipeline-status.txt`.
+6. **The feature under test:** Go `DELETE /tasks/{id}` on a `net/http` task API — source in `sample-app/` (`server.go`, `store.go`), described in `examples/real-run/README.md`.
+
+Do NOT invent UI, web views, or dashboard screens — none exist. This is a terminal-only capture.
+
+## Post-production
+
+1. **Trim to 60–90s.** If the install or `/sdlc` invocation runs long, cut dead time (`asciinema cut` or a video editor).
+2. **Add captions** (overlay text or interstitial slides) per the table above. Make captions large enough to read at 1280×720.
+3. **Export as GIF + mp4:**
+   - GIF (for inline README embedding): e.g. `agg gate-checks.cast demo.gif`, or `svg-term`.
+   - mp4 (for platforms that don't auto-play GIF): screen-record `asciinema-player`, or convert the GIF with `ffmpeg`.
+4. **Verify readability:** font must be legible at 1280×720; test on a phone screen.
+5. **Where it lands:**
+   - **README.md:** replace the `<!-- DEMO PLACEHOLDER … -->` comment (already present just above the badge row) with the demo GIF/video embed.
+   - **Launch posts** (HN/Reddit/social): inline the GIF or link the mp4.
+   - **Anthropic plugin directory submission:** attach the mp4 as a demo asset if the submission form allows.
+
+## Acceptance criteria
+
+- [ ] Total runtime 60–90 seconds (90s hard cap).
+- [ ] Every shot maps to a file that exists in `examples/real-run/` (no invented content or UI).
+- [ ] Displayed terminal text is quoted from the committed artifacts, not paraphrased into fake output.
+- [ ] The devils-advocate catch (shot 4) is the peak — the viewer sees the raw-socket reproduction and understands this is not a rubber stamp.
+- [ ] The gate refusal (shot 5) is the trust moment — the harness enforces the rule, not just the agent.
+- [ ] No fabricated UI, dashboards, or web views (terminal only).
+- [ ] Captions are readable at 1280×720.
+- [ ] Final artifact is a GIF (for README) + mp4 (for platforms that need it).

claude_code_kit-0.57.0/docs/launch/directory-submission.md

@@ -0,0 +1,85 @@
+# Plugin Directory Submission Checklist
+
+This document outlines the steps for submitting claude-kit to the Anthropic plugin directory/marketplace, plus install-today instructions for users.
+
+## Pre-Submission Validation
+
+The plugin manifests (`.claude-plugin/plugin.json` and `.claude-plugin/marketplace.json`) are already valid and ready for submission. Before submitting, run the validation commands to confirm:
+
+```bash
+# Standard validation
+claude plugin validate .
+
+# Strict validation (checks optional/recommended fields)
+claude plugin validate . --strict
+```
+
+Fix any errors. Warnings from `--strict` are optional improvements, not blockers.
+
+## Optional Manifest Hygiene
+
+These are non-blocking improvements that may be addressed before or after submission:
+
+1. **Owner schema alignment**: The `.claude-plugin/marketplace.json` currently uses `{name, url}` for the owner field. The documented schema is `{name, email}`. The `url` field is non-standard and may trigger a warning under `--strict`. Consider switching to `{name, email}` for consistency with the documented schema.
+
+2. **Version duplication**: The version appears in both `plugin.json` (authoritative) and the marketplace entry. This is expected but note that `plugin.json` is the source of truth.
+
+## Install Today (No Directory Required)
+
+Users can install claude-kit immediately without waiting for directory listing:
+
+```bash
+# Add the GitHub marketplace
+/plugin marketplace add ajyadav013/claude-kit
+
+# Install the plugin
+/plugin install claude-kit@claude-kit
+```
+
+Use this snippet in the README, release notes, or social posts.
+
+## Submission Paths
+
+Anthropic reviews third-party submissions before they land in the public community marketplace (`claude-community`). Submit via one of the in-app forms below. The form you can use depends on whether you have a Team/Enterprise organization.
+
+### Solo / Individual Developers
+
+Submit via the Console plugin submission form:
+
+- URL: [platform.claude.com/plugins/submit](https://platform.claude.com/plugins/submit)
+- Available to individual authors who are not part of a Team or Enterprise organization
+
+### Organizations (Team / Enterprise)
+
+Submit via the claude.ai submission form:
+
+- URL: [claude.ai/admin-settings/directory/submissions/plugins/new](https://claude.ai/admin-settings/directory/submissions/plugins/new)
+- Requires a Claude Team or Enterprise organization plus directory management access (organization Owners have this by default)
+
+### Official / Curated Marketplace
+
+The official curated marketplace (`claude-plugins-official`) is curated by Anthropic at its discretion. There is no open application process, and the submission forms above do not add plugins to the official marketplace.
+
+## Reference Documentation
+
+Before submitting, **re-check the live documentation** at the URLs below. Plugin requirements and submission processes may change:
+
+- Plugin development guide: [code.claude.com/docs/en/plugins](https://code.claude.com/docs/en/plugins)
+- Plugin marketplaces: [code.claude.com/docs/en/plugin-marketplaces](https://code.claude.com/docs/en/plugin-marketplaces)
+- Plugin reference: [code.claude.com/docs/en/plugins-reference](https://code.claude.com/docs/en/plugins-reference)
+
+## Owner Submission Checklist
+
+- [ ] Run `claude plugin validate .` and `claude plugin validate . --strict`
+- [ ] Fix any validation errors (warnings are optional)
+- [ ] Verify the live submission form and documentation links above
+- [ ] Consider the optional manifest hygiene items (not required)
+- [ ] Choose submission path: solo (platform.claude.com) or organization (claude.ai)
+- [ ] Submit the plugin
+- [ ] Update installation instructions once directory listing is live (if different from the GitHub marketplace install)
+
+---
+
+**License**: MIT © Arjunsingh Yadav  
+**Repository**: [github.com/ajyadav013/claude-kit](https://github.com/ajyadav013/claude-kit)  
+**PyPI**: [pypi.org/project/claude-code-kit](https://pypi.org/project/claude-code-kit)

claude_code_kit-0.57.0/docs/launch/github-about.md

@@ -0,0 +1,45 @@
+# GitHub About Panel Setup
+
+Internal checklist for setting the GitHub repository "About" sidebar (description, topics, website).
+
+---
+
+## Description
+
+Ready-to-paste candidates (kept within a self-imposed 120-character budget):
+
+1. **Recommended:**  
+   `Stack-agnostic SDLC config scaffolder for Claude Code. Quality gates, 28 agents, no Docker. MIT. pip install.` (109 chars)
+
+2. **Alternative (simpler):**  
+   `Autonomous SDLC pipeline for Claude Code. Spec→review→build→test→ship. Stack-agnostic config, no app code.` (106 chars)
+
+3. **Alternative (trust-focused):**  
+   `Claude Code SDLC scaffolder with quality gates that block on real evidence. Stack-agnostic config, no Docker.` (109 chars)
+
+---
+
+## Website
+
+**Set to:**  
+`https://pypi.org/project/claude-code-kit/`
+
+**Rationale:** The canonical install/distribution page.
+
+---
+
+## Topics
+
+Lowercase, hyphenated tags (copy-paste ready):
+
+```
+claude-code claude ai-agents sdlc agents orchestration code-review testing quality-gates workflow automation scaffold cookiecutter developer-tools python pip plugin
+```
+
+---
+
+## Checklist (repo owner, GitHub web UI)
+
+1. Navigate to the repository home page → click the **gear icon** next to "About" in the right sidebar.
+2. Paste the chosen description (recommend option 1) and set **Website** to `https://pypi.org/project/claude-code-kit/`.
+3. Add the topics from the space-separated list above → click **Save changes**.