product-update

星标12

分支3

更新时间2026年7月16日 17:57

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

Unabyss

Unabyss/unabyss-skills

打开 GitHub 仓库查看创作者相关仓库

下载

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

同仓库更多 Skills

同仓库

product-hunt-launch-kit

Unabyss/unabyss-skills

Generate a personalized Product Hunt launch kit grounded in live product context from the Unabyss MCP (positioning, ICP, pricing, founder voice). Produces one copy-paste-ready markdown brief with tagline options, product descriptions, a maker comment, a 2-email influencer outreach sequence, an influencer materials kit, LinkedIn reshare posts for teammates/investors/network, a founder announcement post, and 1:1 support DMs. Use whenever the user mentions Product Hunt, "PH launch," "PH prep," "maker comment," or "launch tagline," or wants copy and outreach for a Product Hunt launch. Requires the Unabyss MCP.

2026-07-1612

brand-voice

Unabyss/unabyss-skills

Derive a founder or company voice profile from real writing samples found in connected sources, then use it to ensure all content sounds like the actual person — not generic AI copy. Use this skill whenever the user asks about their writing style, brand voice, tone of voice, how they sound, or wants any content to match their voice. Also trigger when another skill needs a voice profile before writing copy, posts, emails, or outreach.

2026-07-1612

company-context

Unabyss/unabyss-skills

Load a full picture of the user's company — what it does, who it's for, current stage, traction, team, and open priorities — from Unabyss as the source of truth. Use this skill at the start of any session where company context would improve the output, before running skills that need to know what the company does or where it stands. Also trigger when the user says load my company context, what do you know about my company, or before any task involving positioning, fundraising, hiring, or GTM.

2026-07-1612

content-engine

Unabyss/unabyss-skills

Turn the founder's own recent thinking, work, and conversations into platform-native content — LinkedIn posts, X threads, newsletters, or long-form articles — written in their actual voice. Use this skill whenever the user wants to create social posts, write a newsletter, draft a thread, repurpose something into content, or asks what they should post about. Also trigger when someone says they should be posting more but never have time, or wants to build in public.

2026-07-1612

customer-pulse

Unabyss/unabyss-skills

Surface what real customers are saying right now — praise worth amplifying, frustrations worth acting on, and accounts showing churn risk. Only active customers, last 1–2 weeks. Use this skill whenever the user asks "what are customers saying", "any good testimonials lately", "who's unhappy", "any churn risk", "what's the customer sentiment", "customer feedback this week", "are customers happy", "what are users complaining about", "any wins from customers", "highlight customer feedback", or anything that implies they want a founder-level read on customer sentiment. Requires Unabyss MCP.

2026-07-1612

daily-brief

Unabyss/unabyss-skills

Start the day calibrated in under 60 seconds — today's meetings, open loops that need a reply, and the top 3 priorities to focus on. Use this skill whenever the user wants a morning brief, daily digest, start of day summary, or asks what's on their plate today. Also trigger when someone says 'what does my day look like', 'catch me up', 'what should I focus on today', or 'what's first'.

2026-07-1612

name

product-update

description

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

product-update

Product Update

Required Integrations

How to Run

Step 1 — Check for an existing export

Step 2 — Run agentic_query

Step 3 — Synthesize the update

Output Rules

同仓库更多 Skills

同仓库更多 Skills

Product Update

Required Integrations

How to Run

Step 1 — Check for an existing export

Step 2 — Run agentic_query

Step 3 — Synthesize the update

Output Rules

Step 2 — Run `agentic_query`

Step 2 — Run `agentic_query`