agentleFS
Sign inStart free
BlakeemBlakeem/aipromptguide-workflows/skills/decide/SKILL.md

decide

Skill1 starsChanged 8 days agoMITView on GitHub

Run the AIPG decide workflow, which runs a bounded chain of investigators that find and improve the options, ranks the options in one weighted matrix and has a final reviewer verify the ranking. Use only when the user explicitly asks for the AIPG decide workflow.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use redesign, weekly and 9 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.
  • arjunkshahSkill

    redesign

    Redesign existing interfaces to premium quality while preserving product goals and functional behavior.

    Also in 3 projects that use this

  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 3 projects that use this

  • SethGammonSkill

    experiment

    Automated optimization loop with scalar fitness function. Proposes changes in isolated worktrees, measures with a metric command, keeps improvements, discards failures. Supports convergence detection and diminishing returns.

    Also in 3 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 3 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 5 projects that use this

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

    line 13
  2. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/workflows/decide/CLAUDE.md and follow it exactly.

    line 16
  3. Distinctive:

    Use these paths wherever the guide says "this checkout" or "the tool's own directory":

    line 18

“Common” is measured: kept by at least 6 in 10 of the 50 edited versions of this file we could read. “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

The user wants to run the decide-cycle dynamic workflow on the decision below.

First run node "${CLAUDE_PLUGIN_ROOT}/tools/plugin-access.mjs" check. The Workflow tool launches only engines the session can read. On missing, unless the working directory is ${CLAUDE_PLUGIN_ROOT} or a folder above it, ask the user once whether to add the printed Read rule to their user settings. On yes, run the command again with grant (settings reload live, no restart). On no, the user can run /add-dir ${CLAUDE_PLUGIN_ROOT} for this session only. When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

Read ${CLAUDE_PLUGIN_ROOT}/workflows/decide/CLAUDE.md and follow it exactly. Work its ## 0. Checklist top to bottom. Use these paths wherever the guide says "this checkout" or "the tool's own directory":

  • Engine scriptPath: ${CLAUDE_PLUGIN_ROOT}/workflows/decide/decide-cycle.mjs
  • root arg: ${CLAUDE_PLUGIN_DATA}. Runs land in its runs/<runId>/. Never the plugin install dir, which is version-swapped on update.

$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