cm-plan

Generates a design document and phased YAML roadmap from a shaped feature spec.

3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/PurdueRCAC/rcac-mcp --skill cm-plan-purduercac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-plan
Source: https://github.com/PurdueRCAC/rcac-mcp/tree/main/.agents/skills/cm-plan
Command: npx skills add https://github.com/PurdueRCAC/rcac-mcp --skill cm-plan-purduercac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a shaped feature goal into a concrete, reviewable design and phased implementation roadmap is slow and error-prone, especially when changes touch security-sensitive code paths. This Skill automates that planning step with enforced invariant checks and appetite-scaled research. ## Core Features & Use Cases - Invariant-gated design: Runs a mandatory pre- and post-design gate against AGENTS.md invariants, recording any deviations in a justification table instead of applying them silently. - Appetite-scaled research fan-out: Launches read-only research subagents (codebase-first, web for external unknowns) for big changes, or collapses to a lean plan for small fixes, with explicit exceptions for diagnostic fixes and high-blast-radius files. - Phased FSM roadmap: Produces spec/{slug}/PLAN.md and spec/{slug}/TECH.md — a YAML finite-state machine of vertical-slice phases with verify commands, consumed by the /cm-build step. - Use Case: After /cm-feature lands a GOAL.md on a feature branch, run /cm-plan to get a reviewed design, research digest, and an ordered phase list ready for human sign-off before any code is written. ## Quick Start Run /cm-plan on the current feature branch to turn spec/{slug}/GOAL.md into a design document and phased TECH.md roadmap.

Frequently Asked Questions about cm-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a design and implementation plan from a feature spec?

Run /cm-plan on a feature or fix branch after /cm-feature has produced a committed GOAL.md. It reads the goal, runs research scaled to the appetite, writes PLAN.md with the design, and generates TECH.md as a phased YAML roadmap.

How do I skip the research phase for a small change?

Pass the 'skip research' argument, for example /cm-plan skip research. This collapses the run to a lean plan with no subagent fan-out, though diagnostic fixes and changes to high-blast-radius files still trigger full research unless explicitly overridden.

What happens if my change touches security-sensitive execution code?

The invariant gate flags changes touching the execution path (context.py, middleware.py, auth.py, token.py, executor, server.py). These force a full research fan-out regardless of appetite, and affected phases are marked hammerable: false and parallel: false in TECH.md.

Can cm-plan run without subagent support in my AI harness?

Yes. The skill includes portability fallbacks: if subagents are unavailable, the research fan-out is performed sequentially by the main agent, writing the same research brief files. If AskUserQuestion is unavailable, it asks in plain text and stops.

Why does cm-plan stop before writing any code?

The skill is strictly a planning step and never edits source files. It stops after committing PLAN.md and TECH.md so a human can review the design and phase list; the separate /cm-build skill executes the implementation phases.