bootstrap-working-agreements

/bootstrap-working-agreements — One-shot project setup

The goal: in one pass on a fresh (or fresh-to-tooling) repo, lay down everything that makes future Claude sessions productive — GitHub Project, working agreements, roadmap, CLAUDE.md hub + spokes — with project-specific values substituted in (not generic placeholders left for the user to fill in later).

This skill proposes and waits for confirmation before writing anything. Almost every value is project-specific.

---

Step 0 — Working tree check

This skill writes multiple files (.claude/rules/working-agreements.md, root CLAUDE.md, optional spokes) and calls into github-project-setup (which writes more). Before any changes, give the user a clean baseline to git diff against if something goes wrong:

git status --short

If the output is non-empty, halt and report:

Uncommitted changes in <N> files:

<git status --short output, truncated to 10 lines if longer>

This skill writes several new and modified files across the repo. If anything goes wrong you'll want a clean baseline. Commit/stash first, or continue anyway?

Wait for explicit "continue" before proceeding. Don't proceed silently.

If git status --short errors (not a git repo), warn the user and ask whether to proceed without a revert baseline. Recommend git init first.

---

Step 0.5 — Check .gitignore for .claude/ patterns

This skill commits three things under .claude/: durable rules in .claude/rules/, the plugin-enablement file .claude/settings.json (Step 6.5), and — via github-project-setup — .claude/gh-project.json. A directory-level ignore (.claude/ with a trailing slash) silently excludes all of them — git can't re-include children of a fully-excluded directory, so they won't show up in git status until someone notices.

grep -nE '^\.claude/?$' .gitignore 2>/dev/null

If a .claude/ line is found, propose the carve-out fix — replace it with:

.claude/*
!.claude/rules/
!.claude/settings.json
!.claude/gh-project.json