lean-gate
Installation
SKILL.md
lean-gate
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 existing agreement, exact deliverable state and evidence.
- Assessment only. An assessment-only request ends with the assessment; repair requires matching authorization.
- BLOCKED, FAILED. The conclusion must name each unmet mandatory condition, distinguish missing evidence (BLOCKED) from demonstrated unresolved failure (FAILED), and give completed checks and the next action.
- DONE. DONE requires the requested destination and evidence appropriate to the task; UI accessibility, security, migration/recovery and post-release checks are mandatory only when required by the agreement, project rules or relevant risk.