Skip to main content

MiCode

tip

399 GitHub stars — Structured Brainstorm → Plan → Implement workflow with full session continuity.

Overview​

MiCode enforces a structured development pipeline: brainstorm ideas, create a detailed implementation plan, then execute with session continuity. This prevents agents from jumping straight to code without understanding requirements and ensures every implementation step is grounded in an approved plan.

When to Use​

ScenarioBenefit
Complex featuresEnsure requirements are fully understood before coding
Team collaborationPlans can be reviewed and approved before implementation
Learning and onboardingStructured workflow guides less experienced developers
Quality controlEach implementation step is verified against the plan

How It Works​

Phase 1: Brainstorm​

The agent explores the problem space, asks clarifying questions, and documents requirements:

  1. Problem analysis — What are we solving and why?
  2. Constraint identification — What are the boundaries and requirements?
  3. Solution exploration — What approaches are available?
  4. Risk assessment — What could go wrong?

Phase 2: Plan​

The agent creates a detailed implementation plan:

  1. Architecture overview — Components, data flow, and interfaces.
  2. Step-by-step breakdown — Concrete implementation steps.
  3. Dependency mapping — What needs to exist before what.
  4. Testing strategy — How each step will be verified.
  5. Timeline estimate — Expected effort per step.

Phase 3: Implement​

The agent executes the plan with verification:

  1. Step execution — Implement one step at a time.
  2. Verification — Each step is tested before proceeding.
  3. Progress tracking — Completion status is maintained across the session.
  4. Continuity — If interrupted, the agent can resume from the last completed step.

Installation​

{
  "plugin": ["micode"]
}

Configuration​

Basic Setup​

{
  "plugin": ["micode"],
  "micode": {
    "require_plan_approval": true,
    "verify_each_step": true
  }
}

Automated Mode​

{
  "micode": {
    "require_plan_approval": false,
    "verify_each_step": true,
    "auto_proceed": true
  }
}

Usage​

Start a Brainstorm​

/micode brainstorm implement user notification preferences

The agent begins Phase 1: asking questions and exploring the problem space.

Review a Plan​

After brainstorming, the agent presents a plan:

/micode review-plan

The agent shows the detailed implementation plan. In require_plan_approval mode, you must approve before implementation begins.

Execute the Plan​

/micode implement

The agent begins Phase 3, working through each step sequentially and verifying before moving to the next.

Continue After Interruption​

/micode continue

The agent picks up from the last completed step, restoring full context.

Best Practices​

Be Thorough in Brainstorming​

  • The quality of the plan depends on the quality of the brainstorm.
  • Take time to answer the agent's clarifying questions fully.

Review Plans Carefully​

  • The plan is your opportunity to correct course before code is written.
  • Check for missing edge cases, incorrect assumptions, and architectural misalignments.

Use Verification​

  • Keep verify_each_step enabled for production work.
  • Automated verification catches issues early and reduces rework.

GitHub​

  • Repo: vtemian/micode
  • Topics: brainstorm, planning, workflow, rpi
  • Category: Agent Workflow / Orchestration