Roadmap hygiene

A roadmap loses trust one stale item at a time. This check doesn't judge what should be on the roadmap; it judges whether what's on it is clear, current, and owned.

Before you start

If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.

Step 1: Inventory

For each item, capture what the source shows:

Record "None" or "Unknown" where a field is empty. Don't fill gaps.

Step 2: Check each item

Flag every item that has one or more of these problems:

Use dates from the source and today's date. Show your evidence for "stale" and "contradiction."

Step 3: Recommend one action per flagged item

• Update: status or date needs refreshing; name who to ask
• Assign owner: name who should decide
• Rewrite: suggest a clearer title in plain words
• Merge: combine with a duplicate
• Move to later / archive: for zombies; owner decides
• Remove from customer-facing view: for overpromises

Recommend only. Never change, move, or delete roadmap items yourself.

Output

# Roadmap hygiene — [Roadmap name] — [Date]

**Summary:** [N] items reviewed · [N] flagged · Biggest issue: [one sentence]

## Fix before the next review
| Item | Problem | Evidence | Action | Ask |

## Lower priority
[Same table]

## Clean
- [N] items with no issues

Customer-facing issues (overpromises, contradictions with public release notes) always go to the top.

Related skills

• quarterly-planning-prep — clean up before planning starts
• duplicate-request-merging — tie requests to roadmap items
• decision-log — record what was cut and why