name: product-ops-manager
description: Support sprint ceremonies, releases, KPIs, stakeholder comms, dependencies, and status reports using Asana data.

Product Ops Manager Skill

An operations-focused PM skill that turns Asana data into ceremonies, communications, release plans, KPI dashboards, and status reports.

When to use this skill

Use this skill when you say:
- “Prepare agendas for sprint ceremonies.”
- “Draft a stakeholder status email from Asana.”
- “Help me plan this release and write release notes.”
- “Create a KPI snapshot / weekly status report.”
- “Map dependencies and blockers across teams.”

Inputs this skill uses

Provide:
- Asana context: project(s), team, or saved search, plus sprint dates.
- Ceremony type or report type you’re working on.
- Any templates you want to mirror (e.g., weekly report template).

Core behaviors

A. Sprint ceremonies (SC)

• For planning, standup, review, and retro:
• Pull sprint data from Asana:
  • Task counts by status.
  • Assignee workloads.
  • Velocity and completion vs plan.
  • Blockers and overdue items.
• Generate ceremony-specific content:
  • Planning: capacity estimate, candidate backlog list, draft sprint goal options.
  • Standup: Yesterday / Today / Blockers view, pre-populated with recent changes.
  • Review: list of completed work, demo agenda, talking points.
  • Retro: metrics snapshot, prompts, and sections for wins / issues / actions.

B. Stakeholder communications (SK)

• Draft emails or docs for:
• Status updates (project / sprint).
• Meeting prep (agenda + supporting data).
• Escalations (Issue → Impact → Root cause → Resolution → Ask).
• Announcements (what changed, who’s impacted, what to do).
• Use Asana to back statements with real numbers:
• Completed items, in-progress work, risks and blockers.
• Format output ready to paste into Gmail:
• Subject line, recipients (placeholder), body with clear sections.

C. Release management (RM)

• For a given release:
• Identify scope from Asana (tasks in a release section or tag).
• Propose a release timeline and key checkpoints.
• Generate:
  • Pre-release checklist (flags, QA sign-off, approvals, monitoring, rollback plan).
  • Release notes grouped by platform / area.
  • Go / No-go summary with risks and blockers.
  • Post-release review outline.

D. KPI tracking & dashboards (KP)

• From Asana data:
• Calculate velocity, completion rate, lead time, cycle time, bug rates, and estimation accuracy (when possible).
• Show trends over recent sprints or weeks.
• Output:
• Simple table or dashboard with trend arrows.
• Short narrative (3–5 sentences) interpreting the numbers.

E. Dependency tracking (DT)

• Find blocked / blocking tasks across Asana:
• Build a dependency map (Feature | Depends On | Owner Team | Blocking Team | Status | Due Date | Risk).
• Identify critical paths and overdue dependencies.
• Suggest follow-up actions and draft messages to blocking teams.

F. Status reports (SR)

• Generate a weekly or sprint status document that includes:
• Executive summary and overall status (green / yellow / red).
• Accomplishments, in-progress work, and next priorities.
• Risks and blockers with owners.
• Key metrics (planned vs completed, velocity trend).
• Align structure with your existing weekly report template when available.

Output format

• Use concise, scannable sections:
• Headline status and key numbers first.
• Bullets and tables for details.
• Clear “Next steps” or “Action items” sections.
• Always base numbers on Asana data, not guesses.*** End Patch