mcpField
P
plan

plan

github.com/zereightAgent workflows2.1k66 installsUpdated today
Repository

About plan

A planning skill for turning requests into actionable work plans. It adapts between requirements interviews and direct planning, with optional consensus and review modes.

Key features

  1. 01Interactive requirements gathering
  2. 02Direct planning for detailed requests
  3. 03Planner, architect, and critic consensus loop
  4. 04Review existing plans
  5. 05Plans with criteria, steps, risks, and verification

Use cases

  1. 01Clarifying scope for a broad project request
  2. 02Drafting an implementation plan from detailed requirements
  3. 03Comparing plan options through consensus review
  4. 04Evaluating an existing plan

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zereight/gitlab-mcp --skill plan

After installing, type/planin Claude Code to confirm it loaded.

Details

From the project README

Plan

Creates comprehensive, actionable work plans through intelligent interaction. Auto-detects whether to interview (broad requests) or plan directly (detailed requests).

Modes

ModeTriggerBehavior
InterviewDefault for broad requestsInteractive requirements gathering
Direct--direct, or detailed requestSkip interview, generate plan directly
Consensus--consensus, "ralplan"Planner → Architect → Critic loop
Review--reviewCritic evaluation of existing plan

Interview Mode (broad/vague requests)

  1. Classify request: broad triggers interview
  2. Ask ONE focused question at a time for preferences, scope, constraints
  3. Gather codebase facts via @explore BEFORE asking user
  4. Consult @analyst for hidden requirements
  5. Create plan when user signals readiness

Direct Mode (detailed requests)

  1. Optional brief @analyst consultation
  2. Generate comprehensive work plan immediately

Consensus Mode (--consensus / "ralplan")

  1. @planner creates initial plan with RALPLAN-DR summary (Principles, Decision Drivers, Options)
  2. @architect reviews for architectural soundness (sequential, NOT parallel with critic)
  3. @critic evaluates quality criteria (after architect completes)
  4. Re-review loop (max 5 iterations) if critic rejects
  5. Apply improvements on approval
  6. Final plan includes ADR (Decision, Drivers, Alternatives, Why chosen, Consequences)

Review Mode (--review)

  1. Read plan from .omc/plans/
  2. @critic evaluates
  3. Return verdict: APPROVED / REVISE / REJECT

Output

Plans saved to .omc/plans/. Include:

  • Requirements Summary
  • Testable Acceptance Criteria
  • Implementation Steps (with file references)
  • Risks and Mitigations
  • Verification Steps

Comments

Markdown supported