메뉴
Use when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | refresh-project-docs |
| description | Use when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows. |
| metadata | {"version":"1.0","dependencies":[]} |
Update documentation from the live repo state, not from outdated docs or feature-memory summaries.
If the user asks to improve or templatize a docs-refresh prompt, route to pulse:prompt-leverage first, then return here for docs execution.
Docs execution: inspect the repo and update the relevant docs directly.Find the docs that may need to move together:
README.mddocs/ pagesDo not assume the README is the only source that matters.
Treat the repository as the source of truth.
Check the most authoritative artifacts available, such as:
When commands, flags, options, or workflows can be verified from source, verify them instead of inferring.
Capture what the docs need to describe in their current form:
Write as if the documented behavior has always been part of the project.
Use these rules without exception:
Avoid release-note phrasing such as:
we addednow supportsrecentlyhas been updatedX is now YCheck that:
Stop and correct the approach if any of these appear:
README.md when the same information lives elsewhereThis skill is complete when the edited docs:
Use after completed Pulse work when the user asks to capture post-cycle machine-readable learnings for future planning and execution.
Use when the user asks to distill accumulated dev-notes into reader-facing topic knowledge, rather than to capture a new note or update machine memory.
Use when implementing approved Pulse beads, either as a swarm worker or as a single worker when swarming is unavailable.
Use before implementation planning when feature intent is clear but implementation decisions are still unresolved, and the user needs those decisions locked first.
Use after pulse:exploring when locked decisions are ready and the user needs a mode-gated plan with an approved work shape and current-work prep for validation.
Use when starting any Pulse workflow, resuming a Pulse session, or before planning or execution when tool readiness or onboarding state may block the flow.