MaybeMonad Pitch Explainer
Use this skill to accelerate reviewer understanding and approval. The output should answer the unknowns reviewers are likely to have before they need to ask.
Workflow
- Gather source material:
- Prototype, spec, plan, implementation notes, diff summary, screenshots, demo GIF/video, commands run, tests, runtime checks, and unresolved risks.
- Identify the audience:
- Product, design, engineering, security, data, leadership, or a mixed review group.
- Lead with the demo or visible outcome when one exists.
- Explain the problem and why the chosen approach is appropriate.
- Include alternatives rejected and why.
- Show which unknowns were resolved and which remain.
- Include verification evidence and reviewer asks.
Output Shape
Use this structure:
- Demo or outcome.
- Problem.
- What changed.
- Decisions and tradeoffs.
- Unknowns resolved.
- Verification evidence.
- Remaining risk.
- Reviewer asks.
Rules
- Write for approval, not for archival completeness.
- Lead with the most concrete artifact: demo, screenshot, prototype, or user flow.
- Do not hide residual risk. State it with its mitigation or follow-up.
- Do not paste long diffs. Explain behavior and link or reference files.
- Keep stakeholder text crisp enough to drop into Slack or a review doc.