Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/unixcrh/phuryn-pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/transform-roadmap)<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/transform-roadmap"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/transform-roadmap/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/unixcrh/phuryn-pm-skills/transform-roadmap"><img src="https://agentmods.dev/badge/commands/unixcrh/phuryn-pm-skills/transform-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00767 |
| Opus 5 | $0.00007 | $0.00383 |
| Sonnet 5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
transform-roadmap scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to transform-roadmap — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/transform-roadmap -- Outcome-Focused Roadmap
Take a list of planned features or an output-focused roadmap and rewrite it as an outcome-focused roadmap that communicates why instead of what.
Invocation
/transform-roadmap [paste your feature list or roadmap]
/transform-roadmap [upload a roadmap doc, spreadsheet, or screenshot]
Workflow
Step 1: Accept the Current Roadmap
Accept in any format:
- Feature list or backlog items
- Roadmap document (Now/Next/Later, quarterly, timeline)
- Spreadsheet or Gantt chart export
- Screenshot of a roadmap tool
Parse each item to extract: feature name, description, target date/timeframe, and any context.
Step 2: Understand Strategic Context
Ask:
- What are the product goals or OKRs for this period?
- Who is the audience for this roadmap? (execs, engineering, customers, board)
- What format do you prefer? (Now/Next/Later, quarterly, timeline)
Step 3: Transform Each Item
Apply the outcome-roadmap skill:
For each feature/output on the roadmap:
- Identify the user or business outcome it's trying to achieve
- Rewrite as an outcome statement: "[Verb] [metric/experience] for [user segment]"
- Group features that serve the same outcome under one initiative
- Add success metrics to each outcome
Before → After examples:
- "Build SSO integration" → "Reduce enterprise onboarding friction — target: 50% faster time-to-first-value for enterprise accounts"
- "Redesign dashboard" → "Help power users find insights faster — target: 30% reduction in time-to-insight"
- "Add CSV export" → "Enable teams to share data outside the product — target: 25% increase in report sharing"
Step 4: Generate Transformed Roadmap
## Outcome-Focused Roadmap: [Product] — [Period]
**Strategic themes**: [2-3 high-level themes]
### Now (Current Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Status |
|---------|---------------|----------------|--------|
### Next (Next Quarter)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Confidence |
|---------|---------------|----------------|------------|
### Later (Future)
**Theme: [Strategic Theme]**
| Outcome | Success Metric | Key Initiatives | Dependencies |
|---------|---------------|----------------|-------------|
### Transformation Notes
| Original Feature | Transformed Outcome | Why This Framing |
|-----------------|--------------------|-----------------|
### What Changed
[Summary of how the roadmap narrative shifted]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 97 lines · 14 tokens per session scan A 2ab9171928c8
transform-roadmap is a command published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 767 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to transform-roadmap, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.