ClaudeQB

ClaudeQB

Vibecoding-first repo planning for Claude Code. ClaudeQB turns a project repository into a durable planning package: main plan, existing-project autopsy, optional project comprehension, project ontology, planning ledger, phase sub-plans, QA audit, and a gated implementation handoff.

ClaudeQB is a Claude Code plugin that installs the /claudeqb:claudeqb skill. It is built for software, AI, infrastructure, security, and automation projects where planning needs to be evidence-backed, reviewable, adaptive, and ready for small verified execution slices.

The current 0.2.1 release adds gate-integrity compatibility on top of evidence-backed project comprehension while keeping repository marketplace distribution hardened through dependency-free make check, GitHub Actions validation, deterministic fixture corpus checks, and tracked-file sanitized exports through make export-sanitized.

Unreleased 0.3.0 preparation adds deterministic Goal preview and Apply artifact layers for no-live implementation readiness checks. These helpers do not run Claude Code, install dependencies, commit, push, deploy, or mutate external systems; they make Step 4 handoff intent and VERIFIED task evidence auditable.

Release contracts:

plugin_version: 0.2.1
artifact_schema_version: 2
handoff_contract_version: 1

Why ClaudeQB

• Repo-aware intake: ClaudeQB inspects the current repository before asking questions, then proposes evidence-backed defaults for project name, intent, target end state, constraints, autonomy/review cadence, and token/context budget assumptions.
• Durable planning docs: Output is written under Planner-docs/ so long planning work, ontology, and implementation history survive context changes and can be reviewed like normal project documentation.
• Project Autopsy + Ontology + Comprehension: Existing projects get a focused Autopsy.md report and may get Project-Ontology.md plus Project-Comprehension.md to capture evidence confidence, CQ/TRACE/ARC links, architecture reflexion, quality scenarios, and open validation probes.
• Full phase decomposition: The main plan can be expanded into ordered phase folders and detailed sub-plan files, using Autopsy feedback when available.
• QA before implementation: The audit step checks coverage, naming, ordering, section structure, readiness, ontology consistency, planning-history continuity, security/governance, vibecoding slice quality, and implementation preparedness.
• Gated execution handoff: ClaudeQB does not implement product changes itself. It prints a separate fresh Claude Code session prompt only when the audit says implementation can begin, then guides that run through the READY queue in small verified slices and asks Step 4 to append concise implementation summaries to Planing-Ledger.md.

Vibecoding-First Behavior

ClaudeQB is intentionally vibecoding-first: it keeps the target vision clear, reads the repository's real shape, avoids fake certainty, and plans the next useful verified moves instead of freezing unnecessary implementation detail too early. Generated plans should favor small reversible slices, fast validation signals, explicit deferrals, and human-review checkpoints. Vibecoding never relaxes safety, secret handling, approval, validation, or file-boundary rules.

When a project is large or ambiguous, ClaudeQB may recommend or explicitly request bounded subagents for read-only repo exploration, readiness/security review, ontology mapping, phase drafting, Step 3 audit, or Step 4 implementation/review separation. The parent ClaudeQB agent remains responsible for final artifact writes.

Workflow