Menu
Use when code changes may affect API contracts, architecture, workflows, or user-facing behavior. Updates only the affected documentation sections.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
์ฌ์ฉ์์ ๋ง์ฐํ ์์ด๋์ด๋ฅผ ํ ์ง๋ฌธ์ฉ ์ธํฐ๋ทฐํด์ ์คํ ๊ฐ๋ฅํ MVP ์คํ์ผ๋ก ๋ง๋ ๋ค
Socratic deep interview with mathematical ambiguity gating before explicit execution approval
Consensus planning entrypoint that auto-gates vague team/ultragoal requests before execution
Multi-worker GJC tmux team orchestration
Create and execute durable repo-native multi-goal plans over GJC goal mode artifacts.
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex. The first-party method drives the real `codex app-server` against an isolated CODEX_HOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by asserting hook/started + hook/completed notifications. Also: isolated install verification, per-component hook probes, a tmux TUI smoke, and runtime log observation (RUST_LOG / logs SQLite / /debug-config). Ships tested helper scripts each with a --self-test. Use whenever someone changes anything under packages/omo-codex or wants to QA, smoke-test, verify, or debug the Codex plugin, its hooks/components, the installer/config.toml, the app-server flow, or the Codex TUI. Triggers: codex qa, qa codex, codex-qa, test codex plugin, verify codex hook, codex app-server, lazycodex qa, isolated CODEX_HOME, prove codex hook fired, codex tui test.
| name | doc-sync |
| description | Use when code changes may affect API contracts, architecture, workflows, or user-facing behavior. Updates only the affected documentation sections. |
When code changes are made:
docs/api-contract.mddocs/architecture.md> TODO: doc-sync verification needed line and report it.python scripts/docs_impact_check.py --require-report to confirm doc-code drift is resolved.