Menu
Bidirectional sync between 100days.md and GitHub Projects board — strikethrough Done items, create new cards, backfill Sprint tags
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Start work in an ISOLATED git worktree (the exception path — use only when two envs must be live at once, the work is multi-day and main must stay shippable meanwhile, or it's a throwaway spike). Creates the branch + worktree + venv + frontend build + smoke test + BRANCHES.md entry. For ordinary work, use /new-feature (trunk) instead. Any Kind — captured in Step 3.5. The `--from-cloud` flag instead ADOPTS an existing `origin/claude/*` cloud branch (built on phone/cloud, never compiled): fetch → build the Mac env → run the tests the cloud couldn't → preview the merge against main.
End-of-session ritual — verify, document for humans and robots, commit, close out
Ship a release — bump version, finalise changelog/readme, tag, push, and verify PyPI. The ONLY workflow command that touches public distribution (PyPI, Homebrew, the public changelog, the tag). Evening window on weekdays. Supports --dry-run.
Finish a piece of trunk work on main — runs tests + lint, surfaces human-QA checks, trues docs, adds a changelog line, marks the 100days item done, and commits. No merge (you're already on main). If you're on a branch, it offers to close the branch properly instead.
Archive a merged feature branch — stale marker, detach worktree, update BRANCHES.md (preserves local directory)
Start a piece of work on main (trunk — the DEFAULT path). Loads the plan / 100days item, checks recent history, agrees a plan, and records the task. No branch, no worktree, no env setup. For work that needs an isolated live environment, use /new-branch instead.
| name | sync-board |
| description | Bidirectional sync between 100days.md and GitHub Projects board — strikethrough Done items, create new cards, backfill Sprint tags |
| model | haiku |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | Bash, Read, Edit |
Sync the 100-day launch inventory (docs/private/100days.md) with the GitHub Projects board (Bristlenose Roadmap).
Two modes, selected by argument $0:
/sync-board (no argument) — bidirectional sync: board→doc strikethrough + doc→board new cards + doc→board sprint backfill/sync-board mark-done "Item 1" "Item 2" ... — move specific items to Done on the board and strike through in the doc. Use when you've verified items are complete by reading the codeRun the unified sync script:
cd /Users/cassio/Code/bristlenose
python3 scripts/sync_100days.py
Review the dry-run output with the user. If changes look correct, apply:
python3 scripts/sync_100days.py --apply
Report what changed in each direction:
The remaining arguments after mark-done are item titles (or substrings). Run:
cd /Users/cassio/Code/bristlenose
python3 scripts/sync_100days.py mark-done "Item title 1" "Item title 2"
Review the dry-run output. If correct, apply:
python3 scripts/sync_100days.py mark-done --apply "Item title 1" "Item title 2"
Report what was moved to Done and what was struck through. Items already Done on the board are skipped (but still struck through in the doc if not already).
PVT_kwHOAEYXlM4BORbYPVTSSF_lAHOAEYXlM4BORbYzg9Becgdocs/private/ (gitignored — contains names and value judgements)[S1]–[S6] before the bold titlescripts/sync_100days.py (tests: tests/test_sync_100days.py)sync-100days-status.py, sync-100days-new.py, sync-100days-mark-done.py) are deprecated — do not use