factory-state-machine

name	factory-state-machine
compatibility	["github-copilot-cli"]
description	Use when defining factory state transitions, reading or writing .github/factory-state.json, or orchestrating workcell workflow gates. USE FOR: intake/complete/pending transitions, auto-proceed rules, escalation checks, and state validation. DO NOT USE FOR: general app state management or unrelated workflow docs.
category	architecture
visibility	internal
metadata	{"category":"architecture","maturity":"stable","audience":["developer"]}
allowed-tools	[]

Factory State Machine Skill

Model and validate factory state transitions for orchestration workflows.

Templates in This Skill

Template	Purpose
factory-state-template.json	Starter .github/factory-state.json with states, transitions, and escalation rules

Core Rules

• Keep the state file as the single source of truth.
• Model each transition explicitly; do not infer hidden hops.
• Separate automatic transitions from human escalation.
• Make terminal states and rollback states obvious.
• Keep state names and conditions deterministic so workflows can read them safely.

Agent Pairing

Use with factory orchestration agents that read .github/factory-state.json and trigger Workcell workflows.