willackerly

willackerly/rebar

Hook Claude Code

Runs when a session starts on startup and clear, executing cold-start-checks.sh. From willackerly/rebar.

willackerly/rebar

Settings file Claude Code

Agent settings declaring 1 hook event (SessionStart).

willackerly/rebar

Skill Claude CodeCodex

Use when asked about a rebar repo's health, compliance, tier, or contract status — and before claiming any tier, badge, or "green" state in docs or commits. Runs the three status surfaces and reads them without conflating the two maturity vocabularies.

willackerly/rebar

Skill Claude CodeCodex

Use at the start of every session in a REBAR-managed repo, before the first substantive task — and any time you catch yourself working from stale context (post-compaction restart, missing cold-start hook output, QUICKCONTEXT claims that don't match git reality). Runs the session-start ritual that grounds you in…

willackerly/rebar

Skill Claude CodeCodex

Use when you hit a gap, anti-pattern, bug, or missing guidance in rebar's templates, practices, or scripts during real work — or when the user says "file feedback" / "write this up for rebar." Files a durable feedback item instead of editing templates directly.

willackerly/rebar

Skill Claude CodeCodex

Use during multi-repo coordination phases (release days, cross-repo arcs, ratification rounds) when this repo holds a peer inbox/ directory — arms a persistent background watcher so new memo deposits reach you as live notifications instead of sitting unread while a peer waits.

willackerly/rebar

MCP server Claude CodeCodexCursor +2

MCP server "rebar-ask" as configured in willackerly/rebar. Launched with /Users/will/dev/rebar/bin/ask-mcp-server --stdio --repos-dir /Users/will/dev.

willackerly/rebar

Instructions file CodexOpenCode

Instructions for willackerly/rebar, covering agents.md — working on rebar itself, read before coding, core tenets, agent autonomy and session lifecycle.

willackerly/rebar

Agent

Status: active — load-bearing doctrine for multi-subagent fanout Source: feedback/processed/2026-04-28-multi-subagent-fanout-playbook.md Provenance: dapple-sdk, 2026-04-28 — two fanout cycles in one 16hr session, 9 fanned-out worktree branches, all merged with zero conflict resolution; 12–16 hours of sequential work…

willackerly/rebar

Agent

Shared behavioral contract for all subagent invocations. The orchestrating agent should instruct every subagent to read this file before starting work.

willackerly/rebar

Agent

Catalog of available subagent templates. Each entry links to the full template in subagent-prompts/.