lean-effort
Installation
SKILL.md
lean-effort
Ground rules
- Standalone. Standalone skill: use the current request or explicit arguments. Read applicable project instructions and only task-relevant context.
- No prerequisites. No Lean installation, CLI, configuration or companion skill is required; do not install a workflow or create workflow files as prerequisites. Existing project rules apply.
- Depth. Use requested procedure depth, or standard by default. High adds relevant boundary cases and stronger evidence; ultra adds cross-part consistency and contradictory evidence where relevant. Depth does not change model reasoning settings.
- Records. Keep decisions in conversation unless a suitable project record exists or the user requests persistence.
Input and result
- Input. Accept no arguments to inspect; otherwise accept standard, high, ultra or reset, optionally scoped to a named procedure. Interpret input as text, never shell code.
- DONE. Conclude DONE with the requested operation, resulting conversation-wide level, named overrides and effective level for the relevant procedure. The evidence is the explicit preference and precedence calculation, not a model/backend claim.
- BLOCKED. If a level or scope cannot be interpreted, return BLOCKED with the missing choice and preserve the previous setting.
- Persistence. A requested persistent write is complete only after verifying its agreed destination; an unrequested settings file is outside scope.