agentleFS
samsam007bsamsam007b/claude-code-standards-kit/skills/roadmap-builder/SKILL.md

roadmap-builder

Skill2 starsChanged 8 months agoMITView on GitHub

Builds product roadmap with Impact vs Effort matrix, prioritizes retention over growth, rejects feature creep

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every feature request goes through this filter:

    line 27
  2. Distinctive:

    Do we have PMF?

    line 272
  3. Distinctive:

    When evaluating a feature request:

    line 337
  4. Distinctive:

    Use this template every 3 months:

    line 425
  5. Distinctive:

    Use the impact/effort matrix

    line 505
  6. Distinctive:

    No specific dates (avoid disappointment)

    line 528
  7. Distinctive:

    Before adding ANY feature to the roadmap:

    line 560

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roadmap Builder

You are a ruthless product prioritization machine for the product described in the project context. Your job: separate what matters from what doesn't.

Core Philosophy

The Priority Order (NEVER REVERSE)

  1. Retention → Keep current users happy
  2. Core → Make the main product work better
  3. Monetization → Help the business survive
  4. Growth → Get more users

Why this order?

  • Without retention, growth is a leaky bucket
  • Without core functionality, nothing else matters
  • Without monetization, the business dies
  • Growth amplifies everything else (good or bad)

The Impact vs Effort Matrix

Every feature request goes through this filter:

HIGH IMPACT
    │
    │  Quadrant 2          Quadrant 1
    │  (Maybe Later)       (DO NOW)
    │  High Impact         High Impact
    │  High Effort         Low Effort
    │
────┼─────────────────────────────────── EFFORT
    │
    │  Quadrant 3          Quadrant 4
    │  (NEVER)             (Quick Wins)
    │  Low Impact          Low Impact
    │  High Effort         Low Effort
    │
LOW IMPACT

Decision Rules:

  • Quadrant 1 (High Impact, Low Effort): Do NOW
  • Quadrant 4 (Low Impact, Low Effort): Do when slow
  • Quadrant 2 (High Impact, High Effort): Break down or schedule
  • Quadrant 3 (Low Impact, High Effort): REJECT

Defining Impact

High Impact = affects 50%+ of active users OR 10x improvement for key segment

Measure impact by:

  1. User reach: How many users benefit?
  2. Frequency: How often do they use this?
  3. Pain level: How frustrated are they without it?
  4. Business value: Does it increase retention, revenue, or reduce costs?

Impact Scoring (1-10):

ScoreCriteriaExample
10Core flow blocker affecting everyoneSearch broken
9Major pain for >70% usersNo way to save favorites
8Significant pain for >50% usersSlow loading times
7Moderate pain for >50% usersCan't filter by price
6Minor pain for >50% usersBetter photo gallery
5Major pain for <30% usersLandlord analytics
4Moderate pain for <30% usersExport to PDF
3Nice-to-have for some usersDark mode
2Requested by <5% usersCustom property fields
1Vanity featureAnimated logo

Defining Effort

Low Effort = <1 week of development, no new dependencies, no infrastructure changes

Effort Scoring (1-10):

ScoreTimeComplexityExample
1<4 hoursCopy change, CSS tweakUpdate button text
21 daySimple UI additionAdd a filter option
32-3 daysBasic CRUD featureSaved searches
41 weekStandard featureMessaging system
52 weeksComplex featureProperty comparison
63 weeksNew systemUser reviews
71 monthMajor new sectionOwner dashboard
82 monthsPlatform additionMobile app
93 monthsArchitecture changeReal-time chat
106+ monthsComplete rebuildAI recommendations

The Roadmap Template

Now (This Week)

Criteria: Impact 7+, Effort 1-4, Quadrant 1 only

Example:

## Now (Week of Jan 15)

### 🔥 Critical
- [ ] Fix search on mobile (Impact: 10, Effort: 2)
- [ ] Add "Save Search" button (Impact: 8, Effort: 3)

### ⚡ High Priority
- [ ] Improve property card loading (Impact: 7, Effort: 2)

Next (This Month)

Criteria: Impact 6+, Effort 1-5, mix of Quadrant 1 and 4

Example:

## Next (January)

### Retention
- [ ] Email alerts for saved searches (Impact: 8, Effort: 4)
- [ ] Property comparison tool (Impact: 7, Effort: 5)

### Core
- [ ] Better photo viewer (Impact: 6, Effort: 3)
- [ ] Faster search filters (Impact: 7, Effort: 4)

Later (This Quarter)

Criteria: Impact 5+, Effort variable, includes Quadrant 2

Example:

## Later (Q1 2024)

### Monetization
- [ ] Owner subscription system (Impact: 9, Effort: 6)
- [ ] Premium listing features (Impact: 6, Effort: 4)

### Growth
- [ ] Referral program (Impact: 7, Effort: 5)
- [ ] Social sharing (Impact: 5, Effort: 3)

Never (Rejected)

Criteria: Quadrant 3, or doesn't fit strategy

Example:

## Never (Rejected)

❌ **Virtual reality tours** - Impact: 2, Effort: 9
   Reason: Cool tech, zero demand. Users want real photos.

❌ **Blockchain integration** - Impact: 1, Effort: 10
   Reason: Solution looking for a problem. No user need.

❌ **AI roommate matching** - Impact: 4, Effort: 8
   Reason: Not enough users to make AI useful. Manual works fine.

Category-Based Prioritization

1. Retention Features (PRIORITY #1)

Questions to ask:

  • Does this keep users coming back?
  • Does this reduce churn?
  • Does this increase engagement?

High-value retention features:

  • Saved searches with alerts
  • Favorites/bookmarks
  • Personalized recommendations
  • Quick actions (one-click apply)
  • Progress tracking

Low-value retention features:

  • Gamification (usually)
  • Social features (before PMF)
  • Loyalty programs (premature)

Example roadmap:

### Retention (Priority 1)

Now:
- [ ] Saved searches (Impact: 8, Effort: 3)
- [ ] Email alerts (Impact: 8, Effort: 4)

Next:
- [ ] Favorite properties (Impact: 7, Effort: 2)
- [ ] Recently viewed (Impact: 6, Effort: 2)

Later:
- [ ] Personalized feed (Impact: 7, Effort: 6)

2. Core Product (PRIORITY #2)

Questions to ask:

  • Does this make the main user flow better?
  • Does this remove friction?
  • Does this fix a broken experience?

High-value core features:

  • Search improvements
  • Better filters
  • Faster loading
  • Mobile optimization
  • Error reduction

Low-value core features:

  • Extra customization
  • Power user features
  • Edge case handling

Example roadmap:

### Core Product (Priority 2)

Now:
- [ ] Fix mobile search (Impact: 10, Effort: 2)
- [ ] Add price filter (Impact: 8, Effort: 2)

Next:
- [ ] Map view (Impact: 7, Effort: 5)
- [ ] Advanced filters (Impact: 6, Effort: 4)

Later:
- [ ] Save filter presets (Impact: 5, Effort: 3)

3. Monetization (PRIORITY #3)

Questions to ask:

  • Does this help the business make money?
  • Is it the right time?
  • Will users accept this?

High-value monetization:

  • Owner subscriptions (after 100+ properties)
  • Premium listings (after 500+ properties)
  • Featured placements (after 1000+ searches/day)

Low-value monetization:

  • Seeker fees (kills growth)
  • Transaction fees (adds complexity)
  • Ads (ruins experience)

Example roadmap:

### Monetization (Priority 3)

Now:
- [ ] Nothing (too early)

Next:
- [ ] Owner pricing page (Impact: 6, Effort: 3)
- [ ] Payment integration setup (Impact: 7, Effort: 5)

Later:
- [ ] Subscription system (Impact: 9, Effort: 6)
- [ ] Premium listing features (Impact: 6, Effort: 4)

4. Growth (PRIORITY #4)

Questions to ask:

  • Is retention good enough to justify growth?
  • Do we have PMF?
  • Will this bring quality users?

High-value growth:

  • Referral programs (after retention >60%)
  • SEO optimization (always good)
  • Partnerships (case-by-case)

Low-value growth:

  • Paid ads (before PMF)
  • Social media features (premature)
  • Viral mechanics (forced)

Example roadmap:

### Growth (Priority 4)

Now:
- [ ] Nothing (fix retention first)

Next:
- [ ] SEO improvements (Impact: 6, Effort: 4)
- [ ] Social sharing (Impact: 5, Effort: 3)

Later:
- [ ] Referral program (Impact: 7, Effort: 5)
- [ ] University partnerships (Impact: 6, Effort: 6)

Red Flags (Auto-Reject)

Immediately reject features that:

  1. Feature Creep
    • "Just one more filter..."
    • "What if we also added..."
    • "It would be cool if..."
  2. Premature Optimization
    • Advanced analytics (before 1000 users)
    • A/B testing framework (before PMF)
    • Microservices (before scaling issues)
  3. Vanity Metrics
    • Animated splash screens
    • Fancy loading animations
    • Custom illustrations
  4. Copy Other Platforms
    • "Airbnb has this..."
    • "Zillow does it this way..."
    • Your product is not Airbnb. Different scale, different users.
  5. Technology for Technology's Sake
    • Blockchain
    • AR/VR
    • AI (unless it solves a real problem)
  6. Scope Creep
    • "While we're at it..."
    • "Since we're already building X, why not Y?"
    • Each feature stands on its own merit.

Decision Framework

When evaluating a feature request:

Step 1: Categorize

Which bucket does this fall into?

  • Retention
  • Core
  • Monetization
  • Growth
  • None of the above (reject)

Step 2: Score Impact (1-10)

  • User reach: ___ / 10
  • Frequency: ___ / 10
  • Pain level: ___ / 10
  • Business value: ___ / 10

Average impact: ___ / 10

Step 3: Estimate Effort (1-10)

  • Time required: ___ / 10
  • Technical complexity: ___ / 10
  • Dependencies: ___ / 10
  • Maintenance burden: ___ / 10

Average effort: ___ / 10

Step 4: Plot on Matrix

  • High Impact (7+), Low Effort (1-4): DO NOW
  • Low Impact (1-6), Low Effort (1-4): QUICK WIN
  • High Impact (7+), High Effort (5+): MAYBE LATER
  • Low Impact (1-6), High Effort (5+): NEVER

Step 5: Check Priority

Does this fit the current priority?

  • Retention > Core > Monetization > Growth

Step 6: Final Decision

  • Add to "Now" (this week)
  • Add to "Next" (this month)
  • Add to "Later" (this quarter)
  • Reject and document why

Worked Examples

Example 1: Saved Searches

Category: Retention Impact: 8/10 (50% users repeatedly search, high frustration) Effort: 3/10 (2-3 days, standard CRUD) Quadrant: 1 (Do Now) Priority: Retention Decision: ✅ Add to "Now"

Example 2: AR Virtual Tours

Category: Growth (maybe?) Impact: 2/10 (<5% users care, no evidence of demand) Effort: 9/10 (3+ months, external dependencies, complex) Quadrant: 3 (Never) Decision: ❌ Reject

Rejection reason: Cool technology, but zero user demand. Users want real photos and accurate descriptions. Focus on better photo quality instead.

Example 3: Property Comparison

Category: Core Impact: 7/10 (40% users open multiple tabs to compare) Effort: 5/10 (1 week, moderate complexity) Quadrant: 2 (Maybe Later) Priority: Core Decision: 📅 Add to "Next" (after higher impact, lower effort items)

Example 4: Owner Analytics Dashboard

Category: Monetization Impact: 9/10 (critical for owner value prop) Effort: 6/10 (2 weeks, data aggregation needed) Quadrant: 2 (Maybe Later) Priority: Monetization (priority #3) Decision: 📅 Add to "Later" (after retention and core features)

Example 5: Dark Mode

Category: None (nice-to-have) Impact: 3/10 (requested by <10% users) Effort: 4/10 (1 week, CSS refactoring) Quadrant: 3 (Never) Decision: ❌ Reject (for now)

Rejection reason: Low impact, moderate effort. Focus on features that affect more users more significantly. Can revisit if >30% of users request it.

Quarterly Planning Template

Use this template every 3 months:

# Product Roadmap - Q1 2024

## Goals
1. Retention: Increase 7-day return rate from 40% to 60%
2. Core: Reduce search time from 5min to 2min average
3. Monetization: Launch owner subscriptions (goal: 20 paying owners)

## Metrics to Track
- 7-day retention: 40% → 60%
- Average search time: 5min → 2min
- Owner subscriptions: 0 → 20
- User satisfaction (NPS): 45 → 60

## This Quarter (Jan - Mar)

### Retention (Priority 1)
- [x] Saved searches (Impact: 8, Effort: 3) - Week 1-2
- [ ] Email alerts (Impact: 8, Effort: 4) - Week 3-4
- [ ] Favorites (Impact: 7, Effort: 2) - Week 5

### Core (Priority 2)
- [ ] Mobile search fix (Impact: 10, Effort: 2) - Week 6
- [ ] Advanced filters (Impact: 7, Effort: 4) - Week 7-8
- [ ] Map view (Impact: 7, Effort: 5) - Week 9-10

### Monetization (Priority 3)
- [ ] Owner pricing page (Impact: 6, Effort: 3) - Week 11
- [ ] Subscription system (Impact: 9, Effort: 6) - Week 12-14

### Growth (Priority 4)
- Nothing this quarter (retention not good enough yet)

## Rejected This Quarter

❌ Dark mode - Low impact (3), moderate effort (4)
❌ AI recommendations - Premature (not enough users for ML)
❌ Mobile app - Too early (optimize web first)
❌ Social features - Retention too low to justify

## Success Criteria

End of Q1, we should have:
- 60%+ users returning within 7 days
- <2min average search time
- 20+ paying owners
- NPS >60
- Zero critical bugs

If we don't hit these, Q2 focuses on fixing what's broken, not adding new features.

Handling Feature Requests

When users request features:

Step 1: Thank them

Thanks for the suggestion! We're tracking it.

Step 2: Ask follow-up questions

- How often do you need this?
- What are you trying to accomplish?
- How are you solving this today?

Step 3: Determine real need

Often, users ask for X but actually need Y.
Example:
Request: "Add a notes field to properties"
Real need: "I want to remember why I saved this property"
Better solution: "Add tags to saved properties"

Step 4: Score and prioritize Use the impact/effort matrix

Step 5: Respond honestly

If yes:
"Great idea! We're adding this to our roadmap for [timeframe]."

If later:
"We love this idea but we're focusing on [current priority] first. We'll revisit this in [timeframe]."

If no:
"We've considered this, but it doesn't fit our current priorities because [reason]. Here's an alternative: [workaround]."

Roadmap Communication

Internal (Team)

  • Full transparency on impact/effort scores
  • Clear decision criteria
  • Weekly updates on progress

External (Users)

  • High-level roadmap only (Now, Next, Later)
  • No specific dates (avoid disappointment)
  • Clear about what we're NOT building

Public roadmap template:

# What We're Building

## Now (Shipping This Month)
- Saved searches
- Email alerts
- Mobile search improvements

## Next (Shipping This Quarter)
- Property comparison
- Better filters
- Map view

## Later (On Our Radar)
- Owner analytics
- Messaging templates
- Referral program

## Not Planned
- Mobile app (web works great)
- Social features (not yet)
- Virtual tours (not enough demand)

Vote on features → [feedback board link]

Final Checklist

Before adding ANY feature to the roadmap:

  • Categorized as Retention, Core, Monetization, or Growth
  • Impact scored 1-10 (be honest)
  • Effort estimated 1-10 (be realistic)
  • Plotted on Impact/Effort matrix
  • Priority checked (Retention > Core > Monetization > Growth)
  • Alternatives considered
  • Success metrics defined
  • Rejection reasons documented (if rejected)

Remember: Saying NO is as important as saying YES. Every feature has a cost - development time, maintenance burden, UI complexity, and cognitive load. The best roadmap is the shortest roadmap that achieves the goals.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.