setup-dream-team
Skill2 starsChanged 19 days agoMITView on GitHub
Marks the user's own clone with a git config key, checks the project against the dream-team flow, applies fixes that change no code after one OK, commits its doc edits and files one maintenance issue for the other failing checks; in an upstream clone it only keeps CLAUDE.local.md out of git. Use when the user asks to set up, audit or align a project with the dream-team flow, or to mark a clone as their own. Not for working an issue (use build-issue) or closing a milestone (use milestone-close).
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-teamSkill
- assemble-metaSkill
- brainstormSkill
- build-issueSkill
- cut-milestonesSkill
- frictionSkill
- milestone-closeSkill
- qa-reviewSkill
- review-benchSkill
- scope-commitSkill
- scope-issueSkill
- scope-mrSkill
- scope-specSkill
- ship-itSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Every open issue in an open milestone has exactly one kind label: bug, feature, maintenance, performance, research or meta.
- Distinctive: line 116
Ask whether the repo is the user's own project or an upstream project.
- Very specific: line 122
Read the project CLAUDE.md or AGENTS.md, the contributor doc, the ROADMAP and the specs folder, at the paths <base …
- Very specific: line 124
Read the tracker's milestones, labels, open issues and every issue with a type:: label through the host's tooling skill.
- Distinctive: line 126
Run every check. Record pass or fail, with the evidence: issue numbers, file and line.
- Distinctive: line 128
All checks pass → say the project is aligned and stop.
- Distinctive: line 129
No direct fix applies → go to step 13.
- Distinctive: line 134
Ask for one OK on the draft.
- Distinctive: line 141
Create the missing labels before any swap.
- Very specific: line 142
Delete a type:: label only after a fresh query shows no issue, open or closed, carries it.
- Distinctive: line 144
No failing check is left for the maintenance issue → report the fixes and any commit, and stop.
- Distinctive: line 146
Ask which milestone takes the maintenance issue, suggesting one.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
setup-dream-team
Bringing a project into line is a program, not a change. This skill audits, makes the
Direct fixes below after one confirm, commits its doc edits and files one issue for the rest.
It changes no code; the filed issue goes through build-issue. It marks an own clone with the
dream-team.own key; in an upstream clone it only adds CLAUDE.local.md to the git exclude file.
Checks
- At least one open milestone is numbered
M<n>, orYY.MMfor a version milestone (v<major>.<minor>in a SemVer repo past 1.0) → each open milestone:- is numbered in one of those forms.
- has a measurable exit criterion in its tracker description.
- lists
Exit:,Gate:andDepends on:as bold bullets in its description.
- The project
CLAUDE.mdsaysVersion milestones release in flow mode.→ a version milestone'sExit:naming its due date is its exit criterion. - A ROADMAP exists, two or more
M<n>milestones are open, or aDepends on:names an openM<n>milestone → each openM<n>milestone has a matching ROADMAP row. - Each ROADMAP row is a tracker milestone, or has status
planned, no#and no tracker milestone. - A ROADMAP with a dependency graph or a
plannedrow → the graph has one node perM<n>orplannedrow and one edge per row'sDepends on:entry. - A milestone gated on field evidence has one open
Evidence:issue. - Every open issue in an open milestone has exactly one kind label:
bug,feature,maintenance,performance,researchormeta. - The tracker has an
area::label → every open non-Meta:issue in an open milestone has anarea::label. - An open issue in a milestone carries
workflow::futureexactly when its milestone has an open dependency. - A
Meta:issue has noarea::label, and a milestone only when every open child is in it. - An issue with an open blocker ends with one
Blocked by #<n>line per blocker. - The specs folder holds only specs the code still follows; every other spec carries a
Superseded byline. - A component table, if the contributor doc has one, matches the code.
- A component table cell says only what the component's name and path don't.
- The repo has an architecture diagram → it matches the code.
- The tracker has every label in Label colours except
area::*. - The tracker has no
type::label. - The project
CLAUDE.mdcarries the meaning of every rule in Project rules below. - A CHANGELOG's header links the Keep a Changelog version it follows.
Project rules
The project CLAUDE.md carries these, in its own words:
- A project with an architecture diagram: it changes in the same MR as a component or pipeline change.
- Detail the code doesn't show goes in the commit, spec or a topic doc, never in module docs.
- A fact the code and paths don't show has one reference doc, updated in the MR that changes it.
- A project with a ROADMAP: its status changes only at milestone close.
- A project with floors: they rise in the feature MR that earns them.
- A project with a CHANGELOG: each entry is one plain sentence on a notable change, with no rationale.
- A CHANGELOG entry has no bold except a
**Breaking:**or**Upgrade note:**prefix. - A project with an open
M<n>,YY.MM(version) orv<major>.<minor>(SemVer past 1.0) milestone: a new milestone takes only one of these forms that an open milestone already uses. - A project with open
M<n>milestones: a split takes the next freeM<n>, never a letter. - A project whose version milestones release at their due date: the line
Version milestones release in flow mode., verbatim. - A project with a contributor doc: its path is named.
Label colours
Values from GitLab's label-picker palette, except wontfix, which takes GitHub's default. Setup
sets a colour only on a label it creates.
| Label | Colour | Description |
bug | #D9534F | |
feature | #44AD8E | |
maintenance | #5BC0DE | |
performance | #AD4363 | Throughput, CPU, memory or latency work, measured before and after |
meta | #8E44AD | A Meta: checklist of child issues |
research | #F0AD4E | Research with questions; a findings comment and follow-up issues, no code |
wontfix | #FFFFFF | This will not be worked on |
area::* | #428BCA | |
workflow::blocked | #34495E | |
workflow::future | #7F8C8D | |
workflow::needs-brainstorm | #D1D100 |
Direct fixes
CLAUDE.mdlacks a project rule → write it in the file's own words, merged into its existing structure.- The project has neither
CLAUDE.mdnorAGENTS.md→ createCLAUDE.mdwith the project rules. - The tracker lacks a label from Label colours → create it with its colour and description.
- The tracker has a
type::<kind>label,<kind>a kind in Label colours → swap it for<kind>on each issue that carries it, then delete thetype::label. - Any other
type::label → an item in the maintenance issue. - A milestone fails the bold-bullet check, but its description has its exit criterion, gate and
dependencies → rewrite them as
Exit:,Gate:andDepends on:bold bullets. - An issue lacks the
Blocked by #<n>line for an open blocker → append one line per missing blocker. - An open issue in a milestone carries
workflow::futurewithout an open milestone dependency, or lacks it with one → add or remove the label. - Any other failing check whose fix changes no code and the draft can state, tracker edits and repo docs included → a direct fix, shown in the step 8 draft.
- A failing check that needs a code change, or a decision the draft cannot state such as a missing exit criterion → an item in the maintenance issue (step 14).
Steps
- Ask whether the repo is the user's own project or an upstream project; a fork counts as own.
- Upstream and
git check-ignore CLAUDE.local.mdprints nothing → addCLAUDE.local.mdto the filegit rev-parse --git-path info/excludeprints. - Upstream → write no marker, report whether
CLAUDE.local.mdwas added to or already in the exclude file, and stop; change nothing else in the repo or its tracker. - Own → run
git config --local dream-team.own true, then go on to step 2.
- Upstream and
- Read the project
CLAUDE.mdorAGENTS.md, the contributor doc, the ROADMAP and the specs folder, at the paths<base directory>/../../references/repo-conventions.mdresolves. - Read the tracker's milestones, labels, open issues and every issue with a
type::label through the host's tooling skill. - Run every check. Record pass or fail, with the evidence: issue numbers, file and line.
- Report one line per check to the user before changing or filing anything.
- All checks pass → say the project is aligned and stop.
- No direct fix applies → go to step 13.
- Show one combined draft of every direct fix: the
CLAUDE.mdand repo-doc diffs, the labels to create, each issue'stype::to flat kind swap, thetype::labels to delete, the labels and milestone to change per issue, each milestone title, milestone description and issue body before and after, and any issue or milestone to create. - Ask for one OK on the draft; a direct fix the user declines becomes an item in the maintenance issue.
- Any approved
CLAUDE.mdor repo-doc edit → write them and commit only those files, in one commit perscope-commit, on the current branch, not pushed.- On
mainormasterwith a spec or design doc among those edits → rungit checkout -b <topic>first and name the branch in the report.
- On
- Make the tracker changes through the host's tooling skill.
- Create the missing labels before any swap.
- Delete a
type::label only after a fresh query shows no issue, open or closed, carries it. - A swap fails → keep that
type::label and report the issue.
- No failing check is left for the maintenance issue → report the fixes and any commit, and stop.
- Ask which milestone takes the maintenance issue, suggesting one.
- File one
maintenanceissue perscope-issue, in that milestone, with one item per remaining failing check. - A check that fails on many items → one item listing them.
- Report the fixes, any commit and the filed issue. It is worked through
build-issue.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

