[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-85175":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":15,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":16,"rankGlobal":10,"rankLanguage":10,"license":17,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":18,"hasPages":18,"topics":20,"createdAt":10,"pushedAt":10,"updatedAt":21,"readmeContent":22,"aiSummary":10,"trendingCount":15,"starSnapshotCount":15,"syncStatus":23,"lastSyncTime":24,"discoverSource":25},85175,"CodexQB","alicankiraz1\u002FCodexQB","alicankiraz1","CodexQB is a Codex plugin that packages a three-step project planning workflow as a reusable skill.","",null,"Python",78,9,59,0,38.54,"MIT License",false,"main",[],"2026-06-15 10:05:14","# CodexQB\n\n[![validate](https:\u002F\u002Fgithub.com\u002Falicankiraz1\u002FCodexQB\u002Factions\u002Fworkflows\u002Fvalidate.yml\u002Fbadge.svg?branch=main)](https:\u002F\u002Fgithub.com\u002Falicankiraz1\u002FCodexQB\u002Factions\u002Fworkflows\u002Fvalidate.yml)\n\n**Repo-aware planning for Codex.** CodexQB turns a project repository into a durable planning package: main plan, existing-project autopsy, phase sub-plans, QA audit, and a gated implementation handoff.\n\n![CodexQB workflow and release validation](docs\u002Fassets\u002Fcodexqb-workflow.png)\n\nCodexQB is a Codex plugin that installs the `$codexqb` skill. It is built for software, AI, infrastructure, security, and automation projects where planning needs to be evidence-backed, reviewable, and ready for step-by-step execution.\n\nThe current release is hardened for repository marketplace distribution: dependency-free `make check`, GitHub Actions validation, and tracked-file sanitized exports through `make export-sanitized`.\n\n## Why CodexQB\n\n- **Repo-aware intake:** CodexQB inspects the current repository before asking questions, then proposes evidence-backed defaults for project name, intent, target end state, and constraints.\n- **Durable planning docs:** Output is written under `Planner-docs\u002F` so long planning work survives context changes and can be reviewed like normal project documentation.\n- **Project Autopsy:** Existing projects get a focused `Autopsy.md` report covering modules, features, placeholders, technical debt, integration gaps, validation gaps, and readiness risks.\n- **Full phase decomposition:** The main plan can be expanded into ordered phase folders and detailed sub-plan files, using Autopsy feedback when available.\n- **QA before implementation:** The audit step checks coverage, naming, ordering, section structure, readiness, security\u002Fgovernance, and implementation preparedness.\n- **Gated execution handoff:** CodexQB does not implement product changes itself. It prints a separate Goal mode prompt only when the audit says implementation can begin, then guides that run through the READY queue in small verified slices.\n\n## Workflow\n\n| Step | What CodexQB Does | Output |\n| --- | --- | --- |\n| 1. Repo Scan + Main Plan | Reads the repository, asks four enriched intake questions, and creates the master plan. | `Planner-docs\u002FMain-Planing.md` |\n| 1.5 Autopsy | For existing projects, audits current project structure, features, placeholders, technical debt, integrations, validation, security, and readiness. | `Planner-docs\u002FAutopsy.md` |\n| 2. Phase Sub-Plans | Expands every main phase into detailed implementation-ready sub-plans. | `Planner-docs\u002FSub-Planing-Index.md`, `Planner-docs\u002FFaz-*-Plans\u002F*.md` |\n| 3. QA Audit | Audits coverage, structure, quality, readiness, and governance without repairing files. | `Planner-docs\u002FSub-Planing-Audit.md` |\n| 4. Gated Handoff | Prints a copy-ready implementation Goal prompt when Step 3 passes. | Text-only Goal mode prompt |\n\nStep 1 runs in the current Codex thread. Steps 2, 3, and 4 are intentionally handed off as text-only Goal mode prompts so the user stays in control of long-running work.\n\n## Quick Start\n\nAdd this repository as a Codex plugin marketplace:\n\n```bash\ncodex plugin marketplace add alicankiraz1\u002FCodexQB --ref main\ncodex plugin add codexqb@codexqb\n```\n\nIf the repository is private, your Codex\u002FGitHub environment must have access to `alicankiraz1\u002FCodexQB`.\n\nStart a new Codex thread in the project you want to plan, then ask:\n\n```text\nUse $codexqb to inspect this repo and plan this project.\n```\n\nCodexQB will inspect the repository briefly, then ask for:\n\n- `PROJECT_NAME`\n- `PROJECT_INTENT`\n- `TARGET_END_STATE`\n- `KNOWN_CONSTRAINTS`\n\nCodexQB asks intake questions in the user's language when practical. Generated Planner-docs artifacts are English by default unless the user explicitly requests another body language. Required document headings remain English for validator stability.\n\nFor existing repositories, the questions include repo-derived suggestions. For empty or minimal repositories, CodexQB falls back to concise generic questions and marks repository evidence as limited.\n\n## Generated Artifacts\n\nCodexQB writes planning artifacts under the target project's `Planner-docs\u002F` directory:\n\n```text\nPlanner-docs\u002F\n  Main-Planing.md\n  Autopsy.md\n  Sub-Planing-Index.md\n  Sub-Planing-Audit.md\n  Faz-0-Plans\u002F\n    Faz0.1-*.md\n  Faz-1-Plans\u002F\n    Faz1.1-*.md\n```\n\nThe `Planing` spelling is intentionally preserved because the bundled planner prompts and validators use these exact filenames.\n\n## Validator\n\nThe skill includes a read-only validator:\n\n```bash\npython3 plugins\u002Fcodexqb\u002Fskills\u002Fcodexqb\u002Fscripts\u002Fvalidate_planner_docs.py --root \u002Fpath\u002Fto\u002Fproject --mode step2 --strict\npython3 plugins\u002Fcodexqb\u002Fskills\u002Fcodexqb\u002Fscripts\u002Fvalidate_planner_docs.py --root \u002Fpath\u002Fto\u002Fproject --mode step3 --strict\npython3 plugins\u002Fcodexqb\u002Fskills\u002Fcodexqb\u002Fscripts\u002Fvalidate_planner_docs.py --root \u002Fpath\u002Fto\u002Fproject --mode step4\n```\n\nThese commands are for manual validation from a CodexQB repository checkout. When running through an installed plugin, CodexQB should use the bundled validator path exposed by the active skill; if that path is unavailable, it should perform equivalent all-file validation and report the fallback clearly.\n\nThe validator checks required sections, phase folders, filename conventions, index references, duplicate numbering, unindexed files, length-bounded secret patterns, and Step 4 readiness. P0\u002FP1 audit findings block the implementation handoff.\n\nRepository maintainers can run the dependency-free repo check with:\n\n```bash\nmake check\n```\n\n`make check` validates plugin JSON, required package files, `agents\u002Fopenai.yaml` semantic fields, stale invocation names, tracked-file secret hygiene, archive hygiene, and the unit test suite without requiring PyYAML or local Codex validator dependencies.\n\n## Release Validation\n\nRun this before sharing, committing, or pushing release changes:\n\n```bash\nmake check\n```\n\nThe repository also includes GitHub Actions at `.github\u002Fworkflows\u002Fvalidate.yml`, which runs the same check on pushes to `main` and pull requests.\n\nFor sanitized zip sharing, use the tracked-file archive target instead of Finder or generic directory compression:\n\n```bash\nmake export-sanitized\n```\n\nThis creates `CodexQB-sanitized.zip` from `git archive`, excluding `.git\u002F`, ignored Python caches, local env files, runtime folders, and other untracked local clutter. The default validation gate also checks that forbidden tracked archive entries are not present.\n\n## Safety Model\n\nCodexQB is planning-first. Steps 1-3 should not:\n\n- implement product features;\n- refactor source code;\n- install dependencies;\n- run destructive commands;\n- commit, push, deploy, or open pull requests;\n- write secrets, tokens, credentials, private keys, or local sensitive environment values into planning files.\n\nGenerated plans should distinguish documentation readiness, local readiness, live readiness, production readiness, and operational evidence.\n\n## Repository Layout\n\n```text\n.agents\u002Fplugins\u002Fmarketplace.json\n.github\u002Fworkflows\u002Fvalidate.yml\nMakefile\nplugins\u002Fcodexqb\u002F\n  .codex-plugin\u002Fplugin.json\n  skills\u002Fcodexqb\u002F\n    SKILL.md\n    agents\u002Fopenai.yaml\n    scripts\u002Fvalidate_planner_docs.py\n    references\u002F\n      First-Planner.md\n      Autopsy-Planner.md\n      Second-Planner.md\n      Third-Planner.md\n      Fourth-Planner.md\n      repo-aware-intake.md\n      workflow-quality.md\ndocs\u002F\n  INSTALLATION.md\n  MAINTAINING.md\n  USAGE.md\n  assets\u002Fcodexqb-workflow.png\nscripts\u002F\n  validate.sh\ntests\u002F\nLICENSE\nREADME.md\n```\n\n## Documentation\n\n- [Installation](docs\u002FINSTALLATION.md)\n- [Usage](docs\u002FUSAGE.md)\n- [Maintaining CodexQB](docs\u002FMAINTAINING.md)\n\n## Public Plugin Directory Status\n\nCodexQB currently uses repository marketplace distribution. Public directory or workspace sharing distribution can be revisited separately; this release focuses on repo-marketplace installation and local\u002Fteam validation.\n\n## License\n\nMIT. See [LICENSE](LICENSE).\n",2,"2026-06-15 02:30:14","CREATED_QUERY"]