Files

T

jpmschweitzerandClaude Opus 4.6 bc226d8baf chore(db): move db/connectors/ to tooling/db/ (#274 )

Consolidates all connector scripts under tooling/ per project
structure conventions. Symlink at db/connectors → tooling/db/
preserves backwards compatibility (remove after Sprint 22).

Updated references in CLAUDE.md, Makefile, DEVOPS.md, all skill
files, agent files, rules, schema comments, and Sprint 21
briefings. Python scripts updated with correct SCHEMA_PATH
(now relative to WORKTREE_ROOT/db/schema.sql).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-27 11:08:00 +01:00

2.9 KiB

Raw Blame History

name, description, user-invocable, allowed-tools

name	description	user-invocable	allowed-tools
sprint-status	Sprint health check and cleanup sweep. Lists all tickets in the active sprint grouped by status, detects bookkeeping issues (stale tickets, orphan PRs, done-but-open PRs, unassigned work), and shows open work by team. Use when checking sprint progress, before sprint close, or when housekeeping feels off. Triggers on "sprint status", "cleanup sweep", "what's open", "sprint health".	true	Task, Read, Grep, Glob

Sprint Status

Delegate this entire skill to a subagent (general-purpose, model: haiku).

When this skill is invoked, spawn a subagent using the Task tool:

Task(
  subagent_type: "general-purpose",
  model: "haiku",
  prompt: "Run /sprint-status. Read the skill at
    .claude/skills/sprint-status/SKILL.md for the full workflow
    (below the --- separator), then execute it.",
  description: "Sprint status report"
)

Present the subagent's output to the user verbatim. Do NOT run the workflow yourself.

The remainder of this file is the subagent's reference for executing the workflow.

Step 1 — Gather data

Run these two commands in parallel:

tooling/db/sprint sweep

tea pr list --login schweitz --repo jpmschweitzer/settled-reach --state open --output simple

The sweep command returns JSON with:

sprint — id, name, goal
progress — total, done, pct
by_status — tickets grouped into done, review, in_progress, blocked, backlog
by_team — per-team counts
issues — bookkeeping problems with suggested fix commands

The tea pr list returns open PRs as #N title lines.

Step 2 — Cross-reference PRs with tickets

Parse PR head branches from the tea pr list output. Known team branches: server, client, copy, audio, visual, ci.

Detect additional issues:

done_team_open_pr: A team's tickets are all done but an open PR still exists for that team branch.
orphan_pr: An open PR exists on a branch that has no tickets in the active sprint.

Add these to the issues list from step 1.

Step 3 — Format output

Read references/output-template.md for the exact format spec.

Render the report using data from steps 1-2. Key rules:

Sections ordered: Completed, In Review, In Progress, Blocked, Backlog
Sort tickets within sections by team then ticket ID
Empty sections: show header with "(0)" and "(none)" — no empty table
Bookkeeping Issues: two-column table (Issue, Fix)
Open Work by Team: summary table at the bottom
Issue type labels: stale_backlog → "Stale backlog", unassigned_in_progress → "Unassigned in_progress", assigned_but_done → "Assigned but done", done_team_open_pr → "Done team with open PR", orphan_pr → "Orphan PR"

Step 4 — Suggest actions

After the formatted report, if there are bookkeeping issues, add a "Suggested fixes" section with the fix command for each issue. Group by issue type for readability.

2.9 KiB Raw Blame History