メニュー
Use for role-scoped FE/BE/DevOps/Admin/QA project docs under .codex/project-docs to preserve micro-context across long projects.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codex-role-docs |
| description | Use for role-scoped FE/BE/DevOps/Admin/QA project docs under .codex/project-docs to preserve micro-context across long projects. |
| load_priority | on-demand |
Use this skill when a project needs durable FE/BE/DevOps/Admin/QA context. Generate .codex/project-docs/ once, then keep role docs updated 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>update_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.mdindex.jsondecisions/ADR-0001-template.mdfrontend/FE-*.mdbackend/BE-*.mddevops/DO-*.mdadmin/AD-*.mdqa/QA-*.mdtemplates/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 for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.
Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
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.