mkelicitlisted

# Elicitation — Structured Second-Pass Reasoning Re-examine an existing output (review verdict, plan, analysis) through a named reasoning method. Surfaces insights that generic "make it better" requests miss. ## When to Use - After `/mk:review` verdict — deepen analysis before Gate 2 - After plan creation — stress-test assumptions before Gate 1 - After any agent output — when user wants a specific angle of analysis - When user says "dig deeper", "what am I missing", "challenge this" **NOT this skill if:** you have no existing artifact to re-examine — use `mk:brainstorming` for open exploration, or `mk:problem-solving` for approach-stuck situations. ## Reasoning Methods | Method | Lens | Best For | | ----------------------- | ----------------------------------------------- | --------------------------------------------- | | **Pre-mortem** | "Assume this shipped and failed. Why?" | Risk discovery, failure mode analysis | | **Inversion** | "What would make this maximally wrong?" | Assumption testing, edge cases | | **Red Team** | "You are an attacker. How do you exploit this?" | Security analysis, adversarial thinking | | **Socratic** | "What evidence supports each claim?" | Logic validation, gap detection | | **First Principles** | "Strip assumptions. What's funda