aped-status

Render an APED pipeline and parallel sprint status dashboard from state.yaml.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-status
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-status
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you quickly understand where your APED pipeline and parallel sprint are right now, without manually checking every worktree or state file.

Core Features & Use Cases

  • Pipeline and sprint status dashboard: Presents an at-a-glance view of completed phases, the active epic, and sprint capacity (parallel limit and review limit).
  • Worktree health and progress: Lists active worktrees for in-progress/review stories, including last commit, dirty count, and test status using the canonical .aped/.last-test-exit cache.
  • Review queue and readiness signals: Shows queued stories, pending Lead check-ins, dispatch-ready stories with dependency resolution, and optionally performs ticket status divergence checks.

Quick Start

Ask for sprint status by running aped-status to display the current APED pipeline dashboard and sprint progress for your project.

Frequently Asked Questions about aped-status

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

FAQPage Schema
How do I check sprint dashboard status for parallel worktrees in Claude Code?

You can view your sprint dashboard status by loading the APED configuration and state.yaml to render worktree health, review queue, and dispatch readiness. It requires an APED-enabled project configuration to function properly.

What is pipeline status reporting for active sprints?

Pipeline status reporting for active sprints is a read-only view that shows completed phases, the active epic, and sprint capacity limits. It aggregates worktree status and review queues into a single dashboard.

How do I monitor worktree health and test status during a sprint?

You monitor worktree health by checking last commit details, dirty file counts, and test status. The dashboard reads this from the canonical .aped/.last-test-exit cache to provide accurate read-only metrics.

Can I check ticket sync divergence and review queue readiness without manual checks?

Yes, you can automatically check ticket sync divergence and review queue readiness. The dashboard identifies queued stories, pending Lead check-ins, and dispatch-ready stories with resolved dependencies from canonical cached data.

Do I need APED configuration files to render a sprint progress dashboard?

Yes, you need APED configuration and state.yaml files to render a sprint progress dashboard. The system enforces an APED-enabled guard, meaning it cannot display pipeline or worktree status without these canonical files.