CodexQB banner
alicankiraz1 alicankiraz1

CodexQB

Security community

Description

CodexQB is a Codex plugin for evidence-backed repo comprehension, planning, QA audit, and gated implementation handoffs.

Installation

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

README

CodexQB

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

**Evidence-backed, vibecoding-first project planning for Codex.**

CodexQB reads the repository before it plans. It turns the current project into a durable, reviewable planning package under `Planner-docs/`, then prepares small implementation handoffs that can be checked before code changes begin.

![CodexQB workflow](docs/assets/codexqb-workflow.png)

What it gives you

  • A repository-aware main plan instead of a generic task list.
  • An existing-project autopsy, optional project comprehension, and project ontology.
  • Phase plans with dependencies, validation commands, risks, and acceptance criteria.
  • A QA audit and controlled Goal/Apply handoff for small, verifiable slices.
  • A planning ledger that keeps decisions and implementation evidence durable across long Codex sessions.

CodexQB is useful for software, AI, infrastructure, security, and automation projects. It is planning-first: it does not silently turn a planning request into product-code changes.

Quick start

Install from the repository marketplace:

codex plugin marketplace add alicankiraz1/CodexQB --ref main
codex plugin add codexqb@codexqb

Open a new Codex task in the project you want to plan and invoke the skill explicitly:

Use $codexqb to inspect this repo and plan this project.

CodexQB is configured with `allow_implicit_invocation: false`. Normal Codex prompts should not activate it; only an explicit `$codexqb` request should start the workflow.

The intake covers four stable fields:

  • PROJECT_NAME
  • PROJECT_INTENT
  • TARGET_END_STATE
  • KNOWN_CONSTRAINTS

CodexQB asks intake questions in the user's language when practical. Generated Planner-docs artifacts are English by default unless the user explicitly requests another content language. Required document headings rem