team-contributionlisted

The contribution contract every team support follows. Use when dispatched as an advisor, reviewer or builder by the Product Owner or Tech Lead hat, and when a hat writes a brief or reads a return. Defines the brief, the contribution file, positions and objection kinds, rounds, and the return summaries.
rafaelgarrafiel/team_skills · ★ 0 · AI & Automation · score 72

Install: claude install-skill rafaelgarrafiel/team_skills

# Contribution contract A hat (Product Owner in `team-grill`, Tech Lead in `team-implement`) dispatches supports. Every support writes exactly one file and returns a short summary. The file is the durable record the human can read where the decision is made; the summary is what the hat reads first. Agents never invoke each other: only the hat delegates. ## The brief The hat's prompt carries the task, never the persona (the harness loads the persona). Every brief has: - the artifact under review: a path, or the design tree so far for a grill round - the open frontier (grill), or the ticket and its spec section (build and review) - the paths of `CONTEXT.md` and the ADRs that touch the area, when they exist - the artifact language, from the `## Team` block - the mode: with or without Matt's skills - the round number, and in round 2 only, the sibling supports' `## Positions` - the output path for the contribution file, and this line verbatim: "Call the Skill tool with `team-contribution` and follow it." Round 1 is **blind**: no brief carries a sibling's contribution. Who sees what is the invariant; whether the harness runs supports in parallel or in sequence is not. ## The file Path, by dispatch: | Dispatch | Path | |---|---| | grill round | `.scratch/<feature-slug>/team/grill/<agent-slug>.md`, one `## Round N` section appended per round | | spec review | `.scratch/<feature-slug>/team/spec/<agent-slug>.md` | | ticket-set check | `.scratch/<feature-slug>/team/tickets/<agen