메뉴
Use when repo reference artifacts need updating — roadmap, decision records, backlog status, or completed history. Frequently invoked at project completion, often chained from `oat-project-document`, to ensure `.oat/repo/reference/` state reflects what shipped.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | oat-pjm-update-repo-reference |
| version | 1.1.1 |
| description | Use when repo reference artifacts need updating — roadmap, decision records, backlog status, or completed history. Frequently invoked at project completion, often chained from `oat-project-document`, to ensure `.oat/repo/reference/` state reflects what shipped. |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | Read, Write, Bash, Glob, Grep, AskUserQuestion |
Keep this repo's OAT reference documentation consistent as implementation evolves, using the file-backed backlog structure under .oat/repo/reference/backlog/.
OAT MODE: Repo Reference Sync
Purpose: Update backlog, roadmap, completed history, and decision records so repo reference docs stay trustworthy after implementation changes.
When executing this skill, provide lightweight progress feedback so the user can tell what’s happening after they confirm.
Print a phase banner once at start using horizontal separators, e.g.:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OAT ▸ UPDATE REPO REFERENCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Before multi-step work, print short step indicators, e.g.:
[1/4] Identifying changed OAT surfaces…[2/4] Updating canonical reference docs…[3/4] Regenerating managed backlog index…[4/4] Running reference sanity checks…Write down a 1-3 bullet summary of the implementation change:
Before editing any backlog files or running backlog regeneration, run:
oat backlog init
This command is idempotent and ensures .oat/repo/reference/backlog/index.md exists with the exact managed markers required by the CLI:
<!-- OAT BACKLOG-INDEX -->
<!-- END OAT BACKLOG-INDEX -->
Do not hand-author or rename those managed markers.
For recently completed or in-progress projects, read discovery.md, spec.md, design.md, and implementation.md as applicable.
Promote notable findings into one of:
.oat/repo/reference/backlog/items/.oat/repo/reference/backlog/completed.md.oat/repo/reference/decision-record.md.oat/repo/reference/roadmap.mdUpdate these files as applicable:
.oat/repo/reference/current-state.md.oat/repo/reference/roadmap.md
Now / Next / Later structure when editing roadmap priorities..oat/repo/reference/backlog/index.md
## Curated Overview section by hand..oat/repo/reference/backlog/items/*.md
.oat/repo/reference/backlog/completed.md
.oat/repo/reference/backlog/archived/*.md
.oat/repo/reference/decision-record.mdIf you modify backlog item files or the completed archive structure, run:
oat backlog regenerate-index
Use the Grep tool for focused searches:
backlog\.md|backlog-completed\.md|deferred-phases\.md across .oat/repo/reference, docs/oat, .agents/skills, and AGENTS.md.\.oat/repo/reference/backlog/(index|completed|items|archived) across the same locations.Confirm that:
backlog/items/backlog/index.md curated sectionbacklog/completed.mdNow / Next / Later structureProvide:
oat backlog regenerate-index was runRun when you need to evaluate agent instruction file coverage, quality, and drift. Produces a severity-rated analysis artifact. Run before oat-agent-instructions-apply to identify what needs improvement.
Run when you need to evaluate documentation structure, navigation, and coverage against the OAT docs app contract. Produces a severity-rated analysis artifact for oat-docs-apply.
Use when the user explicitly asks to continue discovery for an active spec-driven OAT project — e.g. "continue discovery", "run discovery", or confirms a previously offered discovery step. Do NOT auto-invoke for new ideas or quick-mode projects. Gathers requirements and context before spec/design.
Use when you have an external markdown plan to execute with OAT. Preserves the source plan and normalizes it into canonical plan.md format.
Use when design.md is complete and executable implementation tasks are needed. Breaks design into bite-sized TDD tasks in canonical plan.md format.
Use when authoring or mutating plan.md in any OAT workflow. Defines canonical format invariants — stable task IDs, required sections, review table rules, and resume guardrails.