triage-retros

Move open actions from untriaged retros into the Action Register and update frontmatter.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Rwb3n/callsheet --skill triage-retros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-retros
Source: https://github.com/Rwb3n/callsheet/tree/main/.claude/skills/triage-retros
Command: npx skills add https://github.com/Rwb3n/callsheet --skill triage-retros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage retro action items by moving open actions from untriaged retros into the running register and marking retros as triaged. This ensures accountability and preserves an audit trail.

Core Features & Use Cases

  • Scan untriaged retros: identify retros with triaged: false and gather their open actions.
  • Forward and close actions: move selected items to 4-work-management/open-actions.md and mark completed ones as done, updating retro frontmatter accordingly.
  • Maintain retro lifecycle: set triaged: true on retros with all actions forwarded, and status: complete when all actions are done.
  • Use Case: After a sprint retrospective, triage items to keep the running queue up to date and prevent stale work.

Quick Start

Review untriaged retros, forward selected actions to the open-actions.md register, and update retro frontmatter accordingly.

Frequently Asked Questions about triage-retros

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage retrospective action items to keep an audit trail?

Triage retros by scanning untriaged retro files to gather open actions, forwarding selected items to an open-actions.md register, and updating retro frontmatter flags to preserve an audit trail. User confirmation is required to forward or close each action.

What is the best way to manage open actions from sprint retros?

Managing open actions involves enforcing a strict Action Register format, moving items from untriaged retros into a running queue, and marking retros as triaged to prevent stale work after a sprint retrospective completes.

How does triaging retros update frontmatter flags?

Triaging retros updates frontmatter by setting triaged to true once all open actions are forwarded to the register, and status to complete when all actions are done, ensuring traceability across retro files.

Do I need a specific open-actions.md format to triage retros?

Yes, you need a strict open-actions.md format to triage retros. The process enforces this specific Action Register structure to ensure traceability and auditability when moving items from untriaged retros into the running queue.

Can I automatically forward all retrospective action items without confirmation?

No, you cannot automatically forward all items without confirmation. The triage process operates across retro files requiring explicit user confirmation to forward or close actions and update frontmatter flags accordingly.