Moplan
Author and approve CRISPI structured plans in a local marimo notebook; /plan persists YAML and human sign-off to .moplan/moplan.db.
Overview
moplan is a plugin marketplace for the Validate phase that adds CRISPI structured planning and marimo-based human approval for Claude Code projects.
What is this marketplace?
- 1 plugin (moplan v0.2.0 MIT): CRISPI plan authoring + review in local marimo—no server
- /plan creates or reopens structured YAML; approvals persist to .moplan/moplan.db on every click
- Dual-agent critique workflow for plan review
- Plan YAML is the deliverable; integrates crispi, marimo, Claude Code
- strict: false marketplace entry from Shakes (shakestzd/moplan)
- 1 plugin in marketplace (v0.2.0 MIT)
- Persisted DB path: .moplan/moplan.db
- Repository: github.com/shakestzd/moplan
What problem does it solve?
AI-assisted builds often jump straight to code because informal plans are not reviewable, approvable, or durable across sessions.
Who is it for?
Claude Code users who want local marimo notebooks, CRISPI rigor, and click-to-approve planning without a hosted PM tool.
Skip if: Builders who refuse notebooks or YAML plans, or teams that already enforce rigid Jira-only planning with no agent bridge.
What do I get? / Deliverables
You get CRISPI plan YAML with persisted human approvals in .moplan/moplan.db, ready to drive implementation with less scope slip.
- CRISPI structured plan YAML
- Approval history in .moplan/moplan.db
- Reviewed plan notebook session via /plan
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is Validate → scope because moplan is for structured planning and human approval before implementation—not for writing production code. CRISPI plans with vertical slices and design questions tighten scope and surface unknowns while the build is still cheap to change.
How it compares
Planning notebook marketplace plugin, not a deployment MCP or code generator skill.
Common Questions / FAQ
Who is Moplan for?
Solo developers using Claude Code who want structured CRISPI plans reviewed in marimo with persistent approval history.
When should I use Moplan?
Use it before significant implementation—when you need vertical slices, design questions, and dual-agent critique on the plan itself.
How do I add Moplan to my agent?
Register the Moplan marketplace, install the Moplan plugin, ensure marimo runs locally, then use /plan to create YAML under your project and approve steps in the notebook UI.