克劳德开发工具包

Requirements

• Claude Code — CLI, desktop app, or IDE extension
• macOS / Linux
• Python 3.11+
• Git
• GitHub CLI (gh) — authenticated

Optionally add the sales pack — enabling it auto-enables core (declared dependency)

/plugin install claude-dev-kit-sales@claude-dev-kit ```

Namespacing: plugin skills are namespaced by plugin name — e.g. /claude-dev-kit:implement, /claude-dev-kit:review. This is mandatory for plugins (it prevents cross-plugin collisions).

Short names (standalone option): if you prefer the bare /implement, /review, … keep using the submodule + install_project.sh path above — standalone .claude/skills/ keeps short, un-namespaced names. The plugin and submodule paths are equivalent in behavior; they differ only in skill-name prefixing and how updates are delivered (/plugin versioning vs git submodule update). (The bespoke installer is retired in a later step — see ISSUE-027 — once the plugin path reaches parity.)

Migrate — Upgrade dependencies or runtime

/migrate [target, e.g. "Django 5.0" or "Python 3.12"]

Scans the codebase for impact, generates a step-by-step migration plan with rollback instructions, and applies changes incrementally with test verification.

1. Build a product from scratch

``` /prd → /kickoff → /uiux → /sprint

Installation

claude-kit is installed into a service repo as a git submodule.

2. Install user tools

Installs the status line script to ~/.claude/kit/bin/. Run once per machine.

bash .claude-kit/scripts/install_user.sh

3. Install into project

Symlinks core agents, skills, hooks, and settings into the project's .claude/ directory. Default install is core only:

bash .claude-kit/scripts/install_project.sh

To include the sales pack (account-research / discovery / proposal / meeting-capture / follow-up):

bash .claude-kit/scripts/install_project.sh --pack=sales

To include every declared pack:

bash .claude-kit/scripts/install_project.sh --pack=all

After installation:

your-service-repo/
├── .claude/
│   ├── agents/          # 33 core agents (or +5 if --pack=sales)
│   ├── skills/          # 23 core skills (or +5 if --pack=sales)
│   ├── hooks/           # agent_state.py (agent state tracking)
│   └── settings.json    # Status line + hook config (auto-merged)
├── .claude-kit/         # submodule (source — contains packs/ subtree too)
└── ...

Re-running the installer with a different --pack set is destructive of the pack entries from the previous install (the install set IS the active install). Symlinks are per-entry so core + selected packs coexist in the same .claude/agents/ and .claude/skills/.

Add the marketplace (the repo itself), then install the core plugin

/plugin marketplace add pillip/claude-dev-kit /plugin install claude-dev-kit@claude-dev-kit

Implement — Build an issue

/implement ISSUE-001

1. Reads issue spec from issues.md
2. Creates GH Issue if missing
3. Creates branch → implements → tests → commits → pushes
4. Creates PR with Closes #<issue_number> in body
5. Updates issues.md metadata

Ship — Deploy

/ship

Verifies tests pass, updates documentation, merges the PR, and reports test coverage gaps in shipped code with suggestions to run /testgen.

Core Use Cases

Team-scale usage

The kit assumes the repo IS the team boundary. Two adoption patterns cover the common shapes — and there is deliberately no separate "team layer."

Usage

(optional pre-PRD: /brainstorm → /bizanalysis → /prd)

``` Start with an idea, validate it, write a PRD, generate planning docs, design the UI, and let the team-lead auto-implement everything.

(optional pre-PRD: /brainstorm → /bizanalysis → /prd)

**Existing codebase (no PRD):**

**Single issue:**

**Add a feature to existing product:**

Optional pre-PRD: /brainstorm (Socratic exploration) and /bizanalysis (market + SWOT) are stand-alone primitives, not part of the default flow. If your idea is clear, start from /prd. These exist for the case where you genuinely don't know what to build yet. /uiux, /mobile-uiux, and /desktop-uiux are optional for UI projects. Backend/CLI projects go directly from /kickoff to /sprint. /sprint auto-orchestrates multiple issues. For a single issue, use /implement directly. /scan is for existing codebases without a PRD. It reverse-engineers planning docs from code.

Configuring gates via `docs/test_plan.md`

qa-designer generates a ## Verify Gates Configuration section in docs/test_plan.md. Users can edit it to override defaults without touching Python:

```markdown

Verify Gates Configuration

Server start command: npm run dev Server health URL: http://localhost:3000 Server startup timeout: 30 Mobile test framework: maestro Mobile build command: npm run build:ios Mobile Detox config: ios.sim.debug

Workflow

New project: ``` /prd → /kickoff → /uiux → /sprint

1. Add the submodule

cd your-service-repo
git submodule add git@github.com:pillip/claude-dev-kit.git .claude-kit

Alternative: install as a Claude Code plugin

The repo also ships as a Claude Code plugin marketplace (.claude-plugin/marketplace.json), so you can install without the submodule/installer:

```bash