cm-feature

Shapes a feature or fix request into a refined GOAL.md specification on a new git branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting new work on an HPC cluster-mcp project often begins with vague ideas and unscoped requests. This Skill turns an inline description, a hand-written GOAL.md, or a deferred issue into a bounded, unambiguous specification with acceptance criteria before any expensive planning or coding begins. ## Core Features & Use Cases - Goal Shaping: Converts a raw feature, fix, or refactor request into a structured spec/{slug}/GOAL.md with problem statement, outcome, EARS-style acceptance criteria with stable R-IDs, non-goals, and resolved clarifications. - Branch & Safety Management: Verifies a clean main branch, derives a kebab-case slug, and creates the correct feature/{slug} or fix/{slug} branch, stopping on collisions or dirty trees. - Issue Promotion: Promotes deferred issues/{slug}.md records into shaped goals, respecting their status (unshaped, shaped, adopted, declined) and updating the ROADMAP index. - Use Case: Run /cm-feature with "add a --dry-run flag to sbatch" to get a feature/sbatch-dry-run branch containing a reviewable GOAL.md, ready for sign-off before the planning phase. ## Quick Start Ask the agent to start a new feature by describing it, for example: run cm-feature to shape a goal for adding a dry-run flag to sbatch that prints the script without submitting.

Frequently Asked Questions about cm-feature

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

FAQPage Schema
How do I start a new feature with a spec-driven workflow?

Invoke the skill on a clean main branch with an inline description, a path to a hand-written spec/<slug>/GOAL.md, or an issues/<slug>.md file. It creates a feature/{slug} or fix/{slug} branch and writes a refined GOAL.md with acceptance criteria for your sign-off.

What inputs does the cm-feature skill accept?

It accepts an inline feature description, a path to an untracked spec/<slug>/GOAL.md to adopt, or an issues/<slug>.md deferral to promote. Optional modifiers set the kind (fix, refactor) and appetite (small or big).

Does cm-feature write code or do research?

No. It is shaping-only: it produces exactly one artifact, a refined GOAL.md, and stops. Research, design, implementation, and publishing are handled by the later cm-plan, cm-build, and cm-publish steps.

Why does cm-feature stop instead of switching branches automatically?

It requires starting from a clean main branch as a safety principle. If the current branch is not main or the tree has unrelated changes, it stops and asks you to commit, stash, or discard first rather than mutating your state.

What happens when promoting an issue with status declined?

The skill stops and reports that the issue is a terminal record, quoting its existing reasoning. Declined and accepted-behaviour issues are settled questions; re-opening one requires a deliberate status change by a human first.