Skip to content
Skills Library
Management & product · Planning

dev-ralplan

/dev-ralplan

Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.

Repository
evo-nexus ↗
Licence
Apache-2.0
Last repository change
12.05.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 12.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.

Original author description

Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.

How it works

  1. Use When
  2. Do Not Use When
  3. Workflow
  4. Mode Selection
  5. Output
  6. Pairs With
Original SKILL.md headings · 58 lines, 346 words
SKILL.md preview
---
name: dev-ralplan
description: Multi-perspective consensus planning with Planner/Architect/Critic loop. Use when high-stakes decisions need RALPLAN-DR structured deliberation (auth, migrations, public APIs, irreversible changes). Pairs with @compass-planner + @apex-architect + @raven-critic.
---

# Dev Ralplan

Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.

Consensus mode planning: a Planner/Architect/Critic loop that produces a plan with explicit principles, decision drivers, viable options, and an ADR. Used for high-stakes or irreversible work.

## Use When
- Multi-perspective consensus needed on a plan or design
- High-stakes work: auth, security, data migrations, destructive/irreversible changes, production incidents, compliance/PII, public API breakage
- User says "ralplan", "consensus", "let's deliberate"
- When `dev-plan --consensus` would normally apply

## Do Not Use When
- Simple, low-risk task → use `dev-plan` standard mode
- User wants direct execution → use `dev-autopilot`
- Single-perspective is sufficient → use `dev-plan` direct mode

## Workflow

### Stage 1 — Initial plan (`@compass-planner`)
- Run interview if needed
- Emit RALPLAN-DR summary: Principles (3-5), Decision Drivers (top 3), Viable options (≥2)
- If only 1 viable option remains, document explicit invalidation rationale for alternatives

### Stage 2 — Architecture review (`@apex-architect`)
- Read the plan
- Provide consensus addendum: strongest steelman antithesis, real tradeoff tension, synthesis if viable
- In deliberate mode, flag explicit principle violations

### Stage 3 — Critique (`@raven-critic`)
- Multi-perspective adversarial review
- Pre-commitment predictions
- Gap analysis
- Self-audit + realist check
- Verdict: REJECT / REVISE / ACCEPT-WITH-RESERVATIONS / ACCEPT

### Stage 4 — Revised plan (`@compass-planner`)
- Incorporate apex + raven feedback
- Final plan must include ADR: Decision, Drivers, Alternatives considered, Why chosen, Consequences, Follow-ups
- In deliberate mode: pre-mortem (3 scenarios) + expanded test plan (unit/integration/e2e/observability)

## Mode Selection
- **Short mode (default):** principles + drivers + ADR
- **Deliberate mode (`--deliberate`):** + pre-mortem + expanded test plan + principle violation flags

Trigger deliberate mode when: auth/security touched, data migration, destructive/irreversible change, production incident response, compliance/PII implications, public API breakage.

## Output
Final plan saved to `workspace/development/plans/[C]ralplan-{name}-{date}.md` with ADR section.

## Pairs With
- `@compass-planner` (drives the loop)
- `@apex-architect` (architecture review)
- `@raven-critic` (adversarial review)
- `dev-plan` (which can chain into ralplan with `--consensus`)
- `dev-autopilot` (skips its own Phase 0+1 if a ralplan plan already exists)

Versions

The database has no other skills named dev-ralplan.

Database snapshot: 13.11.2026 · package version c1893ba48b26 (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

  • 90ralplan
    Consensus planning with Planner/Architect/Critic iterative loop. Activate when user says: ralplan, consensus plan, consensus planning.
  • 100ralplan
    Consensus planning - agree before executing. Use for "ralplan", "consensus", "pre-execution review".
  • 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.
  • 95ralplan
    Use when requirements are sufficiently known but implementation is broad, risky, architecture-sensitive, cross-file, multi-step, or strategy-unclear and needs a plan; not for still-vague discovery or an execution-ready task.
  • 95ralplan
    Use when requirements are sufficiently known but implementation is broad, risky, architecture-sensitive, cross-file, multi-step, or strategy-unclear and needs a plan; not for still-vague discovery or an execution-ready task.
  • 100board-meeting
    Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes…

Feedback and reports

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