Skip to content
Skills Library
Management & product · Planning

plan

/plan

Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a plan, how should we approach.

Repository
gitlab-mcp ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a plan, how should we approach.

Arguments

/plan [--direct|--consensus|--review] <task description>
Original author description

Strategic planning with optional interview workflow. Activate when user says: plan this, plan the, let's plan, make a plan, how should we approach.

How it works

  1. Modes
  2. Interview Mode (broad/vague requests)
  3. Direct Mode (detailed requests)
  4. Consensus Mode (--consensus / "ralplan")
  5. Review Mode (--review)
  6. Output
Original SKILL.md headings · 46 lines, 251 words
SKILL.md preview
---
name: plan
description: >
  Strategic planning with optional interview workflow.
  Activate when user says: plan this, plan the, let's plan,
  make a plan, how should we approach.
argument-hint: "[--direct|--consensus|--review] <task description>"
---

# Plan

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

## Modes

| Mode | Trigger | Behavior |
|------|---------|----------|
| Interview | Default for broad requests | Interactive requirements gathering |
| Direct | `--direct`, or detailed request | Skip interview, generate plan directly |
| Consensus | `--consensus`, "ralplan" | Planner → Architect → Critic loop |
| Review | `--review` | Critic 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

Versions

RepositoryScoreLicence
This page · zereight/gitlab-mcp90MIT
mlophez/polix-ai100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT
duronext/jig100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
xoai/sage100MIT
JoDi-27/JoDi-SDD100MIT

Database snapshot: 13.11.2026 · package version cf2e46af3bd8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90grill-me
    Interview the user one question at a time to pin down a vague idea, feature or plan before any code is written. Use when the user says "grill me", wants to think a design through, or the request is too fuzzy to plan.
  • 100v1-interview-me
    Use when an idea, feature request, or ticket needs structured questioning before planning. Triggers on "interview me", "flesh out this idea", or "help me spec this".
  • 90dev-plan
    Strategic planning with optional interview workflow. Use when the user wants to plan before implementing — "plan this", "let's plan", structured requirements gathering for vague ideas. Pairs with @compass-planner agent. Supports consensus mode and review mode.
  • 95prep-plan
    Use to think through an implementation approach with the user, discuss useful evidence, and optionally record a working plan. Input can be conversational intent, design, brainstorm, research, or a prompt. Triggers include "prep plan", "prepare a plan", "plan this", "make a…
  • 100make-plan
    Planning executor. ALWAYS invoke this skill when instructed to create, devise, or write an implementation plan. Do not explore the codebase or draft a plan directly — use this skill first to load the planning workflow.
  • 82plan-objective
    Create a detailed execution plan for an objective, breaking it into concrete tasks with success criteria. Use when the user wants to plan an objective, create execution plans, or prepare for building. Triggers on: "plan objective", "create plans", "plan the next objective",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.