mission-definelisted

Authors a project's first `project/mission.md` per the canonical-language file under spec/project/mission/. Invoke when the user says "define the mission", "write project/mission.md", "set up the mission file", "draft the SMART mission", or equivalent German-language requests. Walks SMART one letter at a time (Specific statement, Measurable verifies_via pointer, Achievable MVP scope, Relevant outcome IDs, Time-bound shape), gathers a per-audience MVP-deliverable paragraph, composes the frontmatter plus the four required body sections (Statement, Audiences, Verification, Source), and writes the file with `mvp_status: defining`. Refuses to run when `project/mission.md` already exists (use `mission-revise`) or when `project/goals.md` or the audience artefact is missing. Supports resume on re-invocation per `spec/claude/resumable-work/`.
nolte/claude-shared · ★ 0 · AI & Automation · score 76

Install: claude install-skill nolte/claude-shared

# Mission Define Authors the first-write of `project/mission.md` against `spec/project/mission/<canonical_language>.md` (canonical language: English). The spec is the authority for the on-disk shape; this skill is the interactive front-end that fills it in. ## German trigger phrases This skill also triggers on equivalent German-language requests, including: - "Mission definieren" - "die SMART-Mission formulieren" - "Mission-Datei aufsetzen" ## Why this is a skill, not an agent - **Persistent on-disk artefact** — the output is a versioned markdown file consuming skills (`mission-revise`, future audits, the roadmap layer) read for years to come; a skill owns persistent state, an agent returns a structured report and forgets. - **Mid-flow user gating is the SMART contract** — every letter of SMART is a per-step user dialogue (audience choice, verifying-feature pointer, MVP scope size, outcome list, time-bound shape); the spec forbids batched output, so an agent's fire-and-forget shape would lose the gates. - **Output flows back into the main conversation** — the audience tailoring paragraphs and the verifying-feature reference must surface in the conversation so the user can iterate before the file is written; isolating them behind an agent's structured-report boundary would obscure the iterative drafting. - Counter-dimension considered: a narrower agent prompt could sharpen SMART-statement phrasing, but the load-bearing dimension here is interactivity (every SMART letter