From fieldguides
This skill should be used when checking project status, starting sessions, reviewing activity, or when sitrep, status report, or what's changed are mentioned.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fieldguides:check-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather -> aggregate -> present pattern for comprehensive project status across VCS, PRs, issues, CI.
EXAMPLES.mdreferences/beads.mdreferences/github.mdreferences/graphite.mdreferences/implementation.mdreferences/linear.mdreferences/templates.mdscripts/detect.tsscripts/gatherers/beads-gatherer.tsscripts/gatherers/github-gatherer.tsscripts/gatherers/graphite-gatherer.tsscripts/gatherers/linear-gatherer.tsscripts/lib/time.tsscripts/lib/types.tsscripts/sitrep.tsGather -> aggregate -> present pattern for comprehensive project status across VCS, PRs, issues, CI.
<when_to_use>
NOT for: deep-dive into specific items, real-time monitoring, single-source queries
</when_to_use>
<core_pattern>
Three-stage workflow:
Key principles:
</core_pattern>
Stage 1: Parse Constraints
Extract time from natural language:
-Xh-Xd-1d-12h-7dDefault: 7 days if unspecified.
Stage 2: Gather Data
Run parallel queries for each available source:
Skip unavailable sources gracefully.
Stage 3: Aggregate
Cross-reference and organize:
Stage 4: Present
Format for scanning:
✓ ✗ ⏳ for status)See templates.md for section formats.
<data_sources>
VCS - stack visualization, commit history, working dir state
Code Review - PRs/MRs, CI checks, reviews, comments
Issues - recent updates, metadata, repo relationships
CI/CD - runs, success/failure, timing, errors
Tool-specific: graphite.md, github.md, linear.md, beads.md
</data_sources>
Cross-Referencing:
Stack-Aware Organization:
Filtering:
Relative Timestamps:
= 7 days: "X weeks ago" or absolute
Visual Indicators:
✓ success | ✗ failure | ⏳ pending | ⏸ draft | 🔴 blocker▓▓▓░░ progress (3/5)◇ minor | ◆ moderate | ◈ severeOutput Structure:
=== STATUS REPORT: {repo} ===
Generated: {timestamp}
{Time filter if applicable}
{VCS_SECTION}
{PR_SECTION}
{ISSUE_SECTION}
{CI_SECTION}
⚠️ ATTENTION NEEDED
{blockers and action items}
See templates.md for detailed section templates.
Use scripts/sitrep.ts for automated gathering:
./scripts/sitrep.ts # All sources, 24h default
./scripts/sitrep.ts -t 7d # Last 7 days
./scripts/sitrep.ts -s github # Specific sources
./scripts/sitrep.ts --format=text
Outputs JSON (structured) or text (human-readable). Reduces agent tool calls 80%+.
See implementation.md for script structure and patterns.
Required: VCS tool (git, gt, jj), shell access
Optional (graceful degradation):
Works with ANY available subset.
ALWAYS:
NEVER:
As session starter:
Cross-skill references:
Automation: daily standup, pre-commit hooks, PR creation context
Tool integrations:
Implementation:
Examples:
Formatting:
npx claudepluginhub outfitter-dev/outfitter --plugin fieldguidesCTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
Generates CTO-level project status from git log/status and key docs (README, TODO, CLAUDE.md). Summarizes shipped work, progress, blocks, next steps for standups or 'where are we' queries.
Detects project type, tech stack, AIWG phase status, team config, git activity, blockers, and risks from .aiwg files and repo. Summarizes context and recommends next actions.