alicankiraz1

ClaudeQB — Development skill for Claude Code

Development community

Claude Code plugin for vibecoding-first repo planning.

How to install ClaudeQB

This entry records only its repository, not the path inside it, so there is no exact command to give. Open alicankiraz1/ClaudeQB and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What ClaudeQB does

Claude Code plugin for vibecoding-first repo planning.

Alternatives in Development

OpenAI Codex CLI — (Rust implementation) 67.8k ★
Plan Feature: Comprehensive Archon Implementation Planning — Plan Feature: Comprehensive Archon Implementation Planning skill 17.6k ★
Contributors — Thank you to everyone who has contributed to making planning-with-files better 16.8k ★

README

ClaudeQB

[![validate](https://github.com/alicankiraz1/ClaudeQB/actions/workflows/validate.yml/badge.svg?branch=main)](https://github.com/alicankiraz1/ClaudeQB/actions/workflows/validate.yml)

**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.
**Pro