Stats
Actions
Tags
From missions
Start a new mission — /missions:start "<objective>". Creates the per-project mission control plane and enters the planning interview.
How this skill is triggered — by the user, by Claude, or both
Slash command
/missions:startThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Start a new mission with the objective given in the arguments (ask for one via
Start a new mission with the objective given in the arguments (ask for one via AskUserQuestion if missing). Steps — run them now:
.claude/settings.json (project or user scope) should set
"agent": "missions:missions-orchestrator" for mission sessions. If absent, print
the exact line to add and continue..claude/missions/ should be git-ignored (interview answers can be sensitive; the
dir bloats commits). If not covered by .gitignore/.git/info/exclude, warn and
offer to append.UUID="$(uuidgen | tr 'A-Z' 'a-z')". Create
./.claude/missions/$UUID/ plus subdirs handoffs evidence validation library skills planning hints. Copy every ${CLAUDE_PLUGIN_ROOT}/templates/new-mission/*.tpl into
the mission dir (strip the .tpl suffix) replacing {{MISSION_SHORT_ID}} (first 8
uuid chars), {{NOW}} (UTC ISO-8601), {{WORKING_DIRECTORY}} (the project root, or
what the user specified), {{OBJECTIVE}} / {{OBJECTIVE_TITLE}}.
Write $PWD git branch + working dir to working_directory.txt../.claude/missions/active-mission.txt.${CLAUDE_PLUGIN_ROOT}/bin/append-progress.sh mission_run_started '{"message":"Mission created: <objective summary>. Starting planning interview."}'npx claudepluginhub nicolas-palermo/dotclaude --plugin missionsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.