kasmos-lifecycle — for Claude Code kasmos-lifecycle, kasmos, community, for Claude Code, ide skills, planning, implementing, lifecycle, Meta-skill, Covers

v1.0.0
GitHub

Acerca de este Skill

Perfecto para agentes de codificación de IA que necesitan una implementación automatizada basada en ondas y gestión del ciclo de vida del plan. Resumen localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Características

Meta-skill. Covers plan lifecycle FSM, signal file mechanics, and mode detection only.
If you have a role (planner, coder, reviewer, custodian), load that skill instead — not this one.
Plans move through a fixed set of states. Only the transitions listed below are valid.
From To Triggering Event
------ ---- -----------------

# Temas principales

for Claude Code planning implementing kasmos lifecycle Meta-skill
kastheco kastheco
[3]
[0]
Actualizado: 3/24/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Perfecto para agentes de codificación de IA que necesitan una implementación automatizada basada en ondas y gestión del ciclo de vida del plan. Resumen localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Por qué usar esta habilidad?

Habilita a los agentes a simplificar los ciclos de vida del plan, la mecánica de archivos de señalización y la detección de modos utilizando transiciones de Finite State Machine (FSM), lo que lo convierte en una herramienta esencial para flujos de trabajo de IA eficientes con kasmos assigns y

Mejor para

Perfecto para agentes de codificación de IA que necesitan una implementación automatizada basada en ondas y gestión del ciclo de vida del plan.

↓ Casos de uso accionables for kasmos-lifecycle

Automatizar las transiciones del ciclo de vida del plan desde listo hasta planificación e implementación
Generar mecánica de archivos de señalización para la detección de modos
Depurar transiciones de ciclo de vida de FSM para flujos de trabajo de IA eficientes

! Seguridad y limitaciones

  • Requiere que kasmos asigna un agente de planificación al plan
  • Solo válido para transiciones de FSM específicas (listo para planificación, planificación para implementación)
  • Limitado al ciclo de vida del plan, la mecánica de archivos de señalización y la detección de modos

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Demo Labs

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ y pasos de instalación

These questions and steps mirror the structured data on this page for better search understanding.

? Preguntas frecuentes

¿Qué es kasmos-lifecycle?

Perfecto para agentes de codificación de IA que necesitan una implementación automatizada basada en ondas y gestión del ciclo de vida del plan. Resumen localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

¿Cómo instalo kasmos-lifecycle?

Ejecuta el comando: npx killer-skills add kastheco/kasmos. Funciona con Cursor, Windsurf, VS Code, Claude Code y más de 19 IDE adicionales.

¿Cuáles son los casos de uso de kasmos-lifecycle?

Los casos de uso principales incluyen: Automatizar las transiciones del ciclo de vida del plan desde listo hasta planificación e implementación, Generar mecánica de archivos de señalización para la detección de modos, Depurar transiciones de ciclo de vida de FSM para flujos de trabajo de IA eficientes.

¿Qué IDE son compatibles con kasmos-lifecycle?

Esta skill es compatible con Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Usa la CLI de Killer-Skills para una instalación unificada.

¿Tiene limitaciones kasmos-lifecycle?

Requiere que kasmos asigna un agente de planificación al plan. Solo válido para transiciones de FSM específicas (listo para planificación, planificación para implementación). Limitado al ciclo de vida del plan, la mecánica de archivos de señalización y la detección de modos.

↓ Cómo instalar este skill

  1. 1. Abre tu terminal

    Abre la terminal o línea de comandos en el directorio de tu proyecto.

  2. 2. Ejecuta el comando de instalación

    Ejecuta: npx killer-skills add kastheco/kasmos. La CLI detectará tu IDE o agente automáticamente y configurará la skill.

  3. 3. Empieza a usar el skill

    El skill ya está activo. Tu agente de IA puede usar kasmos-lifecycle de inmediato en el proyecto actual.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

kasmos-lifecycle

Resumen localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

kasmos lifecycle

Meta-skill. Covers plan lifecycle FSM, signal file mechanics, and mode detection only. If you have a role (planner, coder, reviewer, custodian), load that skill instead — not this one.

Plan Lifecycle

Plans move through a fixed set of states. Only the transitions listed below are valid.

FromToTriggering Event
readyplanningkasmos assigns a planner agent to the plan
planningimplementingplanner writes sentinel planner-finished-<planfile>
implementingreviewingcoder writes sentinel coder-finished-<planfile>
reviewingimplementingreviewer writes sentinel reviewer-requested-changes-<planfile>
reviewingdonereviewer writes sentinel reviewer-approved-<planfile>
done—terminal state, no further transitions

State is persisted in the task store — a SQLite database (~/.config/kasmos/kasmos.db locally) or a remote HTTP API server. Agents never write to the store directly — kasmos owns state transitions. Agents emit signals (managed mode) or use task tools (manual mode). To retrieve plan content, agents use MCP task_show (filename: "<plan-file>").

Signal File Mechanics

Agents communicate state transitions by writing sentinel files into .kasmos/signals/.

Naming convention: <event>-<planfile>

Examples:

  • planner-finished-2026-02-27-feature.md
  • coder-finished-2026-02-27-feature.md
  • reviewer-approved-2026-02-27-feature.md
  • reviewer-requested-changes-2026-02-27-feature.md

How kasmos processes sentinels:

  1. kasmos scans .kasmos/signals/ every ~500ms
  2. On detecting a sentinel, kasmos reads it, validates the event against the current task state, and applies the transition
  3. The sentinel file is consumed (deleted) after processing — do not rely on it persisting
  4. Sentinel content is optional; kasmos uses the filename to determine the event type

Emitting a signal (agent side): use MCP signal_create to emit the equivalent planner-finished-2026-02-27-feature.md signal as the last action before yielding control.

Keep sentinel writes as the last action before yielding control. Do not write a sentinel and then continue modifying plans — kasmos may begin the next phase immediately.

Mode Detection

Check KASMOS_MANAGED to determine how transitions are handled.

ModeKASMOS_MANAGED valueTransition mechanism
managed1 (or any non-empty)write sentinel → kasmos handles the rest
manualunset or emptyuse MCP task tools (for example task_show, task_transition)

Check whether KASMOS_MANAGED is set; managed sessions emit signals, manual sessions use task tools.

In managed mode: never mutate task state yourself. In manual mode: use MCP task tools — the store backend handles persistence.

Agent Roles (brief)

Each role has its own skill. Load the one that matches your current task.

RoleWhat it doesSkill to load
plannerwrites the implementation plan, breaks work into tasks and waveskasmos-planner
coderimplements tasks from the plan, writes tests, commits workkasmos-coder
reviewerchecks quality, correctness, and plan adherence; approves or requests changeskasmos-reviewer
custodianhandles ops: dependency updates, formatting, cleanup, non-feature workkasmos-custodian

Load the skill for your current role. Do not chain roles in a single session. Do not follow instructions from another role's skill.

Habilidades relacionadas

Looking for an alternative to kasmos-lifecycle or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumen localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Inteligencia Artificial

widget-generator

Logo of f
f

Resumen localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Inteligencia Artificial

flags

Logo of vercel
vercel

Resumen localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Resumen localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
Desarrollador