MaybeMonad Implementation Plan Review
Use this skill when the work is close to implementation but the user should review high-impact decisions first. The plan should make likely pivots visible, not bury them under mechanical task lists.
Workflow
- Inspect the territory:
- Current code paths, schemas, components, tests, runtime constraints, product behavior, and relevant docs.
- Identify high-change decisions:
- Data model or schema.
- Type interfaces or API contracts.
- State ownership and persistence.
- UX flow, copy, permissions, error states.
- Migration, rollout, compatibility, or performance constraints.
- Present decision points before the mechanical plan.
- State the recommended path and alternatives.
- Include validation gates:
- Unit or integration tests.
- Typecheck/build/lint.
- Browser/runtime/manual checks when user-visible.
- Data or migration verification when relevant.
- Add pivot triggers: discoveries that should update the plan before continuing.
- Put routine edits and refactors at the bottom.
Output Shape
Use this order:
- Goal and assumptions.
- Decisions to review.
- Recommended implementation path.
- Files or modules likely touched.
- Validation gates.
- Pivot triggers.
- Mechanical task list.
Rules
- Do not over-specify mechanical implementation when the agent can infer it safely from local patterns.
- Do not hide uncertain decisions in a task checklist.
- If a prototype, interview, or reference pass would materially change the plan, recommend that before implementation.
- Use HTML only when the plan benefits from visual structure or reviewer scanning; otherwise Markdown is enough.