Huddle
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.