Skip to content

fix: move advisory board personas into repo #399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CalebisGross merged 1 commit into from
Apr 12, 2026
Merged

fix: move advisory board personas into repo #399

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 2 additions & 11 deletions .claude/rules/advisory-board.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,5 @@
# Advisory Board Review

When making significant decisions — architecture choices, experiment design, "should we do X or Y" moments, or planning multi-step work — consult the Advisory Board framework at `~/.claude/projects/-home-hubcaps-Projects-mem/memory/persona_advisory_board.md`.
When making significant decisions — architecture choices, experiment design, planning multi-step work, choosing between approaches, or deciding whether to ship or keep iterating — invoke the `advisory-board` skill.

Run the decision through the 19 lenses. You don't need to list all 19 every time — pick the 3-4 most relevant voices for the specific decision and present the tensions. Caleb is the tiebreaker.

Triggers:
- "what should we do"
- "which approach"
- "let's plan"
- "let's brainstorm"
- Choosing between two architectures, datasets, or approaches
- Deciding whether to ship or keep iterating
- Any decision that commits GPU time or DO droplet credits
Also invoke when GPU time or DO droplet credits are at stake.
Loading