state-machine

Manage task lifecycle state transitions with validation gates and iteration loops.

7|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/MadAppGang/magus --skill state-machine-madappgang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-machine
Source: https://github.com/MadAppGang/magus/tree/main/plugins/autopilot/skills/state-machine
Command: npx skills add https://github.com/MadAppGang/magus --skill state-machine-madappgang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust framework for managing the lifecycle of tasks, ensuring that transitions between states are valid and that necessary validation checks are performed before changes occur.

Core Features & Use Cases

  • State Transition Management: Defines clear states (Todo, In Progress, In Review, Done, Blocked) and the valid transitions between them.
  • Validation Gates: Implements checks (e.g., acceptance criteria, proof quality, confidence scores) that must pass before a state transition can occur.
  • Iteration Handling: Supports loops for iterative development, allowing tasks to return to 'In Progress' from 'In Review' based on feedback.
  • Escalation: Manages transitions to a 'Blocked' state due to unresolvable issues or exceeding iteration limits.
  • Use Case: Automate the workflow for code reviews, ensuring that a task only moves to 'In Review' after all tests pass and code quality meets a certain threshold, and only to 'Done' after user approval or high confidence.

Quick Start

Use the state-machine skill to transition the current task from 'In Progress' to 'In Review'.

Frequently Asked Questions about state-machine

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

FAQPage Schema
How do I enforce validation gates for task lifecycle state transitions?

To enforce validation gates for task lifecycle state transitions, define the required checks for entry conditions, trigger events, and proof-based validation. This ensures necessary validation occurs before any task state changes.

How do I handle iteration loops when a task fails review validation?

Handling iteration loops during task validation allows a task to return to 'In Progress' from 'In Review' based on feedback. This supports iterative development cycles until proof quality and confidence scores pass.

Can I automate workflow approvals using confidence scores and proof quality?

Workflow approvals can be automated using defined validation gates that check confidence scores and proof quality. This allows tasks to automatically progress to 'Done' when acceptance criteria are met without manual review.

What is the best way to manage task escalation to a blocked state?

Managing task escalation to a blocked state requires enforcing workflow rules that trigger on unresolvable issues or exceeding iteration limits. This prevents invalid task progression within the lifecycle.

Does task lifecycle management work without external dependencies?

Task lifecycle management works without external dependencies, using internal scripts and references to define valid state transitions. This standalone approach ensures workflow rules and validation gates function natively.

Why does a task transition fail when moving from Todo to Done?

A task transition fails when moving from Todo to Done because state transition management enforces valid progression paths, requiring intermediate states like 'In Progress' and 'In Review' with passing validation gates.