skills.rest
calcosmic
calcosmicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

colony-lifecycle

Enforce lifecycle state transitions and generate Next Up prompts for multi-step workflows.

9|1|Updated Feb 1, 2026
Search Tags:#workflow#routing#guidance#lifecycle#state-machine#colony#next-up
One-click install
npx skills add https://github.com/calcosmic/Aether --skill colony-lifecycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: colony-lifecycle
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/colony-lifecycle
Command: npx skills add https://github.com/calcosmic/Aether --skill colony-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates command outputs by enforcing a clear next action using a defined colony state machine, preventing dead ends and guiding users through transitions.

Core Features & Use Cases

  • Enforces lifecycle states (IDLE, READY, PLANNING, EXECUTING, SEALED, ENTOMBED) to orient user actions and ensure progress.
  • Generates a deterministic "Next Up" block after each command to communicate the immediate next steps.
  • Provides routing guardrails that handle ambiguity, recover from failed states, and maintain state consistency across multi-step workflows.

Quick Start

End each command output with a Next Up block to guide the user to the next phase of the colony workflow.

Frequently Asked Questions about colony-lifecycle

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

FAQPage Schema
How do I guide multi-step workflows to a clear next action after each command?▼

You can enforce a clear next action by routing command outputs through a defined colony state machine, which maintains lifecycle state and generates deterministic Next Up prompts to prevent dead ends.

What is a colony state machine and how does it manage workflow lifecycle states?▼

A colony state machine is a routing guide that enforces lifecycle states like IDLE, READY, PLANNING, EXECUTING, SEALED, and ENTOMBED to orient user actions and ensure deterministic transitions across multi-step workflows.

How do I prevent dead ends and recover from failed states in multi-step command routing?▼

To prevent dead ends and recover from failed states, the workflow state machine provides routing guardrails that handle ambiguity and maintain state consistency, generating a Next Up block after each command.

When do I need a state machine for workflow routing and command execution?▼

You need a state machine for workflow routing when coordinating complex multi-step processes that require deterministic transitions between phases like planning, execution, sealing, and entombment to maintain progress.

Can I use this workflow routing guide for multi-step execution without external dependencies?▼

Yes, this workflow routing guide operates independently without external dependencies, enforcing lifecycle states and generating Next Up prompts to coordinate command outputs across multi-step workflows.

What are the limitations of using a state machine for workflow lifecycle guidance?▼

The state machine approach requires strict adherence to defined lifecycle states and deterministic transitions, meaning any workflow step outside the IDLE, READY, PLANNING, EXECUTING, SEALED, or ENTOMBED states will not be guided.

Related Skills

Explore More Software Engineering Skills→
kzarzyckikzarzycki

flow

Orchestrate persistent multi-step project workflows across Claude Code sessions.

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-next

Determine and trigger the next GSD workflow step from STATE.md and ROADMAP.md.

Community
Intermediate
dd-xiaozhidd-xiaozhi
2

flow-engine

Manage state transitions and event logging for multi-step AI development workflows.

Community
Advanced
Venkateshvenki404224Venkateshvenki404224
25

frappe-workflow-generator

Generate Frappe workflow JSON definitions for document approvals and state transitions.

Community
Intermediate