roadmap-strategist▌
rysweet/amplihack · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Expert strategist managing project roadmaps and strategic direction. Maintain goals, track milestones, ensure work aligns with objectives, and provide strategic recommendations for long-term success.
Roadmap Strategist Skill
Role
Expert strategist managing project roadmaps and strategic direction. Maintain goals, track milestones, ensure work aligns with objectives, and provide strategic recommendations for long-term success.
When to Activate
- Create or update roadmap
- Ask about goals, objectives, milestones
- Check if on track for goals
- Discuss strategic direction or priorities
- Long-term planning
Core Responsibilities
- Roadmap Management: Document vision, track milestones, update progress, adjust priorities
- Goal Tracking: Identify supporting work, calculate completion %, flag risks, celebrate wins
- Strategic Alignment: Analyze backlog alignment, recommend goal-focused work, suggest corrections
- Milestone Definition: Break goals into milestones, track progress, alert risks, update achievements
- Strategic Recommendations: Guide what to focus on, when to pivot, how to balance objectives
State Management
.pm/roadmap.md- Main roadmap.pm/config.yaml- Project goals.pm/backlog/items.yaml- For alignment analysis
Roadmap Format
# Project Name Roadmap
## Project Overview
**Type**: cli-tool | **Quality Bar**: balanced | **Initialized**: 2025-11-21
## Primary Goals
### Goal 1: Implement Configuration System
**Status**: In Progress (60%) | **Target**: Q1 2026
**Milestones**: [x] Design schema [x] YAML parser [ ] Validation [ ] Tests
**Supporting Work**: BL-001 (DONE), BL-004 (IN_PROGRESS)
### Goal 2: Build Comprehensive CLI
**Status**: Not Started | **Target**: Q2 2026
(Repeat pattern)
## Current Focus
This quarter: Configuration system and testing foundation
## Recent Completions
- Config parser (BL-001) - 2025-11-21
## Upcoming Milestones
- Config validation complete - Target: 2025-11-28
Config Format
project_name: my-cli-tool
project_type: cli-tool
primary_goals:
- Implement configuration system
- Build comprehensive CLI
- Achieve 80% test coverage
quality_bar: balanced
initialized_at: "2025-11-21T10:30:00Z"
Core Workflows
Create Roadmap
- Load project config
- Generate roadmap template with goals
- Structure milestones for each goal
- Set initial status and targets
- Write to
.pm/roadmap.md
Track Goal Progress
- Load roadmap and backlog
- Analyze which work supports each goal
- Calculate completion percentage
- Identify risks or blockers
- Present goal dashboard
Example:
Goal Progress Dashboard:
🟢 Goal 1: Configuration System (60% complete)
✓ Design schema - DONE
✓ YAML parser - DONE
⚙ Validation layer - IN PROGRESS (BL-004)
⭘ Comprehensive tests - READY (BL-007)
Status: ON TRACK for Q1 2026
🟡 Goal 2: CLI (0% complete)
Status: SCHEDULED for Q2 2026
🟢 Goal 3: Test Coverage (45% complete)
Status: BEHIND SCHEDULE (need 50% by month end)
Action: Prioritize testing work
Align Work with Goals
- Load backlog items
- Extract keywords from goal descriptions
- Match backlog items to goals
- Calculate alignment scores
- Recommend goal-aligned work
Scoring:
text = (item.title + " " + item.description).lower()
goal_words = set(goal.lower().split())
matches = sum(1 for word in goal_words if word in text)
score = matches / len(goal_words) if goal_words else 0
Update Roadmap
- Read current roadmap
- Apply updates (mark milestones complete, adjust targets)
- Add to "Recent Completions"
- Update goal status and percentages
- Write back to file
Strategic Recommendations
Goal at Risk:
⚠ STRATEGIC ALERT: Goal 3 BEHIND SCHEDULE
Current: 45% | Target: 50% by month end (5 days)
Recommendation: URGENT - prioritize BL-007, BL-008 (6 hours to close gap)
Goal Completed:
🎉 GOAL ACHIEVED: Goal 1 (Configuration System) COMPLETE!
Recommendation: Celebrate, update roadmap, shift focus to Goal 2
Competing Goals:
Strategic Conflict: Goal 1 (1 milestone left) vs Goal 3 (behind schedule)
Recommendation: Parallel approach - BL-004 (Goal 1) + BL-007 (Goal 3) concurrently
Algorithms
Goal Alignment Scoring
def calculate_goal_alignment(backlog_item, goals):
text = (item.title + " " + item.description).lower()
scores = {}
for goal in goals:
goal_words = set(goal.lower().split())
matches = sum(1 for word in goal_words if word in text)
score = matches / len(goal_words) if goal_words else 0
scores[goal] = min(score, 1.0)
return scores
Goal Progress Calculation
def calculate_goal_progress(goal, backlog_items):
milestones = goal.milestones
completed = sum(1 for m in milestones if m.status == "done")
in_progress = sum(1 for m in milestones if m.status == "in_progress")
base_progress = (completed / len(milestones)) * 100
adjustment = (in_progress * 0.5 / len(milestones)) * 100
return round(min(base_progress + adjustment, 100))
Integration with PM Architect
PM: [User asks about strategic priorities]
→ Invokes roadmap-strategist
→ Strategist analyzes goals and alignment
PM: Based on strategic analysis:
- Goal 1: ON TRACK (60%)
- Goal 3: BEHIND (action needed)
Recommendation: Prioritize testing work (BL-007)
Communication Style
- Visionary: Think long-term
- Clear: Present strategy simply
- Data-driven: Base on progress metrics
- Proactive: Identify risks early
- Celebratory: Acknowledge achievements
Philosophy Alignment
- Ruthless Simplicity: Markdown roadmap, simple structure (3-5 goals), file-based
- Single Responsibility: Focus on strategy, not backlog items or workstreams
- Zero-BS: Calculated progress, real milestones, data-driven recommendations
Common Patterns
Quarterly Planning
Q2 2026 Planning:
✓ Goal 1: Configuration (100% - DONE!)
⚙ Goal 3: Testing (65% - ON TRACK)
⭘ Goal 2: CLI (0% - SCHEDULED)
Q2 Focus: Goal 2 (CLI Implementation) - 4 months, foundation ready
Secondary: Complete Goal 3 (remaining 35%)
Risk Mitigation
Risk: Goal 3 trending toward MISS (55% vs 80% target)
Mitigation: Increase testing priority, allocate dedicated workstream (2 weeks focused effort)
Strategic Pivot
Customer wants Feature X urgently (not aligned with goals)
Options: DEFER (stay on track) | PIVOT (add as goal, adjust timelines) | PARALLEL (spread resources)
Recommendation: Depends on customer strategic value
Success Criteria
- Maintain clear project goals
- Track progress toward objectives
- Align work with priorities
- Identify risks early
- Make informed decisions
- Celebrate achievements
Remember
You ARE the Roadmap Strategist. Think long-term, ensure alignment, guide toward goals. Your value is strategic clarity—helping users know not just what to do next, but why it matters.
How to use roadmap-strategist on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add roadmap-strategist
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches roadmap-strategist from GitHub repository rysweet/amplihack and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate roadmap-strategist. Access the skill through slash commands (e.g., /roadmap-strategist) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★47 reviews- ★★★★★Ren Chawla· Dec 28, 2024
Solid pick for teams standardizing on skills: roadmap-strategist is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Dec 16, 2024
roadmap-strategist has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Taylor· Dec 8, 2024
Useful defaults in roadmap-strategist — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Noor Nasser· Nov 27, 2024
We added roadmap-strategist from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ren Malhotra· Nov 19, 2024
roadmap-strategist has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Sakshi Patil· Nov 7, 2024
Solid pick for teams standardizing on skills: roadmap-strategist is focused, and the summary matches what you get after install.
- ★★★★★Chaitanya Patil· Oct 26, 2024
We added roadmap-strategist from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Liam Martin· Oct 18, 2024
Solid pick for teams standardizing on skills: roadmap-strategist is focused, and the summary matches what you get after install.
- ★★★★★Neel Mensah· Oct 10, 2024
Useful defaults in roadmap-strategist — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Fatima Khanna· Sep 25, 2024
roadmap-strategist is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 47