lean-target

Installation
SKILL.md

lean-target

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 an existing path or remote URL. Reuse an explicitly requested destination.
  • Layout. Without a specified layout, prefer a separate clone; use a submodule only when the user or project explicitly wants parent-repository tracking.
  • DONE. DONE means the requested selection/clone and any explicitly requested setup are verified at the reported path; give repository identity, branch/commit (or unborn state), dirty state, relevant instructions and checks. Selection alone does not require application changes or a passing application build.
  • BLOCKED and FAILED. Return BLOCKED for ambiguous identity/destination, missing access or an unsafe collision, and FAILED for an unresolved executed setup failure.
  • Partial state. Report partial state before a retry, including whether an operation ran or its outcome is uncertain; never erase it to simulate a clean start.

Steps

Installs
2
First Seen
Nov 1, 2026