菜单
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/Next/Later view from scratch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Claude as the trainer. Walks an SMB owner through connecting their first two tools, runs one recipe to prove immediate value, interviews them about their business (industry, size, top three headaches), stores that context persistently so every other skill benefits, and sets a weekly check-in cadence. Use when the owner is getting started or says any of: "set me up," "setup," "help me get set up," "get started," "help me get started," "get me started," "what can you do," "I'm new to this," or is in their first session.
Produces a one-page cross-functional business snapshot for SMB owners — cash position (QuickBooks), sales trend (PayPal/Square), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail/Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a weekly summary, a Monday brief, or says anything like "what am I missing" or "catch me up on the business."
Ranks the top-5 leads most worth calling today, supplies talking points from email history, blocks time on the calendar, and drafts follow-up messages. Accepts optional count and date arguments.
Takes an approved content brief and executes a campaign end-to-end: builds the posting calendar, generates Canva designs for social posts, drafts caption and email copy, and stages social sends in HubSpot. Canva is used for social posts only (Instagram, Facebook, X, LinkedIn) — email content is drafted as plain text and surfaced inline for the owner to send from their own tool. Every step requires explicit owner approval. Use when the user says "make the content," "generate the posts," "create the assets," "turn this into a campaign," or hands off an approved brief for execution.
Reads AR/AP, historical cash timing, and known fixed costs from QuickBooks, PayPal, Stripe, or Square — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.
Closes the month — reconciles QB vs payment processors, flags gaps, writes P&L narrative, exports close packet. Accepts optional month and save-to arguments.
| name | roadmap-update |
| description | 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/Next/Later view from scratch. |
| argument-hint | <update description> |
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Update, create, or reprioritize a product roadmap.
/roadmap-update $ARGUMENTS
If ~~project tracker is connected:
If no project management tool is connected:
Ask what the user wants to do:
Add item: New feature, initiative, or work item to the roadmap
Update status: Change status of existing items
Reprioritize: Change the order or priority of items
Move timeline: Shift dates for items
Create new roadmap: Build a roadmap from scratch
Produce a roadmap view with:
Quick summary: X items in progress, Y completed this period, Z at risk.
For each item, show:
Group items by:
If this is an update to an existing roadmap, summarize what changed:
After generating the roadmap:
The simplest and often most effective roadmap format:
When to use: Most teams, most of the time. Especially good for communicating externally or to leadership because it avoids false precision on dates.
Organize the roadmap around 2-3 themes per quarter:
When to use: When you need to show strategic alignment. Good for planning meetings and executive communication.
Map roadmap items directly to Objectives and Key Results:
When to use: Organizations that run on OKRs. Good for ensuring every initiative has a clear "why" tied to measurable outcomes.
Calendar-based view with items on a timeline:
When to use: Execution planning with engineering. Identifying scheduling conflicts. NOT good for communicating externally (creates false precision expectations).
Score each initiative on four dimensions, then calculate RICE = (Reach x Impact x Confidence) / Effort
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.
Categorize items into Must have, Should have, Could have, Won't have:
When to use: Scoping a release or quarter. Negotiating with stakeholders about what fits. Good for forcing prioritization conversations.
Simpler than RICE. Score each item 1-10 on three dimensions:
ICE Score = Impact x Confidence x Ease
When to use: Quick prioritization of a feature backlog. Good for early-stage products or when you do not have enough data for RICE.
Plot initiatives on a 2x2 matrix:
When to use: Visual prioritization in team planning sessions. Good for building shared understanding of tradeoffs.
Look for dependencies across these categories:
A healthy allocation for most product teams:
Adjust ratios based on team context:
Common triggers for roadmap changes:
Use a clear, scannable format. Tables work well for roadmap items. Use text status labels: Done, On Track, At Risk, Blocked, Not Started.