mission

Create outcome-driven missions by researching projects and interviewing stakeholders.

2|1|Updated Jan 19, 2026

Search Tags:#workflow #planning #research #alignment #artifact #stakeholders #mission

Ready to run

npx skills add https://github.com/msieurthenardier/mission-control --skill mission-msieurthenardier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mission
Source: https://github.com/msieurthenardier/mission-control/tree/main/.claude/skills/mission
Command: npx skills add https://github.com/msieurthenardier/mission-control --skill mission-msieurthenardier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align research, stakeholder input, and artifact drafting to consistently define actionable missions for new projects, features, or initiatives.

Core Features & Use Cases

Research-driven mission creation that collects context from target projects.
Stakeholder interviews and discovery workflows to shape outcomes.
Drafts of mission artifacts in .flightops/ARTIFACTS.md for project-wide alignment and execution.

Quick Start

Start a new mission by initiating the guided interview flow to research your project and draft a concrete mission artifact.

Frequently Asked Questions about mission

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

FAQPage Schema

How do I create outcome-driven missions from project research?▼

To create outcome-driven missions, you initiate a guided interview flow that researches your project context, conducts stakeholder discovery, and drafts a mission artifact in .flightops/ARTIFACTS.md for execution.

What is the best way to align stakeholder input and research for a new initiative?▼

Aligning stakeholder input and research involves conducting discovery workflows and stakeholder interviews to shape outcomes, then drafting mission artifacts to ensure project-wide alignment and actionable execution.

Do I need a specific project structure to draft mission artifacts?▼

Drafting mission artifacts requires an initialized project with a .flightops/ARTIFACTS.md file for artifact structure, access to the target repository for context, and mission-design crew prompts to validate feasibility.

Can I use this workflow for both new projects and feature updates?▼

This workflow supports creating outcome-driven missions for new projects, features, or initiatives, collecting context from target projects and validating feasibility through iteration and stakeholder discovery.

When should I not use a research-driven mission creation process?▼

Avoid research-driven mission creation when you lack an initialized project with .flightops/ARTIFACTS.md, cannot access the target repository for context, or do not need stakeholder alignment for execution.