Manage Status Skill

Manage status.json files with phase tracking, metadata, and lifecycle operations. Handles plan status storage (JSON), phase operations, metadata management, plan discovery, phase transitions, archiving, and routing.

Enforcement

Base contract: See manage-contract.md for shared enforcement rules, TOON output format, and error response patterns.

Skill-specific constraints:

• Only valid phase status values: pending, in_progress, done
• Phase transitions must use set-phase, update-phase, or transition commands
• Metadata operations require explicit --get or --set flags

Standards: See status-lifecycle.md for the phase state machine, plan lifecycle, and metadata conventions.

• Do not skip phase transition validation
• Phase transitions are sequential -- you cannot skip phases
• Routing context is read-only; use get-routing-context for combined state

Storage Location