lean-init
Installation
SKILL.md
lean-init
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 repository and discovery goal, or the current project.
- DONE. Finish discovery with DONE when its root, relevant entry points, instructions and commands are evidenced; include observed failures, unknowns and the next useful action. A discovered application defect is a finding, not permission to repair it or a failure of discovery.
- BLOCKED. Use BLOCKED when a required path, access or fact cannot be established; identify the exact missing prerequisite and completed discovery.
- Verification. Never label an unexecuted command verified.