ask-team
Skill2 starsChanged 19 days agoMITView on GitHub
Answers which Dream Team step or skill fits the user's situation now: reads the open milestones, their issues without an open blocker, open MRs/PRs, the current branch and uncommitted changes, then recommends one skill with why it fits, a ready-to-run command and the WORKFLOW.md step that backs it, and starts that skill when the user says to go ahead or asked for the work itself. Use when the user runs /dream-team:ask-team or asks "which skill", "what now", "what next" or where they stand in the flow.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- l3a0/claude-pluginstheir own version, first seen Nov 1, 2026
- rafaelgarrafiel/team_skillstheir own version, first seen Oct 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- l3a0/claude-plugins★ 19same name
- rafaelgarrafiel/team_skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- assemble-metaSkill
- brainstormSkill
- build-issueSkill
- cut-milestonesSkill
- frictionSkill
- milestone-closeSkill
- qa-reviewSkill
- review-benchSkill
- scope-commitSkill
- scope-issueSkill
- scope-mrSkill
- scope-specSkill
- setup-dream-teamSkill
- ship-itSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read the open milestones and their open issues.
- Distinctive: line 19
Read the open MRs/PRs, the current branch and its uncommitted changes.
- Distinctive: line 23
Read WORKFLOW.md and pick the step and skill that fit the question and the state.
≈ “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
ask-team
1. Read where the work stands
- Read the open milestones and their open issues; keep those whose
Blocked bylines name no open issue. - Read the open MRs/PRs, the current branch and its uncommitted changes.
2. Pick the step
- Read WORKFLOW.md and pick the step and skill that fit the question and the state.
- A new or vague idea →
brainstorm.
3. Reply
- **Recommendation:** <skill> — <why it fits now>
- **Command:** `<ready-to-run command>`
- **Step:** <WORKFLOW.md step number and title>4. Hand off
- The user says to go ahead, or asked for the work itself → start the recommended skill.
- The recommended skill sets
disable-model-invocation: true→ tell the user to run the command themselves. - Otherwise → recommend only.
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.

