agentleFS
sreejithramansreejithraman/SreeStack/skills/reframe/SKILL.md

reframe

Skill1 starsChanged 16 days agoMITView on GitHub

Form a brief for requested reframing or as Goal Swarm's goal-formation step. Use the user's request and context to establish the outcome, methods, constraints, evaluation, and finish line.

8 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

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the request, settled decisions, and relevant project evidence.

    line 15
  2. Distinctive:

    Consider the dimensions that can improve this task:

    line 21
  3. Distinctive:

    Use Research for factual uncertainty worth investigating.

    line 35
  4. Distinctive:

    Use experiments to settle empirical questions within the requested scope.

    line 36
  5. Distinctive:

    Keep ambitious targets distinct from evidence that they have been achieved.

    line 37
  6. Distinctive:

    When another workflow calls Reframe, return the brief to that owner.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 8 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

Reframe

Form a brief worth executing from the user's request and context. Preserve explicit requirements while considering stronger ways to achieve the outcome. Scale the pass to what is unsettled: a precise request may need only a concise confirmation. Reframing alone ends with the brief.

Find the better task

Read the request, settled decisions, and relevant project evidence. Separate the desired result from the proposed means or artifact. Keep alternatives beyond authorized scope labeled as proposals. Use Verify's acceptance guidance to resolve what context can establish and ask for material user decisions.

Consider the dimensions that can improve this task:

  • Outcome: who needs what change, and what decision or activity does the requested artifact serve? Identify a higher-level outcome when it helps.
  • Depth: which original inputs, expert methods, and instruments would make the work more rigorous? Name the method rather than an expert persona.
  • Range: which adjacent field handles the same kind of problem, and which of its concrete techniques transfers here?
  • Evaluation: how and by whom should the result be judged, which constraints must hold, and what finish line was requested? Use the acceptance guidance to propose suitable checks or qualitative criteria, leaving uncertainty and missing prerequisites explicit.

Choose the strongest coherent framing rather than expanding every dimension. Use Research for factual uncertainty worth investigating. Use experiments to settle empirical questions within the requested scope. Keep ambitious targets distinct from evidence that they have been achieved.

Return the brief

State the outcome and target, scope and preserved constraints, relevant methods, evaluation, and requested finish line. Include material assumptions and unknowns; explain meaningful framing changes. Proposed evaluation is not evidence that the result has been achieved. Reuse the existing format and task record; a clear request can be confirmed in a few sentences without a separate document.

When another workflow calls Reframe, return the brief to that owner. The owner continues execution; do not start another copy of its workflow. In particular, Goal Swarm consumes the brief and keeps ownership of the goal.

For a direct reframing request, return the brief in chat unless another format or destination was requested. If the user also requested execution, continue through the authorized workflow with that brief. Requested goal or swarm execution uses Goal Swarm, passing the formed brief so it can be reused. Reframing alone authorizes no implementation, native goal, schedule, or external action.

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.