From mission-spec
Generates a new Mission Decision Record (MDR) draft from a natural language description of the decision. Use when the user is about to make a non-trivial architectural / policy / scope change that deserves a written record. Triggered by requests like "write an MDR", "document this decision", "new decision record", "MDR-005".
How this skill is triggered — by the user, by Claude, or both
Slash command
/mission-spec:ms-decideThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
[English](SKILL.md) | [한국어](SKILL.ko.md) | [中文](SKILL.zh.md)
.mission/decisions/ for existing MDR-NNN-*.md files and pick the next available number (zero-padded to 3 digits)..mission/templates/MDR_TEMPLATE.md with the provided fields; leave explicit placeholders for sections the user did not fill.Status: Proposed, today's date, and [target version] / [author] placeholders when unspecified.goal direction changesconstraints policy changesdone_when evaluation philosophy changesevals ↔ done_when linkage changesIf the user's proposed change does not match any of these, ms-decide should still work, but flag whether a full MDR is warranted versus a simpler mission-history.yaml entry.
Library:
import { generateMdrDraft } from "mission-spec";
const { markdown, suggestedPath, nextMdrNumber } = generateMdrDraft({
title: "Adopt deterministic CHANGELOG generation",
context: "CHANGELOG.md drifted from mission-history.yaml several times.",
decision:
"Generate CHANGELOG.md from mission-history.yaml via pre-commit hook.",
projectDir: ".",
});
CLI (v1.12.0+):
# No dedicated mission-spec subcommand yet — use node + inline:
node -e "import('mission-spec').then(m => m.generateMdrDraft({title: process.argv[1], projectDir: '.'}).markdown)" "Your decision title"
.mission/decisions/ — the authoritative MDR archive.mission/templates/MDR_TEMPLATE.md — the canonical template this skill fillsmission-history.yaml related_decisions — link an MDR ID from a history entry once the MDR is committedGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub chquandogong/mission-spec --plugin mission-spec