camp

---

claude-camp turns Claude Code into a small, disciplined engineering team. Instead of steering an agent step by step, you brief a PM persona — PmCamp. It triages your requirements, breaks them into milestones, delegates the build to sub-agents, and never reports work as "done" without verifying it against tests, git history, and your acceptance criteria.

Two commands run the whole loop:

• /basecamp — one-time project setup (a new project or an existing codebase)
• /kickcamp — hand it a requirements doc; it delivers the feature

Table of contents

• Highlights
• Installation
• Commands
• How it works
• What /basecamp sets up
• The PmCamp persona
• Optional tools
• Roadmap
• Repository structure
• License

Highlights

• 🧭 One point of contact. You talk to PmCamp; it orchestrates everything and pulls you in only for gaps, plan sign-off, real decisions, and verified completion.
• 🔍 Verification-first. No milestone is "done" on a sub-agent's word — PmCamp checks tests, real commits, and acceptance criteria, and reports with evidence.
• 🌱 Greenfield or brownfield. /basecamp scaffolds new projects and safely adopts existing ones (detect stack, map the code, never overwrite).
• 🧱 Python and Node backends. FastAPI/Django (Python) or NestJS ★/Fastify/Express (Node), with PostgreSQL/MySQL/SQLite or MongoDB. Scaffolds run the official generator, then overlay a module-based structure shipped as bundled rules.
• 🎚️ Model-tier enforcement. Pick a tier once (Flagship / Premium ★ / Balanced / Economy) — /basecamp writes it to .claude/settings.json, setting the PM model and forcing every subagent's model via CLAUDE_CODE_SUBAGENT_MODEL (the only layer that catches them all). Escape hatches documented in CLAUDE.md.
• 🪙 Token-efficient by design. Graph-before-grep, scoped reads, sub-agent isolation, session hygiene rules, a snapshot STATUS.md, and optional command/output compression.
• 🧩 Composes, doesn't compete. Builds on Superpowers (workflow), Karpathy's principles, claude-mem, and code-review-graph instead of re-implementing them.

Installation

In Claude Code:

/plugin marketplace add havinhthai/claude-camp
/plugin install camp@claude-camp

That's it — /basecamp and /kickcamp are now available in every project. No cloning, symlinking, or file-permission setup.

Update later with:

/plugin marketplace update

Commands

Command	Purpose
/basecamp	Bootstrap a project. Audits and installs the global toolkit, scaffolds to the chosen stack, and writes CLAUDE.md + the PmCamp persona. Runs in greenfield mode (new) or adopt mode (existing codebase).
/basecamp adopt	Force adopt mode for an existing codebase — detect the stack, build the code graph, scaffold only what's missing, never overwrite.
/kickcamp <doc>	Hand a requirements doc to PmCamp: triage → milestones (you confirm) → build via sub-agents → verify (tests + git + acceptance) → report.

How it works

Setup once — run /basecamp in a project. It prepares the foundation (toolkit, CLAUDE.md, PmCamp, docs/) and stops before any feature code.

Then, per feature — drop a spec in docs/requirements/ and run /kickcamp <doc>:

you → /kickcamp doc
        │
        ▼
   PmCamp: triage ──(gaps?)──► ask you 🟡
        │
        ▼
   milestones ──► you confirm
        │
        ▼
   per milestone: Superpowers workflow via sub-agents
        │
        ▼
   PmCamp VERIFY: tests + git log + acceptance
        │
        ▼
   report with evidence ──► you approve ──► next milestone ↺

You only step in at four moments: a requirement gap, milestone sign-off, a real decision or blocker, and a verified-done report.

What /basecamp sets up

On first run, /basecamp audits and installs (only what's missing) a curated global toolkit — you don't install these by hand: