Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting any CodexAI task; load this baseline before routing, editing, or claiming work is done.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Classify the request, load the smallest matching skill, check dependencies before edits, run a quality gate before claiming done, and reply in the user's language. Scripts: --help first.
P0 baseline. Stack other skills on top of this file; do not replace it.
Before clarifying, exploring, editing, or answering any workflow-like request, match aliases, agents, and workflows. Load only the smallest sufficient skill set. Do not skip a relevant skill because the task "looks simple". Do not bulk-load unrelated skills.
For a single page or component, use codex-frontend-design fast path. For prototype/fullstack, use spec-first $prototype. Documents, reports, and guides load codex-document-writer.
Before creating files or folders, inspect the repository and follow its existing conventions. Co-locate new code and tests with their owning feature; create only directories needed for the requested work. Do not scaffold every optional CodexAI area, empty placeholders, duplicate outputs, or catch-all folders such as misc, output, or final. Put CodexAI-owned artifacts in the documented owner paths; see docs/project-artifact-layout.md and codex-domain-specialist/references/file-structure.md when deciding structure.
If the pack is not loaded, identify the installed host and run python skills/.system/scripts/install.py doctor --host <host> --scope user. Use --host all only after installing every corresponding host integration.
| Alias | Full Command | Skill |
|---|---|---|
$plan | $codex-plan-writer | codex-plan-writer |
$debug | $codex-systematic-debugging | codex-systematic-debugging |
$create | workflow-create + TDD | codex-workflow-autopilot |
$gate | $codex-execution-quality-gate | codex-execution-quality-gate |
$check | auto_gate.py --mode quick | codex-execution-quality-gate |
$design | $codex-frontend-design | codex-frontend-design |
$ux | $codex-frontend-design | codex-frontend-design |
$memory | $codex-project-memory | codex-project-memory |
$today | codex-project-pulse daily brief | codex-project-pulse |
$doctor | install.py doctor | .system |
$doc | $codex-document-writer | codex-document-writer |
$report | $codex-document-writer | codex-document-writer |
$brainstorm | brainstorm mode | codex-workflow-autopilot |
$review-feedback | receiving code review feedback | codex-subagent-execution |
Critical aliases: $hook $preflight $health $init-profile $knowledge $spec $prototype $think $decide $check $check-full $check-deploy $init-docs $check-docs $install-hooks $install-ci $today $pulse.
Also: $direction $refine $polish $fix $build $docs $pipeline $release-gate. Full catalog: ../.system/references/aliases.json.
Request types include question, survey, simple-code, complex-code, prototype, debug, review, and | document |.
When routing returns suggested_agent, load .agents/<name>.md.
| Agent | Domain |
|---|---|
design-lead | Brief, UX contract, visual direction |
frontend-specialist | UI implementation |
visual-quality-reviewer | Post-UI review |
backend-specialist | API and persistence |
security-auditor | Security review |
debugger | Root cause |
test-engineer | Tests |
devops-engineer | CI/CD |
planner | Planning |
scrum-master | Scrum |
Missing agent files fall back to codex-domain-specialist. Honor file_ownership.
$plan $debug $create $build $prototype $review $deploy $handoff $fix $docs $refine load .workflows/<name>.md.
No "done" without fresh evidence. Details: references/baseline-policy.md.
Also load: references/debugging-and-recovery.md, references/scope-escalation.md, references/workflow-cross-reference.md.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
日本語の概要は準備中です。原文の説明を表示しています。
Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
日本語の概要は準備中です。原文の説明を表示しています。
Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
日本語の概要は準備中です。原文の説明を表示しています。