triage-standup

Verifies genealogy team standup updates against the GitHub repo and produces triaged lists.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill triage-standup-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-standup
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/triage-standup
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill triage-standup-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Standup updates from a ~21-person genealogy team contain claims that are routinely wrong in both directions, and buried among them are findings that exist nowhere but chat. This Skill verifies every claim against the actual repository before repeating it, then delivers a short triaged read so the lead can act on what matters. ## Core Features & Use Cases - Roll Call: Checks posted updates against the team roster and reports who did not report, handling name variants and stale-roster edge cases. - Claim Verification: Cross-checks every reported claim against PRs, branches, issues, CI workflows, and commit history, citing file:line or command output as evidence. - Four Triaged Lists: Produces standup topics, proposed Backlog tasks tagged by owner (lead/junior-genealogist/junior-developer), problematic PRs, and per-person replies, then files approved tasks as GitHub issues. - Daily Summary File: Writes a structured YYYY-MM-DD.md summary with corrections, still_open items, and predictions to build institutional memory. - Use Case: Paste a wall of standup updates with no instruction and receive a roll call, verified findings, and an approval-ready task table without any work being started. ## Quick Start Triage these pasted standup updates from the genealogy team and tell me what needs my attention.

Frequently Asked Questions about triage-standup

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

FAQPage Schema
How do I triage team standup updates with AI?▼

Paste the standup updates and the Skill runs a roll call against the roster, verifies each claim against the repo using git and gh commands, then returns four lists: standup topics, proposed Backlog tasks, problematic PRs, and individual replies.

How does the Skill verify standup claims against GitHub?▼

It fetches open PRs and issues with the gh CLI, diffs branches against main, checks merge reachability, inspects commit logs, and runs cheap test suites. Every repeated claim is either cited with evidence like file:line or labeled reported-but-unverified.

Can this triage skill file GitHub issues automatically?▼

It files issues only after the lead approves the proposed task list, using gh issue create with owner labels like developer or genealogist. Lead-tagged rows file with needs-decision and no assignee, and everything lands in Backlog, never Ready.

When should I not use the genealogy triage-standup skill?▼

Do not use it for the three-person book-to-tree team (Wilson, Nnanna, Praise), which has its own triage skill with a different output shape. It also never starts the work it proposes — it only reports and files.

Why does the roll call report the wrong people as missing?▼

Usually because the roster is stale or someone posted under a name variant like Cia for collins. Being mentioned in another person's update also does not count as reporting; only authored updates are matched.