Meeting To Backlog Brief

Status: Experimental

This proposed skill helps the team turn meeting notes, planning conversations, and stakeholder feedback into safe, backlog-ready summaries.

Purpose

Important work often enters through meetings before it becomes clean requirements. This skill gives agents a consistent way to separate decisions, action items, risks, open questions, and PBI candidates while avoiding raw transcript sprawl.

When To Use

• "Turn these meeting notes into action items and PBI candidates."
• "Summarize this stakeholder discussion for backlog grooming."
• "Extract decisions, risks, and open questions from this planning note."

Requirements

• Meeting notes, transcript excerpts, chat discussion, decision log, or stakeholder feedback.
• Target product area or planning context when available.
• Explicit approval before writing to Azure DevOps, Linear, SharePoint, email, or another shared system.

Install

Install only for intentional trial while this skill is Experimental:

scripts/install-skill.sh meeting-to-backlog-brief copilot /path/to/project-repo
scripts/install-skill.sh meeting-to-backlog-brief codex
scripts/install-skill.sh meeting-to-backlog-brief cursor /path/to/project-repo

Typical Output

• Decision summary.
• Action items with owner and due date when known.
• Risks and open questions.
• Backlog candidate list with scope and acceptance signals.
• Recommended next step for ticketing or follow-up.

Testing

• Dry-run with sanitized meeting notes that include decisions, unresolved questions, and ambiguous owners.
• Confirm the skill does not preserve raw transcript text unnecessarily.
• Confirm it asks before creating external tickets or updating shared documents.

Example Prompt

Use the meeting-to-backlog skill to turn these notes into decisions, action items, risks, and PBI candidates for grooming.