Skill: Update Docs

Skill: Update Docs

Steps

• Identify the traceability chain — From the merged PR, identify: Forgejo issue number, phase note slug, plan note slug, project page slug. The board item (if any) links to the Forgejo issue URL.
• Close the Forgejo issue — Check if the issue is already closed. If not, close it.
• Update the phase note — mcp__pal-e-docs__update_note(slug="...", status="completed"). Add deliverables summary if not already there. Record the Forgejo issue number and PR number. The update_note hook automatically propagates this status change to the corresponding board item column — no manual board move needed.
• Update the plan note — mcp__pal-e-docs__get_note(slug="...") to read current state. Update the phase progress summary. If all phases are complete, set plan status to completed.
• Update the project page — mcp__pal-e-docs__get_note(slug="project-...") then update:
• Sync the project board — Call sync_board(board_slug) on the relevant project board to reconcile all phase items. This ensures any new phases, status changes, or completed items are reflected on the board. Manual board item creation/movement is only needed for non-phase items (repos, ad-hoc TODOs).
• Update memory — Edit MEMORY.md if the current state of the platform or plans changed.
• Capture discovered scope — For any bugs or future work identified during implementation or QA, create notes: mcp__pal-e-docs__create_note(slug="todo-...", tags="todo,open").
• Report — Summarize what was updated. Confirm the board is synced and phase items are in the correct columns.

Related

• sop-post-merge-docs — the SOP this skill implements
• pr-lifecycle — Stage 8 triggers this skill
• agent-workflow — Step 12 references this workflow