メニュー
Use when code changes may affect API contracts, architecture, workflows, or user-facing behavior. Updates only the affected documentation sections.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
사용자의 막연한 아이디어를 한 질문씩 인터뷰해서 실행 가능한 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.