lean-task
Installation
SKILL.md
lean-task
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. Input is the requested behavior or fault, expected versus observed outcome, available evidence and requested endpoint. Reuse agreed acceptance; ask only for missing material facts.
- Diagnosis only. A diagnosis-only request concludes with the supported cause or narrowed hypotheses, reproducer/probes, limitations and next action, without editing the application.
- DONE, BLOCKED, FAILED. Use DONE for a completed requested diagnosis or implementation; BLOCKED for an indispensable missing observation/access/decision, and FAILED for a demonstrated unresolved mandatory failure.
- Diagnosis. Diagnose unclear or non-trivial faults using structured diagnosis. A diagnosis result does not complete a requested repair.