standup

Aggregates read-only team status from git, learnings, manifests, and optional backlog state.

Updated Feb 20, 2026

Search Tags:#git #blockers #backlog #learnings #standup #team #status-sync

Ready to run

npx skills add https://github.com/supertyrelle/pelley --skill standup-supertyrelle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/supertyrelle/pelley/tree/main/skills/standup
Command: npx skills add https://github.com/supertyrelle/pelley --skill standup-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a fast, read-only team status sync so you can understand current work, blockers, and learning health without launching agents or writing files.

Core Features & Use Cases

Team snapshot: Reads the team manifest, recent git activity, and member learnings to build a current board.
Backlog awareness: Optionally checks beads backlog state when available to surface ready, in-progress, blocked, and epic progress.
Learning health: Highlights stale, bloated, or inactive learnings so you know when a retro or cleanup may be needed.
Use case: Use it at the start of a work session, after a break, or before planning to quickly reorient on what is happening and what to do next.

Quick Start

Use the standup skill to summarize the team’s current status, blockers, learning health, and suggested next actions for the given focus area.

Frequently Asked Questions about standup

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

FAQPage Schema

How do I get a quick team status sync from git activity and backlog state?▼

Team status sync aggregates recent git commits, member learnings, and optional backlog state from a team manifest to produce a read-only snapshot of current work, blockers, and learning health.

Can I check learning health and identify stale or bloated member learnings before a sprint planning session?▼

Learning health assessment scans per-member learning files to highlight stale, bloated, or inactive learnings, helping you determine when a retro or cleanup is needed before sprint planning.

Does this standup status sync require a team.yaml file to discover team members and ownership?▼

Yes, team.yaml discovery is required to map the team manifest and scan per-member ownership before generating the read-only status board without agent dispatch or file writes.

What is the best way to reorient on project blockers and work progress after a break?▼

Use a read-only status sync to aggregate recent git activity and backlog state, providing a fast snapshot of current work, blockers, and suggested next actions for post-break reorientation.

Are there limitations to using a read-only status sync for file-based team workflows?▼

This approach is limited to read-only aggregation and does not dispatch agents or write files, meaning it cannot modify backlog state or push updates to team members directly.