AIOProductOS

View saved version →

---
name: daily
description: Daily PM briefing — your plate, blockers, and the one thing to do next.
---

# daily

Give the connected member their daily briefing.
1) get_product_brain for context.
2) list_tasks + pm_meta — what's assigned to them, what's blocked, what's overdue or stale.
3) Scan the support inbox (list_conversations) and upcoming calls (list_bookings) for anything urgent.
Output a tight briefing: top priorities today, blockers needing a decision, and ONE recommended next action. Read-only unless they ask you to act.

## Notes

- This routine runs against the connected AIOProductOS workspace through the
  plugin's MCP server. If no server is connected, say so plainly instead of
  inventing an answer — every number here is supposed to be real.
- Prioritise on evidence: affected accounts, MRR, reach. Never invent a score.
- Claim only the writes you actually made.

<!-- GENERATED by build-plugin.mjs from MCP_PROMPTS in src/registry.ts.
     Edit the routine there; edits to this file are overwritten. -->

View saved version →

---
name: standup
description: Board standup — what moved, what's blocked, what needs you today (read-only).
---

# standup

Run the product standup for the connected org. Read-only — don't change anything.
1) pm_meta to resolve lists / statuses / members.
2) list_tasks to read the active board.
Report briefly: what's in progress, what's blocked (and why), what's gone stale with no movement, and the 1–3 decisions that need a human today. Pull get_product_brain if revenue/account context sharpens the call. End with the single most important thing to do next.

## Notes

- This routine runs against the connected AIOProductOS workspace through the
  plugin's MCP server. If no server is connected, say so plainly instead of
  inventing an answer — every number here is supposed to be real.
- Prioritise on evidence: affected accounts, MRR, reach. Never invent a score.
- Claim only the writes you actually made.

<!-- GENERATED by build-plugin.mjs from MCP_PROMPTS in src/registry.ts.
     Edit the routine there; edits to this file are overwritten. -->

View saved version →

---
name: triage
description: Triage — turn fresh customer signal into prioritized, spine-linked work.
---

# triage

Run intake triage for the connected org. Follow get_pm_playbook.
1) get_product_brain — ground in revenue, top accounts, recent verbatim signal, and open work.
2) Review the board (list_tasks, pm_meta) and any fresh insights.
3) Prioritize on EVIDENCE — affected accounts + MRR + reach — never an invented score.
4) Make the writes you're confident in: create_task / update_task, linking insight→feature→task; assign owners; place the clear ones in the current sprint. SURFACE the judgment calls for a human instead of guessing.
Confirm only the writes you actually made.

## Notes

- This routine runs against the connected AIOProductOS workspace through the
  plugin's MCP server. If no server is connected, say so plainly instead of
  inventing an answer — every number here is supposed to be real.
- Prioritise on evidence: affected accounts, MRR, reach. Never invent a score.
- Claim only the writes you actually made.

<!-- GENERATED by build-plugin.mjs from MCP_PROMPTS in src/registry.ts.
     Edit the routine there; edits to this file are overwritten. -->