agentleFS
Sign inStart free
jamillazarevjamillazarev/multica-ops/skills/consult/SKILL.md

consult

Skill11 starsChanged 49 days agoApache-2.0View on GitHub

A question, not a build: answered as an advisor, with nothing created in your workspace.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use discover, review and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • MicrosoftSkill

    council

    Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Load and follow the multica-ops skill (../mops/SKILL.md), executing its /multica-ops:consult flow (FLOWS.md → Consult). An advisory session: answer the owner's question as an advisor with a zero standing footprint — create nothing that outlives the session, keep answers sourced and evidence-tiered, spin research (and, on request, validation) sub-agents ephemerally, and offer to persist or projectize only when the answer leads there.

Optional addressee — /multica-ops:consult [who] <question>: the contract is a property of the conversation, so the default is Mops but any addressee answers under it. Name a team agent (answers from its own craft), an expert (its own voice and sources), or the theatre (personas react — direction-only, 🎭-marked, registered nowhere — but a consulted validated twin still logs its own use per its consent contract, MODULES → Persona theatre). Route to the one addressee, no fan-out. Args: $ARGUMENTS

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.

Check your setup, free