Skip to content

Internal: workflow skills - #3692

Merged
kaitlynmichael merged 4 commits into
mainfrom
share-status-workflow-skills
Jul 27, 2026
Merged

Internal: workflow skills#3692
kaitlynmichael merged 4 commits into
mainfrom
share-status-workflow-skills

Conversation

@kaitlynmichael

@kaitlynmichael kaitlynmichael commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

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 agent skill definitions only; no runtime app, auth, or published docs content changes.

Overview
Adds a daily status loop for parallel docs work: three new Claude Code skills under .claude/skills/ plus shared templates and setup docs in _shared/status-workflow/.

/standup (read-only) reads a personal hub at ~/claude-overview/ and optional live signals (Jira, gh, Calendar, Gmail, Slack) to rank what to do next. /startwork loads one project from the hub, checks out the right branch in ~/repos/docs, and invokes product context (/rs, /k8s, /ff) without editing the hub. /checkpoint is the sole writer: it maps the current branch to a plan file, updates plan + OVERVIEW.md, reconciles DOC-/RED- Jira drift, and refreshes a GitHub snapshot block.

All three support --fast to skip external fetches. Docs explain hub seeding from OVERVIEW.template.md and plans/example-project.md, the read/write split, and why the dive-in skill is named /startwork instead of /pickup (existing parked-PR skill).

Reviewed by Cursor Bugbot for commit 2179332. Bugbot is set up for automated code reviews on this repo. Configure here.

@kaitlynmichael kaitlynmichael self-assigned this Jul 22, 2026
@kaitlynmichael kaitlynmichael added the AI-friendliness Features that help AI tools understand and use the doc pages more easily. label Jul 22, 2026
Comment thread .claude/skills/checkpoint/SKILL.md
Comment thread .claude/skills/checkpoint/SKILL.md Outdated
Comment thread .claude/skills/checkpoint/SKILL.md Outdated

@andy-stark-redis andy-stark-redis left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Bugbot flagged that checkpoint's recursive `grep -rl` over plans/
could match an archived plan, while standup skips archive/ — so the
two skills disagreed on scope. Add --exclude-dir=archive so an
archived plan can't shadow the active one.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 5 related items from repository history:

Memory updated at aa00a9c

Address the two remaining Bugbot Mediums on checkpoint/SKILL.md:

- Plan detection: add -i to the grep so it's case-insensitive like
  /startwork, so a lowercase branch name still matches DOC-/RED- keys.
- Resume pointer: prefer $CLAUDE_CODE_SESSION_ID (the exact running
  session id) over the most-recently-modified .jsonl heuristic, which
  could pick another tab's session in the same repo. Keep the mtime
  scan as a documented fallback.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 5 related items from repository history:

Memory updated at c46dae7

Comment thread .claude/skills/standup/SKILL.md Outdated
@github-actions

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 5 related items from repository history:

Memory updated at 2179332

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ 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 2179332. Configure here.


## Operator note — git in the sandbox

`git fetch` / `checkout` / `pull` in `~/repos/docs` and reading `~/claude-overview/` are normal reads/writes within the clone and hub. If a git network op (`fetch`/`pull`) hits a TLS/keyring error in a restricted shell, that's the same environment restriction described in `/standup`'s operator note — retry outside the sandbox. `gh` is typically sandbox-excluded (`sandbox.excludedCommands: ["gh *"]` in `~/.claude/settings.json`), so PR lookups work in-sandbox.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/startwork missing documented --fast flag support

Medium Severity

The PR description states "All three take --fast to skip live fetches," but /startwork's SKILL.md has no ## Arguments section and never mentions --fast. Both /standup and /checkpoint have detailed --fast behavior documented (which steps to skip, what to state in output), while /startwork has step 5 ("Pull live task signals") performing Jira and GitHub network fetches — exactly the kind of slow step --fast is meant to bypass. Without --fast instructions in the skill file, Claude won't know to skip step 5 when a user passes that flag. The README.md also only mentions /standup --fast and /checkpoint --fast, reinforcing the omission.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 2179332. Configure here.

@kaitlynmichael
kaitlynmichael merged commit e170b15 into main Jul 27, 2026
78 checks passed
@kaitlynmichael
kaitlynmichael deleted the share-status-workflow-skills branch July 27, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI-friendliness Features that help AI tools understand and use the doc pages more easily.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants