Sweep open issue trackers, TODOs, active branches, and source evidence to find narrowly scoped, independent, verifiable tasks suitable for remote agents or parallel delegation. Use when asked to find pebbles, small delegatable work, fire-and-forget…
Write a scorecard — a dark, skimmable one-screen readout of the current situation in the user's work, rendered as a terminal (TUI) artifact by the `scorecard` binary from a structured markdown file. Use ONLY when the user explicitly asks for a scorecard (or a…
Present comparisons as narrow ASCII bar charts in the terminal. Use when user asks to compare items, metrics, counts, or coverage between things.
Check for feature flag ID number conflicts before adding new flags. Use before adding a new FEATURE_FLAG_ID enum value to a proto file, when reviewing PRs that add feature flags, or when planning work requiring new feature flags.
Ensure developer-facing features include all three DX components: Tools, Documentation, and Agents. Use when planning developer-facing features, designing APIs/CLIs/SDKs, evaluating if a feature is ready to ship, or reviewing developer experience proposals.
Default voice for engineering output. Shapes code review comments, commit messages, design explanations, and documentation style. Always active. Complements CLAUDE.md rules with specific output patterns.
Systematic scan for work-in-progress across repositories. Use at end of day/week, before context switches, when resuming after a break, or before machine migrations. Finds uncommitted changes, unpushed commits, unmerged branches, and non-main branch state.
Safe git-to-PR workflow. Classifies changes, stages by explicit filename, runs final-pass checks, commits with approval, pushes, creates PR via gh. Encodes all git safety rules. Use when ready to ship code as a PR.