codexqb

Inspect repository evidence and create durable, reviewable implementation plans.

185|17|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/alicankiraz1/CodexQB --skill codexqb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codexqb
Source: https://github.com/alicankiraz1/CodexQB/tree/main/plugins/codexqb/skills/codexqb
Command: npx skills add https://github.com/alicankiraz1/CodexQB --skill codexqb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

CodexQB prevents generic or premature coding plans by inspecting the current repository, grounding decisions in evidence, and turning project goals into durable, reviewable implementation plans.

Core Features & Use Cases

  • Repository-Aware Planning: Analyze project structure, documentation, configuration, tests, integrations, and existing planning artifacts before defining the roadmap.
  • Gated Delivery Workflow: Create master plans, project autopsies, ontology and comprehension artifacts, phase sub-plans, QA audits, and controlled implementation handoffs.
  • Evidence and Safety Controls: Preserve ledger continuity, enforce file boundaries, validate planner artifacts, separate local from live readiness, and require explicit approval before implementation.
  • Use Case: For an existing software repository, use CodexQB to identify architectural gaps, define small validated delivery phases, audit implementation readiness, and prepare bounded Goal-mode handoffs without modifying product code during planning.

Quick Start

Use the codexqb skill to inspect this repository and create an evidence-backed project plan.

Frequently Asked Questions about codexqb

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an evidence-backed implementation plan for an existing software repository?

Repository planning uses project evidence inspection to ground decisions, producing durable implementation plans. It analyzes structure, documentation, and tests before defining a phased delivery roadmap for software, AI, or infrastructure projects.

What is the best way to break down a software project into validated delivery phases?

Phase decomposition breaks project goals into small, validated delivery phases using structured validation. It creates master plans and phase sub-plans to ensure reviewable, gated implementation handoffs without modifying product code during planning.

How do I audit implementation readiness before starting a repository handoff?

Implementation readiness auditing validates planner artifacts, enforces file boundaries, and separates local from live readiness. It requires explicit approval and controlled artifact writes to ensure safe, gated goal-mode handoffs.

Can I run a project autopsy on my existing automation repository to identify architectural gaps?

Project autopsy inspects existing automation repositories to identify architectural gaps and comprehension artifacts. It preserves ledger continuity and applies to security and infrastructure repositories requiring evidence and safety controls.

Does repository planning require modifying product code during the planning phase?

Repository planning does not modify product code during the planning phase. It enforces approval-aware safety boundaries, separates local from live readiness, and only produces controlled planning artifacts.

When do I need ontology and comprehension artifacts for repository planning?

Ontology and comprehension artifacts are needed when inspecting complex project structure for phased planning. They preserve ledger continuity and support gated delivery workflows for AI and software repositories.