メニュー
When and how to update project documentation. Use whenever you change architecture, patterns, features, or user-facing behavior; or when implementing a development phase.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Install ComfyUI Assistant as a ComfyUI custom node. Use when performing or troubleshooting installation (clone, Python deps, frontend build, restart).
For complex user requests — evaluate, investigate, ask questions, propose a plan, accept modifications, then execute. Use when the request is multi-step, ambiguous, or high-impact.
Workflow execution and complete workflow generation tools (executeWorkflow, applyWorkflowJson). Use when the user wants to run a workflow or build a complete workflow from a description.
Python backend modules, chat request lifecycle, SSE format, and API endpoints
System prompt assembly from system_context, user_context, and environment sources
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
| name | documentation |
| description | When and how to update project documentation. Use whenever you change architecture, patterns, features, or user-facing behavior; or when implementing a development phase. |
Golden rule: If code changes, documentation changes. Update docs in the same commit or PR as the code. Do not defer documentation to "later" or a separate PR.
| Trigger | What to update (see below) |
|---|---|
| Architecture changes | project-context, skills (e.g. tools), READMEs, API docs |
| Pattern or practice changes | conventions.md, relevant skill references, README examples |
| New feature (tool, component, API) | project-context, relevant skill, README, tool defs if tools |
| Phase implementation or iteration | .project/development/<phase_name>/implemented.md |
| User-facing behavior or usage | doc/, README |
| New or changed endpoints, routes | project-context, API docs, README if user-facing |
Before committing any such change, ask: "What documentation does this change affect?" Then update all affected files.
| File / directory | Purpose | Update when |
|---|---|---|
.agents/project-context.md | Project overview, architecture, structure, features | Architecture, stack, structure, or new features |
.agents/conventions.md | Development standards | New or changed patterns, practices |
.agents/skills/<topic>/ | Topic-specific guides (e.g. tools, runtime) | That area changes (e.g. new tool → tools skill) |
.project/development/<phase>/implemented.md | Phase deliverables and iteration log | Implementing or iterating that phase |
.project/planning/ | Planning, design, WIP | New planning docs go here (not at root) |
README.md | User-facing overview and usage | Feature or usage changes |
doc/ | User and developer docs (installation, config, skills, tools, roadmap, dev_docs) | User-facing behavior, setup, or dev process |
tools_definitions.py | Backend tool declarations | Any tool addition or change |
Details and examples: .agents/conventions.md — "Documentation Maintenance Protocol" and "Documentation Sources of Truth".
.agents/project-context.md if architecture, structure, or features changed.agents/conventions.md if patterns or practices changed.agents/skills/ (e.g. tools, setup) if that area changedREADME.md if usage or features changeddoc/ if user-facing behavior, setup, or dev process changed.project/development/<phase>/implemented.md if implementing or iterating a phasetools_definitions.py) if tools changedWhen implementing or iterating a development phase:
.project/development/<phase_name>/ (e.g. .project/development/phase_3/).implemented.md in that folder with:
.project/development/phase_0/implemented.md, phase_1/implemented.md, phase_2/implemented.md.