claude-skills

Record architecture decisions only when they clear three gates (hard to reverse, surprising without context, a real trade-off), in the repo's own ADR convention or a minimal docs/adr/ default.

1 skill

Transcribe a cleared wayfinder design document into increments on squadra's board; it never designs. Validates the document (DESIGN-FORMAT checks 6–15), reads squadra's board, reconciles the two and writes the plan's withdrawals and queues through `squadra board`; `--dry-run` prints the plan instead.

1 skill

Build and sharpen a repo's domain language: challenge and sharpen terms, write GLOSSARY.md inline with Eric Evans (board-eric) reviewing every write, and keep a settled-term record so closed naming debates stay closed.

1 skill

Stress-test a plan, decision, or idea with a round-based interview: numbered questions with a recommended answer each, facts looked up rather than asked, and a confirmation gate. Never writes code.

1 skill

Compact the current session into a handoff a fresh agent session can pick up: structured by a template (bundled, or the effort's own), pointing at the ledger and other artifacts instead of copying them, secrets redacted, and written to a git-ignored handoffs/ beside the ledger.

1 skill

Scaffold a personal, git-excluded local backlog (BACKLOG.local.md) in the current repo, and wire the maintenance convention into CLAUDE.local.md.

1 skill

Build a throwaway prototype (a clickable logic demo or radically different UI variants) to settle one design question that talking can't. Hands it over and waits: the verdict is always the user's, and it never builds the real thing.

1 skill

Chart the way to one destination too big for a single session: a committed map of tickets resolved one per session with grilling and domain-modeling, published as a design document of increments. Writes only the map and the design document; never builds.

1 skill