vibe-sdlc-status

Aggregate per-agent status files into a unified STATUS.md document.

6|3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-sdlc-status
Source: https://github.com/robin-li/vibe-money-book/tree/main/.claude/skills/vibe-sdlc-status
Command: npx skills add https://github.com/robin-li/vibe-money-book --skill vibe-sdlc-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a single-entry, reproducible way to gather and present the runtime status of multiple SDLC agents and the overall project health by reading per-agent status files and repository metadata, avoiding fragmented or noisy status reporting.

Core Features & Use Cases

  • Agent state aggregation: Read A-*.md files under /docs/status/ and synthesize a consolidated /docs/status/STATUS.md with timestamps, agent tables, notices, and recent activity.
  • Fallback discovery: When per-agent files are absent, infer current work from GitHub issues, PRs, and milestones to populate the status snapshot.
  • Version-control-safe snapshotting: Support writing a snapshot branch dev/main-agent with an explicit reset-and-force-push contract and enforce display rules that avoid misleading ahead/behind warnings.
  • Operational alerts: Detect stale agent files, red/blocked states, and blocking chains and surface human-actionable reminders.

Quick Start

Request a consolidated project status by asking the agent to read /docs/status/, aggregate A-*.md and repository issues/PRs, and write the result to /docs/status/STATUS.md.

Frequently Asked Questions about vibe-sdlc-status

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

FAQPage Schema
How do I consolidate multiple agent status files into a single project status report?

You can consolidate agent status files by reading individual A-*.md files from the /docs/status/ directory and synthesizing them into a unified /docs/status/STATUS.md with timestamps, agent tables, and recent activity.

What is the best way to track SDLC agent status when individual status files are missing?

When per-agent status files are absent, you can infer current work from GitHub issues, PRs, and milestones to populate the status snapshot automatically.

How do I safely snapshot agent status updates to a dev branch without misleading ahead or behind warnings?

You can safely snapshot status updates by using an explicit reset-and-force-push contract to the dev/main-agent branch, enforcing display rules that prevent misleading ahead or behind warnings.

Can I detect blocked or stale agent states across a software development lifecycle automatically?

Yes, the aggregation process detects stale agent files, red or blocked states, and blocking chains to surface human-actionable operational alerts and reminders.

Does this status aggregation approach require a specific repository directory structure?

Yes, it applies to repositories that maintain a /docs/status/ directory with per-agent A-*.md files, or where agent status must be inferred from GitHub issues and milestones.

How do I manage version control when writing automated SDLC status reports?

You manage version control by reading and writing /docs/status/ files while following the configured version-control mode specified in the project's CLAUDE.md file.