[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-anthropic-roadmap-update":3,"mdc-c5pbwa-key":31,"related-repo-anthropic-roadmap-update":1364,"related-org-anthropic-roadmap-update":1483},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":26,"sourceUrl":29,"mdContent":30},"roadmap-update","update and reprioritize product roadmaps","Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now\u002FNext\u002FLater view from scratch.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"anthropic","Anthropic","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fanthropic.png","anthropics",[13,17],{"name":14,"slug":15,"type":16},"Roadmap","roadmap","tag",{"name":18,"slug":19,"type":16},"Product Management","product-management",22885,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","2026-04-06T17:59:10.241373",null,2736,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":28},[],"Open source repository of plugins primarily intended for knowledge workers to use in Claude Cowork","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\u002Ftree\u002FHEAD\u002Fproduct-management\u002Fskills\u002Froadmap-update","---\nname: roadmap-update\ndescription: Update, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now\u002FNext\u002FLater view from scratch.\nargument-hint: \"\u003Cupdate description>\"\n---\n\n# Roadmap Update\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nUpdate, create, or reprioritize a product roadmap.\n\n## Usage\n\n```\n\u002Froadmap-update $ARGUMENTS\n```\n\n## Workflow\n\n### 1. Understand Current State\n\nIf **~~project tracker** is connected:\n- Pull current roadmap items with their statuses, assignees, and dates\n- Identify items that are overdue, at risk, or recently completed\n- Surface any items without clear owners or dates\n\nIf no project management tool is connected:\n- Ask the user to describe their current roadmap or paste\u002Fupload it\n- Accept any format: list, table, spreadsheet, screenshot, or prose description\n\n### 2. Determine the Operation\n\nAsk what the user wants to do:\n\n**Add item**: New feature, initiative, or work item to the roadmap\n- Gather: name, description, priority, estimated effort, target timeframe, owner, dependencies\n- Suggest where it fits based on current priorities and capacity\n\n**Update status**: Change status of existing items\n- Options: not started, in progress, at risk, blocked, completed, cut\n- For \"at risk\" or \"blocked\": ask for the blocker and mitigation plan\n\n**Reprioritize**: Change the order or priority of items\n- Ask what changed (new information, strategy shift, resource change, customer feedback)\n- Apply a prioritization framework if helpful — see **Prioritization Frameworks** below for RICE, MoSCoW, ICE, and value-vs-effort\n- Show before\u002Fafter comparison\n\n**Move timeline**: Shift dates for items\n- Ask why (scope change, dependency slip, resource constraint)\n- Identify downstream impacts on dependent items\n- Flag items that move past hard deadlines\n\n**Create new roadmap**: Build a roadmap from scratch\n- Ask about timeframe (quarter, half, year)\n- Ask about format preference (Now\u002FNext\u002FLater, quarterly columns, OKR-aligned) — see **Roadmap Frameworks** below\n- Gather the list of initiatives to include\n\n### 3. Generate Roadmap Summary\n\nProduce a roadmap view with:\n\n#### Status Overview\nQuick summary: X items in progress, Y completed this period, Z at risk.\n\n#### Roadmap Items\nFor each item, show:\n- Name and one-line description\n- Status indicator (on track \u002F at risk \u002F blocked \u002F completed \u002F not started)\n- Target timeframe or date\n- Owner\n- Key dependencies\n\nGroup items by:\n- Timeframe (Now \u002F Next \u002F Later) or quarter, depending on format\n- Or by theme\u002Fgoal if the user prefers\n\n#### Risks and Dependencies\n- Items that are blocked or at risk, with details\n- Cross-team dependencies and their status\n- Items approaching hard deadlines\n\n#### Changes This Update\nIf this is an update to an existing roadmap, summarize what changed:\n- Items added, removed, or reprioritized\n- Timeline shifts\n- Status changes\n\n### 4. Follow Up\n\nAfter generating the roadmap:\n- Offer to format for a specific audience (executive summary, engineering detail, customer-facing)\n- Offer to draft communication about roadmap changes\n- If project management tool is connected, offer to update ticket statuses\n\n## Roadmap Frameworks\n\n### Now \u002F Next \u002F Later\nThe simplest and often most effective roadmap format:\n\n- **Now** (current sprint\u002Fmonth): Committed work. High confidence in scope and timeline. These are the things the team is actively building.\n- **Next** (next 1-3 months): Planned work. Good confidence in what, less confidence in exactly when. Scoped and prioritized but not yet started.\n- **Later** (3-6+ months): Directional. These are strategic bets and opportunities we intend to pursue, but scope and timing are flexible.\n\nWhen to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.\n\n### Quarterly Themes\nOrganize the roadmap around 2-3 themes per quarter:\n\n- Each theme represents a strategic area of investment (e.g., \"Enterprise readiness\", \"Activation improvements\", \"Platform extensibility\")\n- Under each theme, list the specific initiatives planned\n- Themes should map to company or team OKRs\n- This format makes it easy to explain WHY you are building what you are building\n\nWhen to use: When you need to show strategic alignment. Good for planning meetings and executive communication.\n\n### OKR-Aligned Roadmap\nMap roadmap items directly to Objectives and Key Results:\n\n- Start with the team's OKRs for the period\n- Under each Key Result, list the initiatives that will move that metric\n- Include the expected impact of each initiative on the Key Result\n- This creates clear accountability between what you build and what you measure\n\nWhen to use: Organizations that run on OKRs. Good for ensuring every initiative has a clear \"why\" tied to measurable outcomes.\n\n### Timeline \u002F Gantt View\nCalendar-based view with items on a timeline:\n\n- Shows start dates, end dates, and durations\n- Visualizes parallelism and sequencing\n- Good for identifying resource conflicts\n- Shows dependencies between items\n\nWhen to use: Execution planning with engineering. Identifying scheduling conflicts. NOT good for communicating externally (creates false precision expectations).\n\n## Prioritization Frameworks\n\n### RICE Score\nScore each initiative on four dimensions, then calculate RICE = (Reach x Impact x Confidence) \u002F Effort\n\n- **Reach**: How many users\u002Fcustomers will this affect in a given time period? Use concrete numbers (e.g., \"500 users per quarter\").\n- **Impact**: How much will this move the needle for each person reached? Score on a scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal.\n- **Confidence**: How confident are we in the reach and impact estimates? 100% = high confidence (backed by data), 80% = medium (some evidence), 50% = low (gut feel).\n- **Effort**: How many person-months of work? Include engineering, design, and any other functions.\n\nWhen to use: When you need a quantitative, defensible prioritization. Good for comparing a large backlog of initiatives. Less good for strategic bets where impact is hard to estimate.\n\n### MoSCoW\nCategorize items into Must have, Should have, Could have, Won't have:\n\n- **Must have**: The roadmap is a failure without these. Non-negotiable commitments.\n- **Should have**: Important and expected, but delivery is viable without them.\n- **Could have**: Desirable but clearly lower priority. Include only if capacity allows.\n- **Won't have**: Explicitly out of scope for this period. Important to list for clarity.\n\nWhen to use: Scoping a release or quarter. Negotiating with stakeholders about what fits. Good for forcing prioritization conversations.\n\n### ICE Score\nSimpler than RICE. Score each item 1-10 on three dimensions:\n\n- **Impact**: How much will this move the target metric?\n- **Confidence**: How confident are we in the impact estimate?\n- **Ease**: How easy is this to implement? (Inverse of effort — higher = easier)\n\nICE Score = Impact x Confidence x Ease\n\nWhen to use: Quick prioritization of a feature backlog. Good for early-stage products or when you do not have enough data for RICE.\n\n### Value vs Effort Matrix\nPlot initiatives on a 2x2 matrix:\n\n- **High value, Low effort** (Quick wins): Do these first.\n- **High value, High effort** (Big bets): Plan these carefully. Worth the investment but need proper scoping.\n- **Low value, Low effort** (Fill-ins): Do these when you have spare capacity.\n- **Low value, High effort** (Money pits): Do not do these. Remove from the backlog.\n\nWhen to use: Visual prioritization in team planning sessions. Good for building shared understanding of tradeoffs.\n\n## Dependency Mapping\n\n### Identifying Dependencies\nLook for dependencies across these categories:\n\n- **Technical dependencies**: Feature B requires infrastructure work from Feature A\n- **Team dependencies**: Feature requires work from another team (design, platform, data)\n- **External dependencies**: Waiting on a vendor, partner, or third-party integration\n- **Knowledge dependencies**: Need research or investigation results before starting\n- **Sequential dependencies**: Must ship Feature A before starting Feature B (shared code, user flow)\n\n### Managing Dependencies\n- List all dependencies explicitly in the roadmap\n- Assign an owner to each dependency (who is responsible for resolving it)\n- Set a \"need by\" date: when does the depending item need this resolved\n- Build buffer around dependencies — they are the highest-risk items on any roadmap\n- Flag dependencies that cross team boundaries early — these require coordination\n- Have a contingency plan: what do you do if the dependency slips?\n\n### Reducing Dependencies\n- Can you build a simpler version that avoids the dependency?\n- Can you parallelize by using an interface contract or mock?\n- Can you sequence differently to move the dependency earlier?\n- Can you absorb the work into your team to remove the cross-team coordination?\n\n## Capacity Planning\n\n### Estimating Capacity\n- Start with the number of engineers and the time period\n- Subtract known overhead: meetings, on-call rotations, interviews, holidays, PTO\n- A common rule of thumb: engineers spend 60-70% of time on planned feature work\n- Factor in team ramp time for new members\n\n### Allocating Capacity\nA healthy allocation for most product teams:\n\n- **70% planned features**: Roadmap items that advance strategic goals\n- **20% technical health**: Tech debt, reliability, performance, developer experience\n- **10% unplanned**: Buffer for urgent issues, quick wins, and requests from other teams\n\nAdjust ratios based on team context:\n- New product: more feature work, less tech debt\n- Mature product: more tech debt and reliability investment\n- Post-incident: more reliability, less features\n- Rapid growth: more scalability and performance\n\n### Capacity vs Ambition\n- If roadmap commitments exceed capacity, something must give\n- Do not solve capacity problems by pretending people can do more — solve by cutting scope\n- When adding to the roadmap, always ask: \"What comes off?\"\n- Better to commit to fewer things and deliver reliably than to overcommit and disappoint\n\n## Communicating Roadmap Changes\n\n### When the Roadmap Changes\nCommon triggers for roadmap changes:\n- New strategic priority from leadership\n- Customer feedback or research that changes priorities\n- Technical discovery that changes estimates\n- Dependency slip from another team\n- Resource change (team grows or shrinks, key person leaves)\n- Competitive move that requires response\n\n### How to Communicate Changes\n1. **Acknowledge the change**: Be direct about what is changing and why\n2. **Explain the reason**: What new information drove this decision?\n3. **Show the tradeoff**: What was deprioritized to make room? Or what is slipping?\n4. **Show the new plan**: Updated roadmap with the changes reflected\n5. **Acknowledge impact**: Who is affected and how? Stakeholders who were expecting deprioritized items need to hear it directly.\n\n### Avoiding Roadmap Whiplash\n- Do not change the roadmap for every piece of new information. Have a threshold for change.\n- Batch roadmap updates at natural cadences (monthly, quarterly) unless something is truly urgent.\n- Distinguish between \"roadmap change\" (strategic reprioritization) and \"scope adjustment\" (normal execution refinement).\n- Track how often the roadmap changes. Frequent changes may signal unclear strategy, not good responsiveness.\n\n## Output Format\n\nUse a clear, scannable format. Tables work well for roadmap items. Use text status labels: **Done**, **On Track**, **At Risk**, **Blocked**, **Not Started**.\n\n## Tips\n\n- A roadmap is a communication tool, not a project plan. Keep it at the right altitude — themes and outcomes, not tasks.\n- When reprioritizing, always ask what changed. Priority shifts should be driven by new information, not whim.\n- Flag capacity issues early. If the roadmap has more work than the team can handle, say so.\n- Dependencies are the biggest risk to roadmaps. Surface them explicitly.\n- If the user asks to add something, always ask what comes off or moves. Roadmaps are zero-sum against capacity.\n",{"data":32,"body":34},{"name":4,"description":6,"argument-hint":33},"\u003Cupdate description>",{"type":35,"children":36},"root",[37,45,64,69,76,89,95,102,115,135,140,153,159,164,174,187,197,210,220,245,255,273,283,308,314,319,326,331,337,342,370,375,388,394,412,418,423,441,447,452,470,475,481,486,519,524,530,535,558,563,569,574,597,602,608,613,636,641,646,652,657,700,705,711,716,759,764,770,775,806,811,816,822,827,870,875,881,887,892,945,951,984,990,1013,1019,1025,1048,1054,1059,1092,1097,1120,1126,1149,1155,1161,1166,1199,1205,1259,1265,1288,1294,1330,1336],{"type":38,"tag":39,"props":40,"children":41},"element","h1",{"id":4},[42],{"type":43,"value":44},"text","Roadmap Update",{"type":38,"tag":46,"props":47,"children":48},"blockquote",{},[49],{"type":38,"tag":50,"props":51,"children":52},"p",{},[53,55,62],{"type":43,"value":54},"If you see unfamiliar placeholders or need to check which tools are connected, see ",{"type":38,"tag":56,"props":57,"children":59},"a",{"href":58},"..\u002F..\u002FCONNECTORS.md",[60],{"type":43,"value":61},"CONNECTORS.md",{"type":43,"value":63},".",{"type":38,"tag":50,"props":65,"children":66},{},[67],{"type":43,"value":68},"Update, create, or reprioritize a product roadmap.",{"type":38,"tag":70,"props":71,"children":73},"h2",{"id":72},"usage",[74],{"type":43,"value":75},"Usage",{"type":38,"tag":77,"props":78,"children":82},"pre",{"className":79,"code":81,"language":43},[80],"language-text","\u002Froadmap-update $ARGUMENTS\n",[83],{"type":38,"tag":84,"props":85,"children":87},"code",{"__ignoreMap":86},"",[88],{"type":43,"value":81},{"type":38,"tag":70,"props":90,"children":92},{"id":91},"workflow",[93],{"type":43,"value":94},"Workflow",{"type":38,"tag":96,"props":97,"children":99},"h3",{"id":98},"_1-understand-current-state",[100],{"type":43,"value":101},"1. Understand Current State",{"type":38,"tag":50,"props":103,"children":104},{},[105,107,113],{"type":43,"value":106},"If ",{"type":38,"tag":108,"props":109,"children":110},"strong",{},[111],{"type":43,"value":112},"~~project tracker",{"type":43,"value":114}," is connected:",{"type":38,"tag":116,"props":117,"children":118},"ul",{},[119,125,130],{"type":38,"tag":120,"props":121,"children":122},"li",{},[123],{"type":43,"value":124},"Pull current roadmap items with their statuses, assignees, and dates",{"type":38,"tag":120,"props":126,"children":127},{},[128],{"type":43,"value":129},"Identify items that are overdue, at risk, or recently completed",{"type":38,"tag":120,"props":131,"children":132},{},[133],{"type":43,"value":134},"Surface any items without clear owners or dates",{"type":38,"tag":50,"props":136,"children":137},{},[138],{"type":43,"value":139},"If no project management tool is connected:",{"type":38,"tag":116,"props":141,"children":142},{},[143,148],{"type":38,"tag":120,"props":144,"children":145},{},[146],{"type":43,"value":147},"Ask the user to describe their current roadmap or paste\u002Fupload it",{"type":38,"tag":120,"props":149,"children":150},{},[151],{"type":43,"value":152},"Accept any format: list, table, spreadsheet, screenshot, or prose description",{"type":38,"tag":96,"props":154,"children":156},{"id":155},"_2-determine-the-operation",[157],{"type":43,"value":158},"2. Determine the Operation",{"type":38,"tag":50,"props":160,"children":161},{},[162],{"type":43,"value":163},"Ask what the user wants to do:",{"type":38,"tag":50,"props":165,"children":166},{},[167,172],{"type":38,"tag":108,"props":168,"children":169},{},[170],{"type":43,"value":171},"Add item",{"type":43,"value":173},": New feature, initiative, or work item to the roadmap",{"type":38,"tag":116,"props":175,"children":176},{},[177,182],{"type":38,"tag":120,"props":178,"children":179},{},[180],{"type":43,"value":181},"Gather: name, description, priority, estimated effort, target timeframe, owner, dependencies",{"type":38,"tag":120,"props":183,"children":184},{},[185],{"type":43,"value":186},"Suggest where it fits based on current priorities and capacity",{"type":38,"tag":50,"props":188,"children":189},{},[190,195],{"type":38,"tag":108,"props":191,"children":192},{},[193],{"type":43,"value":194},"Update status",{"type":43,"value":196},": Change status of existing items",{"type":38,"tag":116,"props":198,"children":199},{},[200,205],{"type":38,"tag":120,"props":201,"children":202},{},[203],{"type":43,"value":204},"Options: not started, in progress, at risk, blocked, completed, cut",{"type":38,"tag":120,"props":206,"children":207},{},[208],{"type":43,"value":209},"For \"at risk\" or \"blocked\": ask for the blocker and mitigation plan",{"type":38,"tag":50,"props":211,"children":212},{},[213,218],{"type":38,"tag":108,"props":214,"children":215},{},[216],{"type":43,"value":217},"Reprioritize",{"type":43,"value":219},": Change the order or priority of items",{"type":38,"tag":116,"props":221,"children":222},{},[223,228,240],{"type":38,"tag":120,"props":224,"children":225},{},[226],{"type":43,"value":227},"Ask what changed (new information, strategy shift, resource change, customer feedback)",{"type":38,"tag":120,"props":229,"children":230},{},[231,233,238],{"type":43,"value":232},"Apply a prioritization framework if helpful — see ",{"type":38,"tag":108,"props":234,"children":235},{},[236],{"type":43,"value":237},"Prioritization Frameworks",{"type":43,"value":239}," below for RICE, MoSCoW, ICE, and value-vs-effort",{"type":38,"tag":120,"props":241,"children":242},{},[243],{"type":43,"value":244},"Show before\u002Fafter comparison",{"type":38,"tag":50,"props":246,"children":247},{},[248,253],{"type":38,"tag":108,"props":249,"children":250},{},[251],{"type":43,"value":252},"Move timeline",{"type":43,"value":254},": Shift dates for items",{"type":38,"tag":116,"props":256,"children":257},{},[258,263,268],{"type":38,"tag":120,"props":259,"children":260},{},[261],{"type":43,"value":262},"Ask why (scope change, dependency slip, resource constraint)",{"type":38,"tag":120,"props":264,"children":265},{},[266],{"type":43,"value":267},"Identify downstream impacts on dependent items",{"type":38,"tag":120,"props":269,"children":270},{},[271],{"type":43,"value":272},"Flag items that move past hard deadlines",{"type":38,"tag":50,"props":274,"children":275},{},[276,281],{"type":38,"tag":108,"props":277,"children":278},{},[279],{"type":43,"value":280},"Create new roadmap",{"type":43,"value":282},": Build a roadmap from scratch",{"type":38,"tag":116,"props":284,"children":285},{},[286,291,303],{"type":38,"tag":120,"props":287,"children":288},{},[289],{"type":43,"value":290},"Ask about timeframe (quarter, half, year)",{"type":38,"tag":120,"props":292,"children":293},{},[294,296,301],{"type":43,"value":295},"Ask about format preference (Now\u002FNext\u002FLater, quarterly columns, OKR-aligned) — see ",{"type":38,"tag":108,"props":297,"children":298},{},[299],{"type":43,"value":300},"Roadmap Frameworks",{"type":43,"value":302}," below",{"type":38,"tag":120,"props":304,"children":305},{},[306],{"type":43,"value":307},"Gather the list of initiatives to include",{"type":38,"tag":96,"props":309,"children":311},{"id":310},"_3-generate-roadmap-summary",[312],{"type":43,"value":313},"3. Generate Roadmap Summary",{"type":38,"tag":50,"props":315,"children":316},{},[317],{"type":43,"value":318},"Produce a roadmap view with:",{"type":38,"tag":320,"props":321,"children":323},"h4",{"id":322},"status-overview",[324],{"type":43,"value":325},"Status Overview",{"type":38,"tag":50,"props":327,"children":328},{},[329],{"type":43,"value":330},"Quick summary: X items in progress, Y completed this period, Z at risk.",{"type":38,"tag":320,"props":332,"children":334},{"id":333},"roadmap-items",[335],{"type":43,"value":336},"Roadmap Items",{"type":38,"tag":50,"props":338,"children":339},{},[340],{"type":43,"value":341},"For each item, show:",{"type":38,"tag":116,"props":343,"children":344},{},[345,350,355,360,365],{"type":38,"tag":120,"props":346,"children":347},{},[348],{"type":43,"value":349},"Name and one-line description",{"type":38,"tag":120,"props":351,"children":352},{},[353],{"type":43,"value":354},"Status indicator (on track \u002F at risk \u002F blocked \u002F completed \u002F not started)",{"type":38,"tag":120,"props":356,"children":357},{},[358],{"type":43,"value":359},"Target timeframe or date",{"type":38,"tag":120,"props":361,"children":362},{},[363],{"type":43,"value":364},"Owner",{"type":38,"tag":120,"props":366,"children":367},{},[368],{"type":43,"value":369},"Key dependencies",{"type":38,"tag":50,"props":371,"children":372},{},[373],{"type":43,"value":374},"Group items by:",{"type":38,"tag":116,"props":376,"children":377},{},[378,383],{"type":38,"tag":120,"props":379,"children":380},{},[381],{"type":43,"value":382},"Timeframe (Now \u002F Next \u002F Later) or quarter, depending on format",{"type":38,"tag":120,"props":384,"children":385},{},[386],{"type":43,"value":387},"Or by theme\u002Fgoal if the user prefers",{"type":38,"tag":320,"props":389,"children":391},{"id":390},"risks-and-dependencies",[392],{"type":43,"value":393},"Risks and Dependencies",{"type":38,"tag":116,"props":395,"children":396},{},[397,402,407],{"type":38,"tag":120,"props":398,"children":399},{},[400],{"type":43,"value":401},"Items that are blocked or at risk, with details",{"type":38,"tag":120,"props":403,"children":404},{},[405],{"type":43,"value":406},"Cross-team dependencies and their status",{"type":38,"tag":120,"props":408,"children":409},{},[410],{"type":43,"value":411},"Items approaching hard deadlines",{"type":38,"tag":320,"props":413,"children":415},{"id":414},"changes-this-update",[416],{"type":43,"value":417},"Changes This Update",{"type":38,"tag":50,"props":419,"children":420},{},[421],{"type":43,"value":422},"If this is an update to an existing roadmap, summarize what changed:",{"type":38,"tag":116,"props":424,"children":425},{},[426,431,436],{"type":38,"tag":120,"props":427,"children":428},{},[429],{"type":43,"value":430},"Items added, removed, or reprioritized",{"type":38,"tag":120,"props":432,"children":433},{},[434],{"type":43,"value":435},"Timeline shifts",{"type":38,"tag":120,"props":437,"children":438},{},[439],{"type":43,"value":440},"Status changes",{"type":38,"tag":96,"props":442,"children":444},{"id":443},"_4-follow-up",[445],{"type":43,"value":446},"4. Follow Up",{"type":38,"tag":50,"props":448,"children":449},{},[450],{"type":43,"value":451},"After generating the roadmap:",{"type":38,"tag":116,"props":453,"children":454},{},[455,460,465],{"type":38,"tag":120,"props":456,"children":457},{},[458],{"type":43,"value":459},"Offer to format for a specific audience (executive summary, engineering detail, customer-facing)",{"type":38,"tag":120,"props":461,"children":462},{},[463],{"type":43,"value":464},"Offer to draft communication about roadmap changes",{"type":38,"tag":120,"props":466,"children":467},{},[468],{"type":43,"value":469},"If project management tool is connected, offer to update ticket statuses",{"type":38,"tag":70,"props":471,"children":473},{"id":472},"roadmap-frameworks",[474],{"type":43,"value":300},{"type":38,"tag":96,"props":476,"children":478},{"id":477},"now-next-later",[479],{"type":43,"value":480},"Now \u002F Next \u002F Later",{"type":38,"tag":50,"props":482,"children":483},{},[484],{"type":43,"value":485},"The simplest and often most effective roadmap format:",{"type":38,"tag":116,"props":487,"children":488},{},[489,499,509],{"type":38,"tag":120,"props":490,"children":491},{},[492,497],{"type":38,"tag":108,"props":493,"children":494},{},[495],{"type":43,"value":496},"Now",{"type":43,"value":498}," (current sprint\u002Fmonth): Committed work. High confidence in scope and timeline. These are the things the team is actively building.",{"type":38,"tag":120,"props":500,"children":501},{},[502,507],{"type":38,"tag":108,"props":503,"children":504},{},[505],{"type":43,"value":506},"Next",{"type":43,"value":508}," (next 1-3 months): Planned work. Good confidence in what, less confidence in exactly when. Scoped and prioritized but not yet started.",{"type":38,"tag":120,"props":510,"children":511},{},[512,517],{"type":38,"tag":108,"props":513,"children":514},{},[515],{"type":43,"value":516},"Later",{"type":43,"value":518}," (3-6+ months): Directional. These are strategic bets and opportunities we intend to pursue, but scope and timing are flexible.",{"type":38,"tag":50,"props":520,"children":521},{},[522],{"type":43,"value":523},"When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.",{"type":38,"tag":96,"props":525,"children":527},{"id":526},"quarterly-themes",[528],{"type":43,"value":529},"Quarterly Themes",{"type":38,"tag":50,"props":531,"children":532},{},[533],{"type":43,"value":534},"Organize the roadmap around 2-3 themes per quarter:",{"type":38,"tag":116,"props":536,"children":537},{},[538,543,548,553],{"type":38,"tag":120,"props":539,"children":540},{},[541],{"type":43,"value":542},"Each theme represents a strategic area of investment (e.g., \"Enterprise readiness\", \"Activation improvements\", \"Platform extensibility\")",{"type":38,"tag":120,"props":544,"children":545},{},[546],{"type":43,"value":547},"Under each theme, list the specific initiatives planned",{"type":38,"tag":120,"props":549,"children":550},{},[551],{"type":43,"value":552},"Themes should map to company or team OKRs",{"type":38,"tag":120,"props":554,"children":555},{},[556],{"type":43,"value":557},"This format makes it easy to explain WHY you are building what you are building",{"type":38,"tag":50,"props":559,"children":560},{},[561],{"type":43,"value":562},"When to use: When you need to show strategic alignment. Good for planning meetings and executive communication.",{"type":38,"tag":96,"props":564,"children":566},{"id":565},"okr-aligned-roadmap",[567],{"type":43,"value":568},"OKR-Aligned Roadmap",{"type":38,"tag":50,"props":570,"children":571},{},[572],{"type":43,"value":573},"Map roadmap items directly to Objectives and Key Results:",{"type":38,"tag":116,"props":575,"children":576},{},[577,582,587,592],{"type":38,"tag":120,"props":578,"children":579},{},[580],{"type":43,"value":581},"Start with the team's OKRs for the period",{"type":38,"tag":120,"props":583,"children":584},{},[585],{"type":43,"value":586},"Under each Key Result, list the initiatives that will move that metric",{"type":38,"tag":120,"props":588,"children":589},{},[590],{"type":43,"value":591},"Include the expected impact of each initiative on the Key Result",{"type":38,"tag":120,"props":593,"children":594},{},[595],{"type":43,"value":596},"This creates clear accountability between what you build and what you measure",{"type":38,"tag":50,"props":598,"children":599},{},[600],{"type":43,"value":601},"When to use: Organizations that run on OKRs. Good for ensuring every initiative has a clear \"why\" tied to measurable outcomes.",{"type":38,"tag":96,"props":603,"children":605},{"id":604},"timeline-gantt-view",[606],{"type":43,"value":607},"Timeline \u002F Gantt View",{"type":38,"tag":50,"props":609,"children":610},{},[611],{"type":43,"value":612},"Calendar-based view with items on a timeline:",{"type":38,"tag":116,"props":614,"children":615},{},[616,621,626,631],{"type":38,"tag":120,"props":617,"children":618},{},[619],{"type":43,"value":620},"Shows start dates, end dates, and durations",{"type":38,"tag":120,"props":622,"children":623},{},[624],{"type":43,"value":625},"Visualizes parallelism and sequencing",{"type":38,"tag":120,"props":627,"children":628},{},[629],{"type":43,"value":630},"Good for identifying resource conflicts",{"type":38,"tag":120,"props":632,"children":633},{},[634],{"type":43,"value":635},"Shows dependencies between items",{"type":38,"tag":50,"props":637,"children":638},{},[639],{"type":43,"value":640},"When to use: Execution planning with engineering. Identifying scheduling conflicts. NOT good for communicating externally (creates false precision expectations).",{"type":38,"tag":70,"props":642,"children":644},{"id":643},"prioritization-frameworks",[645],{"type":43,"value":237},{"type":38,"tag":96,"props":647,"children":649},{"id":648},"rice-score",[650],{"type":43,"value":651},"RICE Score",{"type":38,"tag":50,"props":653,"children":654},{},[655],{"type":43,"value":656},"Score each initiative on four dimensions, then calculate RICE = (Reach x Impact x Confidence) \u002F Effort",{"type":38,"tag":116,"props":658,"children":659},{},[660,670,680,690],{"type":38,"tag":120,"props":661,"children":662},{},[663,668],{"type":38,"tag":108,"props":664,"children":665},{},[666],{"type":43,"value":667},"Reach",{"type":43,"value":669},": How many users\u002Fcustomers will this affect in a given time period? Use concrete numbers (e.g., \"500 users per quarter\").",{"type":38,"tag":120,"props":671,"children":672},{},[673,678],{"type":38,"tag":108,"props":674,"children":675},{},[676],{"type":43,"value":677},"Impact",{"type":43,"value":679},": How much will this move the needle for each person reached? Score on a scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal.",{"type":38,"tag":120,"props":681,"children":682},{},[683,688],{"type":38,"tag":108,"props":684,"children":685},{},[686],{"type":43,"value":687},"Confidence",{"type":43,"value":689},": How confident are we in the reach and impact estimates? 100% = high confidence (backed by data), 80% = medium (some evidence), 50% = low (gut feel).",{"type":38,"tag":120,"props":691,"children":692},{},[693,698],{"type":38,"tag":108,"props":694,"children":695},{},[696],{"type":43,"value":697},"Effort",{"type":43,"value":699},": How many person-months of work? Include engineering, design, and any other functions.",{"type":38,"tag":50,"props":701,"children":702},{},[703],{"type":43,"value":704},"When to use: When you need a quantitative, defensible prioritization. Good for comparing a large backlog of initiatives. Less good for strategic bets where impact is hard to estimate.",{"type":38,"tag":96,"props":706,"children":708},{"id":707},"moscow",[709],{"type":43,"value":710},"MoSCoW",{"type":38,"tag":50,"props":712,"children":713},{},[714],{"type":43,"value":715},"Categorize items into Must have, Should have, Could have, Won't have:",{"type":38,"tag":116,"props":717,"children":718},{},[719,729,739,749],{"type":38,"tag":120,"props":720,"children":721},{},[722,727],{"type":38,"tag":108,"props":723,"children":724},{},[725],{"type":43,"value":726},"Must have",{"type":43,"value":728},": The roadmap is a failure without these. Non-negotiable commitments.",{"type":38,"tag":120,"props":730,"children":731},{},[732,737],{"type":38,"tag":108,"props":733,"children":734},{},[735],{"type":43,"value":736},"Should have",{"type":43,"value":738},": Important and expected, but delivery is viable without them.",{"type":38,"tag":120,"props":740,"children":741},{},[742,747],{"type":38,"tag":108,"props":743,"children":744},{},[745],{"type":43,"value":746},"Could have",{"type":43,"value":748},": Desirable but clearly lower priority. Include only if capacity allows.",{"type":38,"tag":120,"props":750,"children":751},{},[752,757],{"type":38,"tag":108,"props":753,"children":754},{},[755],{"type":43,"value":756},"Won't have",{"type":43,"value":758},": Explicitly out of scope for this period. Important to list for clarity.",{"type":38,"tag":50,"props":760,"children":761},{},[762],{"type":43,"value":763},"When to use: Scoping a release or quarter. Negotiating with stakeholders about what fits. Good for forcing prioritization conversations.",{"type":38,"tag":96,"props":765,"children":767},{"id":766},"ice-score",[768],{"type":43,"value":769},"ICE Score",{"type":38,"tag":50,"props":771,"children":772},{},[773],{"type":43,"value":774},"Simpler than RICE. Score each item 1-10 on three dimensions:",{"type":38,"tag":116,"props":776,"children":777},{},[778,787,796],{"type":38,"tag":120,"props":779,"children":780},{},[781,785],{"type":38,"tag":108,"props":782,"children":783},{},[784],{"type":43,"value":677},{"type":43,"value":786},": How much will this move the target metric?",{"type":38,"tag":120,"props":788,"children":789},{},[790,794],{"type":38,"tag":108,"props":791,"children":792},{},[793],{"type":43,"value":687},{"type":43,"value":795},": How confident are we in the impact estimate?",{"type":38,"tag":120,"props":797,"children":798},{},[799,804],{"type":38,"tag":108,"props":800,"children":801},{},[802],{"type":43,"value":803},"Ease",{"type":43,"value":805},": How easy is this to implement? (Inverse of effort — higher = easier)",{"type":38,"tag":50,"props":807,"children":808},{},[809],{"type":43,"value":810},"ICE Score = Impact x Confidence x Ease",{"type":38,"tag":50,"props":812,"children":813},{},[814],{"type":43,"value":815},"When to use: Quick prioritization of a feature backlog. Good for early-stage products or when you do not have enough data for RICE.",{"type":38,"tag":96,"props":817,"children":819},{"id":818},"value-vs-effort-matrix",[820],{"type":43,"value":821},"Value vs Effort Matrix",{"type":38,"tag":50,"props":823,"children":824},{},[825],{"type":43,"value":826},"Plot initiatives on a 2x2 matrix:",{"type":38,"tag":116,"props":828,"children":829},{},[830,840,850,860],{"type":38,"tag":120,"props":831,"children":832},{},[833,838],{"type":38,"tag":108,"props":834,"children":835},{},[836],{"type":43,"value":837},"High value, Low effort",{"type":43,"value":839}," (Quick wins): Do these first.",{"type":38,"tag":120,"props":841,"children":842},{},[843,848],{"type":38,"tag":108,"props":844,"children":845},{},[846],{"type":43,"value":847},"High value, High effort",{"type":43,"value":849}," (Big bets): Plan these carefully. Worth the investment but need proper scoping.",{"type":38,"tag":120,"props":851,"children":852},{},[853,858],{"type":38,"tag":108,"props":854,"children":855},{},[856],{"type":43,"value":857},"Low value, Low effort",{"type":43,"value":859}," (Fill-ins): Do these when you have spare capacity.",{"type":38,"tag":120,"props":861,"children":862},{},[863,868],{"type":38,"tag":108,"props":864,"children":865},{},[866],{"type":43,"value":867},"Low value, High effort",{"type":43,"value":869}," (Money pits): Do not do these. Remove from the backlog.",{"type":38,"tag":50,"props":871,"children":872},{},[873],{"type":43,"value":874},"When to use: Visual prioritization in team planning sessions. Good for building shared understanding of tradeoffs.",{"type":38,"tag":70,"props":876,"children":878},{"id":877},"dependency-mapping",[879],{"type":43,"value":880},"Dependency Mapping",{"type":38,"tag":96,"props":882,"children":884},{"id":883},"identifying-dependencies",[885],{"type":43,"value":886},"Identifying Dependencies",{"type":38,"tag":50,"props":888,"children":889},{},[890],{"type":43,"value":891},"Look for dependencies across these categories:",{"type":38,"tag":116,"props":893,"children":894},{},[895,905,915,925,935],{"type":38,"tag":120,"props":896,"children":897},{},[898,903],{"type":38,"tag":108,"props":899,"children":900},{},[901],{"type":43,"value":902},"Technical dependencies",{"type":43,"value":904},": Feature B requires infrastructure work from Feature A",{"type":38,"tag":120,"props":906,"children":907},{},[908,913],{"type":38,"tag":108,"props":909,"children":910},{},[911],{"type":43,"value":912},"Team dependencies",{"type":43,"value":914},": Feature requires work from another team (design, platform, data)",{"type":38,"tag":120,"props":916,"children":917},{},[918,923],{"type":38,"tag":108,"props":919,"children":920},{},[921],{"type":43,"value":922},"External dependencies",{"type":43,"value":924},": Waiting on a vendor, partner, or third-party integration",{"type":38,"tag":120,"props":926,"children":927},{},[928,933],{"type":38,"tag":108,"props":929,"children":930},{},[931],{"type":43,"value":932},"Knowledge dependencies",{"type":43,"value":934},": Need research or investigation results before starting",{"type":38,"tag":120,"props":936,"children":937},{},[938,943],{"type":38,"tag":108,"props":939,"children":940},{},[941],{"type":43,"value":942},"Sequential dependencies",{"type":43,"value":944},": Must ship Feature A before starting Feature B (shared code, user flow)",{"type":38,"tag":96,"props":946,"children":948},{"id":947},"managing-dependencies",[949],{"type":43,"value":950},"Managing Dependencies",{"type":38,"tag":116,"props":952,"children":953},{},[954,959,964,969,974,979],{"type":38,"tag":120,"props":955,"children":956},{},[957],{"type":43,"value":958},"List all dependencies explicitly in the roadmap",{"type":38,"tag":120,"props":960,"children":961},{},[962],{"type":43,"value":963},"Assign an owner to each dependency (who is responsible for resolving it)",{"type":38,"tag":120,"props":965,"children":966},{},[967],{"type":43,"value":968},"Set a \"need by\" date: when does the depending item need this resolved",{"type":38,"tag":120,"props":970,"children":971},{},[972],{"type":43,"value":973},"Build buffer around dependencies — they are the highest-risk items on any roadmap",{"type":38,"tag":120,"props":975,"children":976},{},[977],{"type":43,"value":978},"Flag dependencies that cross team boundaries early — these require coordination",{"type":38,"tag":120,"props":980,"children":981},{},[982],{"type":43,"value":983},"Have a contingency plan: what do you do if the dependency slips?",{"type":38,"tag":96,"props":985,"children":987},{"id":986},"reducing-dependencies",[988],{"type":43,"value":989},"Reducing Dependencies",{"type":38,"tag":116,"props":991,"children":992},{},[993,998,1003,1008],{"type":38,"tag":120,"props":994,"children":995},{},[996],{"type":43,"value":997},"Can you build a simpler version that avoids the dependency?",{"type":38,"tag":120,"props":999,"children":1000},{},[1001],{"type":43,"value":1002},"Can you parallelize by using an interface contract or mock?",{"type":38,"tag":120,"props":1004,"children":1005},{},[1006],{"type":43,"value":1007},"Can you sequence differently to move the dependency earlier?",{"type":38,"tag":120,"props":1009,"children":1010},{},[1011],{"type":43,"value":1012},"Can you absorb the work into your team to remove the cross-team coordination?",{"type":38,"tag":70,"props":1014,"children":1016},{"id":1015},"capacity-planning",[1017],{"type":43,"value":1018},"Capacity Planning",{"type":38,"tag":96,"props":1020,"children":1022},{"id":1021},"estimating-capacity",[1023],{"type":43,"value":1024},"Estimating Capacity",{"type":38,"tag":116,"props":1026,"children":1027},{},[1028,1033,1038,1043],{"type":38,"tag":120,"props":1029,"children":1030},{},[1031],{"type":43,"value":1032},"Start with the number of engineers and the time period",{"type":38,"tag":120,"props":1034,"children":1035},{},[1036],{"type":43,"value":1037},"Subtract known overhead: meetings, on-call rotations, interviews, holidays, PTO",{"type":38,"tag":120,"props":1039,"children":1040},{},[1041],{"type":43,"value":1042},"A common rule of thumb: engineers spend 60-70% of time on planned feature work",{"type":38,"tag":120,"props":1044,"children":1045},{},[1046],{"type":43,"value":1047},"Factor in team ramp time for new members",{"type":38,"tag":96,"props":1049,"children":1051},{"id":1050},"allocating-capacity",[1052],{"type":43,"value":1053},"Allocating Capacity",{"type":38,"tag":50,"props":1055,"children":1056},{},[1057],{"type":43,"value":1058},"A healthy allocation for most product teams:",{"type":38,"tag":116,"props":1060,"children":1061},{},[1062,1072,1082],{"type":38,"tag":120,"props":1063,"children":1064},{},[1065,1070],{"type":38,"tag":108,"props":1066,"children":1067},{},[1068],{"type":43,"value":1069},"70% planned features",{"type":43,"value":1071},": Roadmap items that advance strategic goals",{"type":38,"tag":120,"props":1073,"children":1074},{},[1075,1080],{"type":38,"tag":108,"props":1076,"children":1077},{},[1078],{"type":43,"value":1079},"20% technical health",{"type":43,"value":1081},": Tech debt, reliability, performance, developer experience",{"type":38,"tag":120,"props":1083,"children":1084},{},[1085,1090],{"type":38,"tag":108,"props":1086,"children":1087},{},[1088],{"type":43,"value":1089},"10% unplanned",{"type":43,"value":1091},": Buffer for urgent issues, quick wins, and requests from other teams",{"type":38,"tag":50,"props":1093,"children":1094},{},[1095],{"type":43,"value":1096},"Adjust ratios based on team context:",{"type":38,"tag":116,"props":1098,"children":1099},{},[1100,1105,1110,1115],{"type":38,"tag":120,"props":1101,"children":1102},{},[1103],{"type":43,"value":1104},"New product: more feature work, less tech debt",{"type":38,"tag":120,"props":1106,"children":1107},{},[1108],{"type":43,"value":1109},"Mature product: more tech debt and reliability investment",{"type":38,"tag":120,"props":1111,"children":1112},{},[1113],{"type":43,"value":1114},"Post-incident: more reliability, less features",{"type":38,"tag":120,"props":1116,"children":1117},{},[1118],{"type":43,"value":1119},"Rapid growth: more scalability and performance",{"type":38,"tag":96,"props":1121,"children":1123},{"id":1122},"capacity-vs-ambition",[1124],{"type":43,"value":1125},"Capacity vs Ambition",{"type":38,"tag":116,"props":1127,"children":1128},{},[1129,1134,1139,1144],{"type":38,"tag":120,"props":1130,"children":1131},{},[1132],{"type":43,"value":1133},"If roadmap commitments exceed capacity, something must give",{"type":38,"tag":120,"props":1135,"children":1136},{},[1137],{"type":43,"value":1138},"Do not solve capacity problems by pretending people can do more — solve by cutting scope",{"type":38,"tag":120,"props":1140,"children":1141},{},[1142],{"type":43,"value":1143},"When adding to the roadmap, always ask: \"What comes off?\"",{"type":38,"tag":120,"props":1145,"children":1146},{},[1147],{"type":43,"value":1148},"Better to commit to fewer things and deliver reliably than to overcommit and disappoint",{"type":38,"tag":70,"props":1150,"children":1152},{"id":1151},"communicating-roadmap-changes",[1153],{"type":43,"value":1154},"Communicating Roadmap Changes",{"type":38,"tag":96,"props":1156,"children":1158},{"id":1157},"when-the-roadmap-changes",[1159],{"type":43,"value":1160},"When the Roadmap Changes",{"type":38,"tag":50,"props":1162,"children":1163},{},[1164],{"type":43,"value":1165},"Common triggers for roadmap changes:",{"type":38,"tag":116,"props":1167,"children":1168},{},[1169,1174,1179,1184,1189,1194],{"type":38,"tag":120,"props":1170,"children":1171},{},[1172],{"type":43,"value":1173},"New strategic priority from leadership",{"type":38,"tag":120,"props":1175,"children":1176},{},[1177],{"type":43,"value":1178},"Customer feedback or research that changes priorities",{"type":38,"tag":120,"props":1180,"children":1181},{},[1182],{"type":43,"value":1183},"Technical discovery that changes estimates",{"type":38,"tag":120,"props":1185,"children":1186},{},[1187],{"type":43,"value":1188},"Dependency slip from another team",{"type":38,"tag":120,"props":1190,"children":1191},{},[1192],{"type":43,"value":1193},"Resource change (team grows or shrinks, key person leaves)",{"type":38,"tag":120,"props":1195,"children":1196},{},[1197],{"type":43,"value":1198},"Competitive move that requires response",{"type":38,"tag":96,"props":1200,"children":1202},{"id":1201},"how-to-communicate-changes",[1203],{"type":43,"value":1204},"How to Communicate Changes",{"type":38,"tag":1206,"props":1207,"children":1208},"ol",{},[1209,1219,1229,1239,1249],{"type":38,"tag":120,"props":1210,"children":1211},{},[1212,1217],{"type":38,"tag":108,"props":1213,"children":1214},{},[1215],{"type":43,"value":1216},"Acknowledge the change",{"type":43,"value":1218},": Be direct about what is changing and why",{"type":38,"tag":120,"props":1220,"children":1221},{},[1222,1227],{"type":38,"tag":108,"props":1223,"children":1224},{},[1225],{"type":43,"value":1226},"Explain the reason",{"type":43,"value":1228},": What new information drove this decision?",{"type":38,"tag":120,"props":1230,"children":1231},{},[1232,1237],{"type":38,"tag":108,"props":1233,"children":1234},{},[1235],{"type":43,"value":1236},"Show the tradeoff",{"type":43,"value":1238},": What was deprioritized to make room? Or what is slipping?",{"type":38,"tag":120,"props":1240,"children":1241},{},[1242,1247],{"type":38,"tag":108,"props":1243,"children":1244},{},[1245],{"type":43,"value":1246},"Show the new plan",{"type":43,"value":1248},": Updated roadmap with the changes reflected",{"type":38,"tag":120,"props":1250,"children":1251},{},[1252,1257],{"type":38,"tag":108,"props":1253,"children":1254},{},[1255],{"type":43,"value":1256},"Acknowledge impact",{"type":43,"value":1258},": Who is affected and how? Stakeholders who were expecting deprioritized items need to hear it directly.",{"type":38,"tag":96,"props":1260,"children":1262},{"id":1261},"avoiding-roadmap-whiplash",[1263],{"type":43,"value":1264},"Avoiding Roadmap Whiplash",{"type":38,"tag":116,"props":1266,"children":1267},{},[1268,1273,1278,1283],{"type":38,"tag":120,"props":1269,"children":1270},{},[1271],{"type":43,"value":1272},"Do not change the roadmap for every piece of new information. Have a threshold for change.",{"type":38,"tag":120,"props":1274,"children":1275},{},[1276],{"type":43,"value":1277},"Batch roadmap updates at natural cadences (monthly, quarterly) unless something is truly urgent.",{"type":38,"tag":120,"props":1279,"children":1280},{},[1281],{"type":43,"value":1282},"Distinguish between \"roadmap change\" (strategic reprioritization) and \"scope adjustment\" (normal execution refinement).",{"type":38,"tag":120,"props":1284,"children":1285},{},[1286],{"type":43,"value":1287},"Track how often the roadmap changes. Frequent changes may signal unclear strategy, not good responsiveness.",{"type":38,"tag":70,"props":1289,"children":1291},{"id":1290},"output-format",[1292],{"type":43,"value":1293},"Output Format",{"type":38,"tag":50,"props":1295,"children":1296},{},[1297,1299,1304,1306,1311,1312,1317,1318,1323,1324,1329],{"type":43,"value":1298},"Use a clear, scannable format. Tables work well for roadmap items. Use text status labels: ",{"type":38,"tag":108,"props":1300,"children":1301},{},[1302],{"type":43,"value":1303},"Done",{"type":43,"value":1305},", ",{"type":38,"tag":108,"props":1307,"children":1308},{},[1309],{"type":43,"value":1310},"On Track",{"type":43,"value":1305},{"type":38,"tag":108,"props":1313,"children":1314},{},[1315],{"type":43,"value":1316},"At Risk",{"type":43,"value":1305},{"type":38,"tag":108,"props":1319,"children":1320},{},[1321],{"type":43,"value":1322},"Blocked",{"type":43,"value":1305},{"type":38,"tag":108,"props":1325,"children":1326},{},[1327],{"type":43,"value":1328},"Not Started",{"type":43,"value":63},{"type":38,"tag":70,"props":1331,"children":1333},{"id":1332},"tips",[1334],{"type":43,"value":1335},"Tips",{"type":38,"tag":116,"props":1337,"children":1338},{},[1339,1344,1349,1354,1359],{"type":38,"tag":120,"props":1340,"children":1341},{},[1342],{"type":43,"value":1343},"A roadmap is a communication tool, not a project plan. Keep it at the right altitude — themes and outcomes, not tasks.",{"type":38,"tag":120,"props":1345,"children":1346},{},[1347],{"type":43,"value":1348},"When reprioritizing, always ask what changed. Priority shifts should be driven by new information, not whim.",{"type":38,"tag":120,"props":1350,"children":1351},{},[1352],{"type":43,"value":1353},"Flag capacity issues early. If the roadmap has more work than the team can handle, say so.",{"type":38,"tag":120,"props":1355,"children":1356},{},[1357],{"type":43,"value":1358},"Dependencies are the biggest risk to roadmaps. Surface them explicitly.",{"type":38,"tag":120,"props":1360,"children":1361},{},[1362],{"type":43,"value":1363},"If the user asks to add something, always ask what comes off or moves. Roadmaps are zero-sum against capacity.",{"items":1365,"total":1482},[1366,1382,1398,1414,1432,1451,1467],{"slug":1367,"name":1367,"fn":1368,"description":1369,"org":1370,"tags":1371,"stars":20,"repoUrl":21,"updatedAt":1381},"accessibility-review","run WCAG accessibility audits","Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with \"audit accessibility\", \"check a11y\", \"is this accessible?\", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1372,1375,1378],{"name":1373,"slug":1374,"type":16},"Accessibility","accessibility",{"name":1376,"slug":1377,"type":16},"Design","design",{"name":1379,"slug":1380,"type":16},"WCAG","wcag","2026-04-06T17:58:05.682394",{"slug":1383,"name":1383,"fn":1384,"description":1385,"org":1386,"tags":1387,"stars":20,"repoUrl":21,"updatedAt":1397},"account-research","research accounts for sales intel","Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with \"research [company]\", \"look up [person]\", \"intel on [prospect]\", \"who is [name] at [company]\", or \"tell me about [company]\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1388,1391,1394],{"name":1389,"slug":1390,"type":16},"CRM","crm",{"name":1392,"slug":1393,"type":16},"Research","research",{"name":1395,"slug":1396,"type":16},"Sales","sales","2026-04-06T17:56:41.410418",{"slug":1399,"name":1399,"fn":1400,"description":1401,"org":1402,"tags":1403,"stars":20,"repoUrl":21,"updatedAt":1413},"analyze","answer data questions and run analyses","Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1404,1407,1410],{"name":1405,"slug":1406,"type":16},"Analytics","analytics",{"name":1408,"slug":1409,"type":16},"Data Analysis","data-analysis",{"name":1411,"slug":1412,"type":16},"SQL","sql","2026-04-06T17:57:21.593647",{"slug":1415,"name":1415,"fn":1416,"description":1417,"org":1418,"tags":1419,"stars":20,"repoUrl":21,"updatedAt":1431},"architecture","create and evaluate architecture decision records","Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1420,1423,1425,1428],{"name":1421,"slug":1422,"type":16},"ADR","adr",{"name":1424,"slug":1415,"type":16},"Architecture",{"name":1426,"slug":1427,"type":16},"Documentation","documentation",{"name":1429,"slug":1430,"type":16},"Engineering","engineering","2026-04-06T17:57:49.26444",{"slug":1433,"name":1433,"fn":1434,"description":1435,"org":1436,"tags":1437,"stars":20,"repoUrl":21,"updatedAt":1450},"audit-support","support SOX 404 control testing","Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1438,1441,1444,1447],{"name":1439,"slug":1440,"type":16},"Audit","audit",{"name":1442,"slug":1443,"type":16},"Finance","finance",{"name":1445,"slug":1446,"type":16},"Regulatory Compliance","regulatory-compliance",{"name":1448,"slug":1449,"type":16},"SOX","sox","2026-04-06T17:57:36.714815",{"slug":1452,"name":1452,"fn":1453,"description":1454,"org":1455,"tags":1456,"stars":20,"repoUrl":21,"updatedAt":1466},"brand-review","review content against brand voice","Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before\u002Fafter fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1457,1460,1463],{"name":1458,"slug":1459,"type":16},"Branding","branding",{"name":1461,"slug":1462,"type":16},"Marketing","marketing",{"name":1464,"slug":1465,"type":16},"Writing","writing","2026-04-06T17:58:19.548331",{"slug":1468,"name":1468,"fn":1469,"description":1470,"org":1471,"tags":1472,"stars":20,"repoUrl":21,"updatedAt":1481},"brand-voice-enforcement","enforce brand voice in content","This skill applies brand guidelines to content creation. It should be used when the user asks to \"write an email\", \"draft a proposal\", \"create a pitch deck\", \"write a LinkedIn post\", \"draft a presentation\", \"write a Slack message\", \"draft sales content\", or any content creation request where brand voice should be applied. Also triggers on \"on-brand\", \"brand voice\", \"enforce voice\", \"apply brand guidelines\", \"brand-aligned content\", \"write in our voice\", \"use our brand tone\", \"make this sound like us\", \"rewrite this in our tone\", or \"this doesn't sound on-brand\". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1473,1474,1477,1480],{"name":1458,"slug":1459,"type":16},{"name":1475,"slug":1476,"type":16},"Communications","communications",{"name":1478,"slug":1479,"type":16},"Content Creation","content-creation",{"name":1464,"slug":1465,"type":16},"2026-04-06T18:00:23.528956",200,{"items":1484,"total":1661},[1485,1504,1516,1528,1547,1558,1579,1599,1609,1624,1632,1645],{"slug":1486,"name":1486,"fn":1487,"description":1488,"org":1489,"tags":1490,"stars":1501,"repoUrl":1502,"updatedAt":1503},"algorithmic-art","create algorithmic art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1491,1494,1495,1498],{"name":1492,"slug":1493,"type":16},"Creative","creative",{"name":1376,"slug":1377,"type":16},{"name":1496,"slug":1497,"type":16},"Generative Art","generative-art",{"name":1499,"slug":1500,"type":16},"JavaScript","javascript",161831,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills","2026-04-06T17:56:15.455818",{"slug":1505,"name":1505,"fn":1506,"description":1507,"org":1508,"tags":1509,"stars":1501,"repoUrl":1502,"updatedAt":1515},"brand-guidelines","apply Anthropic brand colors and typography","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1510,1511,1512],{"name":1458,"slug":1459,"type":16},{"name":1376,"slug":1377,"type":16},{"name":1513,"slug":1514,"type":16},"Typography","typography","2026-04-06T17:56:05.042852",{"slug":1517,"name":1517,"fn":1518,"description":1519,"org":1520,"tags":1521,"stars":1501,"repoUrl":1502,"updatedAt":1527},"canvas-design","create posters and visual art as PNG or PDF","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1522,1523,1524],{"name":1492,"slug":1493,"type":16},{"name":1376,"slug":1377,"type":16},{"name":1525,"slug":1526,"type":16},"PDF","pdf","2026-04-06T17:56:03.794732",{"slug":1529,"name":1529,"fn":1530,"description":1531,"org":1532,"tags":1533,"stars":1501,"repoUrl":1502,"updatedAt":1546},"claude-api","build apps with the Claude API","Reference for the Claude API \u002F Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.\nTRIGGER — read BEFORE opening the target file; don't skip because it \"looks like a one-liner\" — whenever: the prompt names Claude\u002FAnthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing\u002Fmodel choice\u002Flimits\u002Fcaching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent\u002FMCP\u002Ftool-definition\u002Fmulti-agent\u002FRAG\u002FLLM-judge\u002Fcomputer-use; generate\u002Fsummarize\u002Fextract\u002Fclassify\u002Frewrite\u002Fconverse over NL; debugging refusals\u002Fcutoffs\u002Fstreaming\u002Ftool-calls\u002Ftokens).\nSKIP only when another provider is being worked on (overrides all triggers): OpenAI\u002FGPT\u002FGemini\u002FLlama\u002FMistral\u002FCohere\u002FOllama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1534,1537,1538,1541,1543],{"name":1535,"slug":1536,"type":16},"Agents","agents",{"name":9,"slug":8,"type":16},{"name":1539,"slug":1540,"type":16},"Anthropic SDK","anthropic-sdk",{"name":1542,"slug":1529,"type":16},"Claude API",{"name":1544,"slug":1545,"type":16},"LLM","llm","2026-07-28T05:36:08.213335",{"slug":1548,"name":1548,"fn":1549,"description":1550,"org":1551,"tags":1552,"stars":1501,"repoUrl":1502,"updatedAt":1557},"doc-coauthoring","co-author documentation and technical specs","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1553,1554],{"name":1426,"slug":1427,"type":16},{"name":1555,"slug":1556,"type":16},"Technical Writing","technical-writing","2026-04-06T17:56:14.18897",{"slug":1559,"name":1559,"fn":1560,"description":1561,"org":1562,"tags":1563,"stars":1501,"repoUrl":1502,"updatedAt":1578},"docx","create and edit Word documents","Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1564,1567,1569,1572,1575],{"name":1565,"slug":1566,"type":16},"Documents","documents",{"name":1568,"slug":1559,"type":16},"DOCX",{"name":1570,"slug":1571,"type":16},"Office","office",{"name":1573,"slug":1574,"type":16},"Templates","templates",{"name":1576,"slug":1577,"type":16},"Word","word","2026-07-18T05:16:23.136271",{"slug":1580,"name":1580,"fn":1581,"description":1582,"org":1583,"tags":1584,"stars":1501,"repoUrl":1502,"updatedAt":1598},"frontend-design","design production-grade frontend interfaces","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1585,1586,1589,1592,1595],{"name":1376,"slug":1377,"type":16},{"name":1587,"slug":1588,"type":16},"Frontend","frontend",{"name":1590,"slug":1591,"type":16},"React","react",{"name":1593,"slug":1594,"type":16},"Tailwind CSS","tailwind-css",{"name":1596,"slug":1597,"type":16},"UI Components","ui-components","2026-04-06T17:56:16.723469",{"slug":1600,"name":1600,"fn":1601,"description":1602,"org":1603,"tags":1604,"stars":1501,"repoUrl":1502,"updatedAt":1608},"internal-comms","write internal company communications","A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1605,1606,1607],{"name":1475,"slug":1476,"type":16},{"name":1573,"slug":1574,"type":16},{"name":1464,"slug":1465,"type":16},"2026-04-06T17:56:20.695522",{"slug":1610,"name":1610,"fn":1611,"description":1612,"org":1613,"tags":1614,"stars":1501,"repoUrl":1502,"updatedAt":1623},"mcp-builder","build MCP servers","Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node\u002FTypeScript (MCP SDK).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1615,1616,1619,1620],{"name":1535,"slug":1536,"type":16},{"name":1617,"slug":1618,"type":16},"API Development","api-development",{"name":1544,"slug":1545,"type":16},{"name":1621,"slug":1622,"type":16},"MCP","mcp","2026-04-06T17:56:10.357665",{"slug":1526,"name":1526,"fn":1625,"description":1626,"org":1627,"tags":1628,"stars":1501,"repoUrl":1502,"updatedAt":1631},"read edit and manipulate PDF files","Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text\u002Ftables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting\u002Fdecrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1629,1630],{"name":1565,"slug":1566,"type":16},{"name":1525,"slug":1526,"type":16},"2026-04-06T17:56:02.483316",{"slug":1633,"name":1633,"fn":1634,"description":1635,"org":1636,"tags":1637,"stars":1501,"repoUrl":1502,"updatedAt":1644},"pptx","create and edit PowerPoint presentations","Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1638,1641],{"name":1639,"slug":1640,"type":16},"PowerPoint","powerpoint",{"name":1642,"slug":1643,"type":16},"Presentations","presentations","2026-07-18T05:16:24.1471",{"slug":1646,"name":1646,"fn":1647,"description":1648,"org":1649,"tags":1650,"stars":1501,"repoUrl":1502,"updatedAt":1660},"skill-creator","create and optimize agent skills","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[1651,1652,1653,1656,1659],{"name":1535,"slug":1536,"type":16},{"name":1426,"slug":1427,"type":16},{"name":1654,"slug":1655,"type":16},"Evals","evals",{"name":1657,"slug":1658,"type":16},"Performance","performance",{"name":1555,"slug":1556,"type":16},"2026-04-19T06:45:40.804",490]