standup

Generate verified standup reports for hierarchical Claude Code session trees.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill standup-tuvens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/tuvens/phased-development/tree/main/skills/standup
Command: npx skills add https://github.com/tuvens/phased-development --skill standup-tuvens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stale or fabricated status reporting by turning a subtree of Claude Code sessions into a verified standup snapshot with evidence-backed liveness and state.

Core Features & Use Cases

  • Live-first status checks: Confirms whether subordinate sessions are working, idle, blocked, finished, or unreachable.
  • Ground-truth fallback: Uses state files, git evidence, and registry resolution when live replies do not arrive.
  • Tree rollups: Renders leadership, phase, epic, and sprint subtrees as a clean indented status report.
  • Use case: A lead can quickly inspect a long-running project and see which sessions are active, stale, completed, or unresolved before making the next orchestration decision.

Quick Start

Ask the assistant to run a standup for the current session tree and return a verified indented status report with evidence tags.

Frequently Asked Questions about standup

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

FAQPage Schema
How do I generate verified status reports for hierarchical Claude Code session trees?

Standup reports verify session health by applying live liveness checks and git evidence fallbacks to hierarchical Claude Code session trees, rendering a clean indented status summary with mandatory evidence tags.

What is the best way to detect stale runners and verify partial results in Claude Code orchestration?

Detect stale runners by applying live round-trips to subordinate Claude Code sessions, resolving partial results through explicit state-file and git backstops when live replies do not arrive.

How does size-weighted percentage rollup work for sprint and epic status summaries?

Size-weighted percentage rollups aggregate subordinate session statuses by relative size, rendering leadership, phase, epic, and sprint subtrees into a clean indented status report for orchestration decisions.

Does standup reporting work without live session round-trips?

Standup reporting works without live round-trips by using ground-truth fallbacks, relying on explicit state files, git evidence, and registry resolution to verify liveness and state when live replies do not arrive.

When do I need legacy-hash resolution for Claude Code session liveness checks?

Legacy-hash resolution is needed when verifying standup reports for hierarchical Claude Code session trees where state files or git backstops contain unresolved hashes from prior orchestration runs.