About huddle
A Claude skill that convenes repo-grounded perspectives from specialists on a topic, then pauses for the user to decide what happens next. It is intended for team-style deliberation without Claude independently advancing the agenda.
Key features
- 01Specialist perspectives on raised topics
- 02Opinions grounded in the repository
- 03User-led decisions and agenda
- 04Huddle notes resumed by date and branch
- 05Records decisions as user-made
Use cases
- 01Reviewing a repository-level proposal
- 02Considering security and architecture concerns
- 03Comparing product and engineering perspectives
- 04Resuming a prior decision discussion
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/huddlein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
CLAUDE.mdinstall.shREADME.md.gitignoreinstall.cmddocs/specs/huddle-config-and-local-mode.mdhuddle-global-roster-rename.mdflow-control.mde2e/run.pyreferences/activation-routing.xmldispatch-table.mdpersona-roster.xmlreferences/personas/amara-trendresearcher.mdbabu-demandreality.mddeepak-techwriter.mdelango-specwriter.mdelanchezian-brainstormer.mddileep-visionary.mdhari-builder.mdharshvardhan-builder.mdmaya-strategist.mdnina-tester.mdsenthil-security.mdkishore-storyteller.mdluca-frontend.mdprabagar-pm.mdshaama-engineer.mdsreyash-solodev.mdsuren-architect.mdsuna-designer.mdDetails
From the project READMEHuddle
Use this skill as the repo's decision huddle.
For any topic raised, Claude surfaces relevant perspectives from a team of specialists (Architecture, Engineering, Security, Product, Design, Testing, Test Architecture, Analysis, Documentation, Strategy, Prioritization, Validation, Vision, Presentation, Narrative, Data, Trend Scanning, Spec Creation) — short, opinionated, grounded in the repo — then stops and waits for the user to decide and move forward.
The user drives. Claude does not make decisions or advance the agenda unilaterally.
Core Rules
- Identify the user with
git config user.name. Use their name throughout. - Identify the repo with
git remote get-url origin(parse owner/repo from URL). Fallback:basename $(git rev-parse --show-toplevel). - Store huddle memory in
~/.config/muthuishere-agent-skills/{reponame}/{branch}/huddle/. - Today's huddle note is
{YYYY-MM-DD}.md. Always resume if it exists. - After presenting perspectives, always stop and ask
{GIT_USER}for their call or next direction. - Never advance to a new topic without the user signalling to move on.
- Record every decision as made by the user, not by a perspective.
Follow the instructions in ./references/workflow.md.