Tracking Sweep
Portfolio-wide drift sweep across Jira, beads, and GitHub PRs — flags status drift, orphan work, parent-moved beads, and stale items. Read-only; use for a "where is everything" reconciliation, unlike /landscape's passive snapshot.
Install
npx skills add flurdy/agent-skills --skill tracking-sweepgit clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/tracking-sweep ~/.claude/skills/tracking-sweepPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tracking Sweep — Portfolio Drift Reconciliation Cross-reference your **assigned Jira tickets**, **beads**, and **GitHub PRs** to flag drift across the portfolio. Read-only. Recommendations only — never auto-posts comments, never moves Jira status, never closes beads. ## Relationship to other tools - **`/landscape`** is passive display: lists everything in three sections, side-by-side. Doesn't cross-reference. - **`tracking-auditor`** (agent) is per-branch depth: "does THIS branch's diff match its ticket?" Used as a PR-boundary gate. - **`/tracking-sweep`** (this skill) is portfolio breadth: "across everything in flight, where's the drift?" Used ad-hoc. If a single branch looks suspicious during the sweep, recommend invoking `tracking-auditor` for that branch — don't replicate its logic. ## Usage ```bash /tracking-sweep # Full sweep /tracking-sweep quick # Skip stale-beads + PR-detail fetches (faster) ``` ## Output A drift report. Items that match across all three systems are NOT listed — only deviations. If there's no drift, the report is short. That's the point. ## Procedure Run sections 1–3 in parallel (independent data fetches). Sections 4+ are sequential cross-referencing. ### 1. Fetch Jira tickets Tickets assigned to current user, not Done. Include the sprint custom field (`customfield_10020`) — the table both displays it and orders by it:
Details
- Skill name
tracking-sweep- Repository
- flurdy/agent-skills
- Path
skills/tracking-sweep/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Tracking Sweep skill do?
Portfolio-wide drift sweep across Jira, beads, and GitHub PRs — flags status drift, orphan work, parent-moved beads, and stale items. Read-only; use for a "where is everything" reconciliation, unlike /landscape's passive snapshot.
How do I install the Tracking Sweep skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill tracking-sweep. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tracking Sweep popular?
It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Architect
9flurdy/agent-skills
Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Backlog Groom
9flurdy/agent-skills
Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.
Watch PR Feedback
9flurdy/agent-skills
Watch the user's open GitHub PRs for normalized feedback, validate each new or edited actionable item once, and render a bounded decision queue. Read-only by default; attended mode pauses only when the queue needs acknowledgment.
Start Ticket
9flurdy/agent-skills
Initialize work on a Jira ticket. Creates a new branch with conventional commit prefix based on the ticket type. Use when starting work on a new ticket.
Watch Prs
9flurdy/agent-skills
Start a recurring PR status dashboard — runs /pr-status on an adaptive cadence (fast when CI is in flight, backing off when settled) until end of day. Unattended: renders tables and suggested next actions, never prompts or blocks.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.