메뉴
Use when syncing website roadmap page against current GitHub issues and PRs. Matches open/closed issues + open/merged PRs to roadmap features, updates statuses, adds links, flags unlinked issues as candidates. Triggers: "sync roadmap", "/ocx-sync-roadmap".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when a diff or PR is too big to review by eye and the question is "what should I actually look at" — sorts each changed line into wire / CLI / API / logic / test / doc tiers, then opens a clickable local page with the real hunks. A reading order, never a verdict.
Use to implement a plan artifact from `/swarm-plan`, or a free-text implementation task with contract-first TDD + Review-Fix Loop. Tier (`low | auto | high | max`) scales builder model, loop rounds, review breadth, and Codex code-diff gate.
Use for branch, PR, or diff review before landing on main. Tier (`low | auto | high | max`) scales breadth from single reviewer to adversarial panel with architect + SOTA-gap + Codex cross-model gate. Triggers: "review", "/swarm-review", pre-merge checks.
Use when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature or worktree branch. OCX working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.
Use for feature planning, task decomposition, multi-perspective research, or ADR scaffolding. Tier (`low | auto | high | max`) scales research depth, architect model, and review breadth. Canonical research primitive for AI config / ADR work.
Use when the user says "codex review", "/codex-adversary", "adversarial review", "cross-model review", or asks for a different-model second opinion on a diff or plan artifact. Complements `/swarm-review` via Codex-CLI. Scopes: code-diff (default), plan-artifact (gate for `/swarm-plan`).
| name | ocx-sync-roadmap |
| description | Use when syncing website roadmap page against current GitHub issues and PRs. Matches open/closed issues + open/merged PRs to roadmap features, updates statuses, adds links, flags unlinked issues as candidates. Triggers: "sync roadmap", "/ocx-sync-roadmap". |
Sync website/src/docs/roadmap.md with current GitHub issues + PRs.
Prefer MCP tools mcp__github__list_issues and mcp__github__list_pull_requests — return typed objects, no shell parsing, no subprocess cost. Request state: "all", paginate as needed.
Fallback (MCP unavailable or missing field projection), run parallel:
gh issue list --state all --limit 200 --json number,title,state,labels
gh pr list --state all --limit 200 --json number,title,state,labels
Read website/src/docs/roadmap.md, parse:
<RoadmapItem> (title, accent, icon)<RoadmapFeature> within (text, status, issue number, PR number)Each roadmap feature with issue or pr prop:
| GitHub State | → Roadmap Status |
|---|---|
| Issue open, no PR | planned |
| PR open | active |
| PR merged | shipped |
| Issue closed (no PR) | shipped |
Update status prop on each <RoadmapFeature>.
Scan issues + PRs with titles matching roadmap themes:
| Issue/PR title contains | Likely roadmap item |
|---|---|
| layer, compose, multi-layer | Composable Packages |
| depend, resolution, toolchain | Dependencies |
| require, capability, glibc, variant | System Requirements |
| referrer, sbom, signature, attestation | Referrer API |
| bazel, cmake, gradle, action, devcontainer, shim | Interoperability |
| semver, stable, schema, diagnostic, symlink, path | Hardening |
Show summary table of all changes before apply:
## Roadmap Sync Proposal
### Status Updates
| Feature | Old Status | New Status | Reason |
|---------|-----------|------------|--------|
| Multi-layer artifacts | active | shipped | PR #22 merged |
### New Links
| Feature | Added |
|---------|-------|
| Schema validation | issue #30 |
### Suggested New Features
| Item | Feature | Issue/PR |
|------|---------|----------|
| Hardening | Error context improvements | #35 |
Apply these changes? [y/n]
Edit website/src/docs/roadmap.md with approved changes.
<RoadmapFeatures> blockissue and pr can set on same feature<RoadmapFeature status="active" issue="20" pr="22">Multi-layer artifacts</RoadmapFeature>
| Prop | Values | Description |
|---|---|---|
status | shipped, active, planned | Feature progress |
issue | number | GitHub issue (links to ocx-sh/ocx/issues/{n}) |
pr | number | GitHub PR (links to ocx-sh/ocx/pull/{n}) |