ibahgatibahgat/oh-my-iflow/skills/reasoning/SKILL.md

reasoning

Skill2 starsChanged 8 months agoMITView on GitHub

Control omi reasoning effort level to balance depth, rigor, latency, and token cost.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

0
Common
Most of the 4 edited versions we read keep these.
1
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

Distinctive:
Use this skill to set an explicit reasoning posture before planning, execution, or verification-heavy turns.
line 8

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

Purpose

Use this skill to set an explicit reasoning posture before planning, execution, or verification-heavy turns.

Trigger

User asks for faster vs deeper reasoning
Session needs tighter quality gates or lower latency
Team wants predictable planning/verification effort across stages

Supported Effort Levels

low
medium
high
xhigh

Workflow

Identify requested effort or infer medium as default.
Explain impact on planning depth, verification strictness, and cost/latency.
Persist/update .iflow/state/reasoning.json when filesystem tools are available.
Recommend a next command (/omi:mode, /omi:team, or /omi:loop) based on posture.

Output Template

## Reasoning
- requested:
- applied:

## Profile
| Dimension | Value |
| --- | --- |

## Next Command
- ...

Download now (ZIP)

Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
microsoft/devsquad-copilot★ 50same name
hajekim/agentic-design-patterns-skills★ 4same name
Firekid-is-him/Reasoning-Skill-Claude★ 1same name
hajekim/agentic-design-patterns-extension★ 1same 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 repository24 other files it gives its agents.
- ui-ux-pro-maxSkill
- approvalSkill
- autopilotSkill
- cancelSkill
- consensusSkill
- context-optimizeSkill
- deep-initSkill
- doctorSkill
- executeSkill
- hooksSkill
- hudSkill
- intentSkill
- loopSkill
- memorySkill
- modeSkill
- planSkill
- prdSkill
- ralphSkill
- ralplanSkill
- researchSkill
- rulesSkill
- team-assembleSkill
- teamSkill
- ultraworkSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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