ocx-sync-roadmap

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 Roadmap

Sync website/src/docs/roadmap.md with current GitHub issues + PRs.

Workflow

Step 1: Gather GitHub State

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

Step 2: Read Current Roadmap

Read website/src/docs/roadmap.md, parse:

• Each <RoadmapItem> (title, accent, icon)
• Each <RoadmapFeature> within (text, status, issue number, PR number)

Step 3: Match and Update

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>.

Step 4: Find Unlinked Issues

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

Step 5: Propose Changes

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]

Step 6: Apply

Edit website/src/docs/roadmap.md with approved changes.

Feature Conventions

• Feature text: 1-3 words, nominative, consistent capitalization
• Shipped first within <RoadmapFeatures> block
• Active next, planned last
• Both issue and pr can set on same feature

Component Reference

<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})