agentleFS
nshopiknshopik/dream-team/skills/ask-team/SKILL.md

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

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
  1. Very specific:

    Read the open milestones and their open issues.

    line 17
  2. Distinctive:

    Read the open MRs/PRs, the current branch and its uncommitted changes.

    line 19
  3. Distinctive:

    Read WORKFLOW.md and pick the step and skill that fit the question and the state.

    line 23

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ask-team

1. Read where the work stands

  • Read the open milestones and their open issues; keep those whose Blocked by lines 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.