spec-kitty-mission-system

Name: spec-kitty-mission-system
Availability: InStock
Author: kimprobably

Explain Spec Kitty mission types, phases, artifacts, and guards for workflow advancement.

Updated May 13, 2026

Search Tags:#workflow design #specification #agent prompts #state machine #guard conditions #template resolution #doctrine composition

Ready to run

npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-mission-system

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-kitty-mission-system
Source: https://github.com/kimprobably/maestro-os/tree/main/.claude/skills/spec-kitty-mission-system
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-mission-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It explains how to model and choose Spec Kitty missions so you can reliably define the workflow, step ordering, required artifacts, and doctrine-driven behaviors for an AI execution run.

Core Features & Use Cases

Clarifies the mission hierarchy: mission type → mission → work packages → isolated execution workspaces.
Documents built-in mission types and transitions: software-dev, research, plan, and documentation, including their step sequences, guards, and required artifacts.
Shows how doctrine composes behavior: step contracts delegate to procedures, tactics, and directives, and action indices scope injected doctrine per action.

Quick Start

Use the spec-kitty mission system to map your goal to the correct mission type and define which artifacts and guards must exist for the workflow to advance.

Frequently Asked Questions about spec-kitty-mission-system

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

FAQPage Schema

How do I design AI agent workflows with state machine guard conditions?▼

Designing AI agent workflows with state machine guard conditions involves mapping mission types to required artifacts and advancement rules. You can model mission.yaml state machines to define step ordering, required artifacts, and doctrine-driven behaviors for reliable AI execution runs.

What are mission types and how do they structure workflow behavior?▼

Built-in mission types like software-dev, research, plan, and documentation define end-to-end step sequences, transitions, and required artifacts. They structure workflow behavior by mapping specific work domains to runtime DAGs and isolated execution workspaces.

How do I select the right mission type for my AI execution run?▼

Selecting the right mission type requires mapping your goal to the correct workflow domain. You evaluate built-in mission types, their specific step sequences, and required artifacts to determine which aligns with your work domain before resolving templates through the five-tier chain.

How does doctrine composition work with step contracts and action indices?▼

Doctrine composition works by delegating step contracts to procedures, tactics, and directives. Action indices scope injected doctrine per action, ensuring the correct workflow behaviors are applied and advanced through the mission hierarchy from work packages to isolated execution workspaces.

What is the five-tier chain for resolving mission templates?▼

The five-tier chain for resolving mission templates is the mechanism used to map mission phases to required artifacts and guards. It ensures workflow templates are correctly resolved and applied across different work domains, runtime DAGs, and execution contexts.

When should I not use a mission system for workflow design?▼

You should avoid a mission system for workflow design when your task does not require strict step ordering, required artifacts, or doctrine-driven behaviors. It is best suited for complex AI execution runs needing reliable end-to-end workflow behavior and advancement rules.