| name | product-update |
| description | Give a non-technical founder a clear picture of where the product stands right now — what shipped, what's in progress, what's blocked, what customers are asking for, and what the team is focused on next. Use this skill whenever the user asks "what did we ship this week", "what are we working on", "what's the status of the product", "what's our biggest bug right now", "what's in progress", "what's blocking the team", "product update", "engineering update", "what's on the roadmap", "what are customers complaining about", "what's the team focused on", or anything that implies they want a snapshot of product development without reading through tickets or Slack threads. Requires Unabyss MCP. |
Product Update
Give a non-technical founder a complete, plain-language snapshot of where the product stands — what's shipped, what's in flight, what's stuck, and what's coming next.
Required Integrations
This skill uses Unabyss MCP — specifically agentic_query for cross-source synthesis across product, engineering, and customer signals.
If Unabyss is not connected, tell the user: "This skill requires Unabyss MCP. You can connect it from the Tools menu."
How to Run
Step 1 — Check for an existing export
Call export_list first. If a recent product update export exists and is fresh, call export_read — no need to regenerate.
Step 2 — Run agentic_query
If no fresh export exists, use agentic_query — product signals are scattered across many tools:
Look across all connected sources for signals about product and engineering activity from the last 7–14 days. Find:
- What has been released, shipped, or deployed — features, fixes, changes that are live
- What is currently being worked on — features or improvements in progress
- What is blocked, delayed, or deprioritized — and why
- What bugs or issues are currently open and treated as priority
- What customers or users have been asking for, complaining about, or flagging repeatedly
- What is planned or coming next — near-term roadmap, committed decisions
- Any significant technical decisions made recently
- Any debates or open questions the team hasn't resolved yet
Return raw signals, not a summary. Be specific — feature names, who raised things, dates where available.
Call agentic_query_read with the returned query id to retrieve the result.
Step 3 — Synthesize the update
Plain language throughout — no ticket IDs, no jargon, no acronyms without explanation.
Product Update — [Date]
✅ Shipped — What's live. What it does and why it matters.
🔨 In progress — What's being built, when expected, who's driving it.
🚧 Blocked or delayed — What stalled and the honest reason why.
🐛 Biggest open issues — Top 2–3 bugs, plain description, user impact.
📣 What customers are asking for — Recurring requests from real users, grouped by theme.
🗺️ What's next — Committed roadmap only, not wishlist.
❓ Open decisions — Questions where founder input is needed.
Output Rules
- Use
export_read if a fresh export exists — skip agentic_query
- Plain language — explain any technical term in one clause
- Omit empty sections entirely
- If signals are thin: "Limited signal — consider asking the team for a written update"
- No preamble before the update header
- Keep under 400 words
