Internal: workflow skills

[kaitlynmichael]

What this is

A personal daily status loop for juggling parallel docs work — three Claude Code skills plus a private markdown hub they read and maintain:

• /standup — ranks "what to do next" from your hub + live signals (Jira, GitHub, Calendar, Gmail, Slack). Read-only.
• /startwork <project> — loads one task: reads its plan, checks out the branch, loads product context (/rs, /k8s, /ff). Read-only on the hub.
• /checkpoint — the only writer: records progress into the plan + OVERVIEW.md and reconciles Jira drift.

/standup → /startwork → work → /checkpoint. All three take --fast to skip live fetches.

How to get them

1. Get the skills. Once this merges, just git pull on main — they live in .claude/skills/ and auto-register, no config. To try them before merge: git fetch && git checkout share-status-workflow-skills.

2. Create your private hub from the templates (one time, ~5 min):

   mkdir -p ~/claude-overview/plans
   cp .claude/skills/_shared/status-workflow/OVERVIEW.template.md ~/claude-overview/OVERVIEW.md
   cp .claude/skills/_shared/status-workflow/plans/example-project.md ~/claude-overview/plans/<your-first-project>.md
   

   Fill in OVERVIEW.md and one plan file. Start with a single project. Keep the hub out of git — it's your personal working state.

3. Connect live integrations (optional — /standup's signals degrade gracefully if absent): Atlassian MCP (Jira), gh auth login (GitHub), Calendar/Gmail/Slack MCP.

Full setup, design notes, and the hub layout are in _shared/status-workflow/README.md.

One naming note

This repo already has a /pickup skill (thaw a parked PR, pairs with /park) — unrelated. The standup companion is named /startwork here to avoid the collision; natural-language "pick up X" / "work on X" still triggers it.

Note

Low Risk
Documentation and Claude skill definitions only; no runtime or published docs behavior changes.

Overview
Adds a daily status loop for parallel docs work: a private ~/claude-overview/ hub (markdown templates) plus three Claude Code skills that read and update it.

/standup ranks what to do next from the hub and optional live signals (Jira, gh, Calendar, Gmail, Slack); read-only. /startwork loads one project—plan, branch checkout in ~/repos/docs, and product context (/rs, /k8s, /ff); hub stays read-only. /checkpoint is the sole writer: updates the matching plan and OVERVIEW.md, reconciles DOC-/RED- Jira drift, and refreshes a GitHub PR/issue snapshot. All three support --fast to skip external fetches.

Shared docs under _shared/status-workflow/ cover setup, naming (startwork vs existing /pickup for parked PRs), and split read/write design.

^{Reviewed by Cursor Bugbot for commit 8a6e100. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8a6e100. Configure here.}

[cursor]

Archived plans matched on checkpoint

Medium Severity

/checkpoint resolves the target plan with recursive grep -rl over all of ~/claude-overview/plans/, while /standup explicitly ignores archive/ when reading active plans. A branch or ticket string that appears only under plans/archive/ can be the sole match, so checkpoint may update a retired plan and leave the live project stale.

 

^{Reviewed by Cursor Bugbot for commit 8a6e100. Configure here.}

[cursor]

Resume session id wrong heuristic

Medium Severity

Step 2 equates the current session with the most recently modified .jsonl in the project folder. With multiple Claude sessions in the same repo, another tab’s activity can produce a newer mtime, so the saved claude --resume id may not match this checkpoint thread.

 

^{Reviewed by Cursor Bugbot for commit 8a6e100. Configure here.}

[cursor]

Case-sensitive plan branch grep

Medium Severity

Project detection uses case-sensitive grep -rl for the branch or ticket, unlike /startwork, which uses grep -rli. Lowercase git branch names or ticket fragments may fail to match DOC-/RED- keys in plans, leading to “no match” prompts or missed auto-detection.

 

^{Reviewed by Cursor Bugbot for commit 8a6e100. Configure here.}

[andy-stark-redis]

I'll approve (I'm sure you'll fix the Bugbot stuff).