lean-scope
Installation
SKILL.md
lean-scope
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 request, known users/constraints and any existing agreement.
- READY. Return READY when the bounded scope has observable acceptance, a verification method and delivery destination; READY_WITH_ASSUMPTIONS when only explicit reversible assumptions remain.
- BLOCKED. Return BLOCKED for a material unanswered decision, naming its effect and the next question.
- Evidence. Cite the request, decisions and project evidence that support the scope.
- Product and UX. Read product and UX acceptance for product discovery or user-facing behavior where usability or accessibility affects acceptance.
- Scope only. A scope-only request ends with this deliverable; it does not start implementation.