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 for role-scoped FE/BE/DevOps/Admin/QA project docs under .codex/project-docs to preserve micro-context across long projects.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when a project needs durable FE/BE/DevOps/Admin/QA context. Initialize only the project brief by default; create role folders for the roles this project actually needs, then keep those docs current as code changes.
$role-docs, $init-docs, or $check-docs.Role docs are project-local artifacts, not always-loaded context. Read only the role docs needed for the current task, then update the same docs before completion when code behavior, contracts, architecture, UI patterns, deployment, admin flows, or tests changed.
init_role_docs.py --project-root <path> (project brief + ADR template only)init_role_docs.py --project-root <path> --roles frontend,qainit_role_docs.py --project-root <path> --roles allupdate_role_docs.py --project-root <path> --role <role> --doc <doc-id> --summary <text> --files <csv>check_role_docs.py --project-root <path> --changed-files <csv>build_role_docs_index.py --project-root <path>skills/.system/REGISTRY.md for full script paths.| Role | Owns |
|---|---|
frontend-specialist | frontend/FE-*, admin UI flows, dashboards, reports |
backend-specialist | backend/BE-*, admin permissions, contracts, data management |
devops-engineer | devops/DO-* |
test-engineer | qa/QA-* |
security-auditor | auth/security, permissions, audit-log docs |
planner | project brief, ADR template, admin scope |
.codex/project-docs/.$init-docs.$check-docs or map changed files manually.PROJECT-BRIEF.md and decisions/ADR-0001-template.md.frontend/FE-*.md, backend/BE-*.md, devops/DO-*.md, admin/AD-*.md, and/or qa/QA-*.md for the selected roles.index.json is created only when the index builder runs.templates/role_docs_manifest.json: canonical role docs, owners, and doc metadata.templates/project-brief-template.md: project-level context template.templates/role-doc-template.md: shared role-document template.templates/adr-template.md: decision record template.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。