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

v1.0.0
GitHub

Sobre este Skill

Perfeito para Agentes de Codificação de IA que necessitam de implementação automatizada baseada em ondas e gerenciamento de ciclo de vida de planos. Resumo localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Recursos

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
------ ---- -----------------

# Core Topics

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

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
35
Canonical Locale
en
Detected Body Locale
en

Perfeito para Agentes de Codificação de IA que necessitam de implementação automatizada baseada em ondas e gerenciamento de ciclo de vida de planos. Resumo localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Por que usar essa habilidade

Habilita os agentes a simplificar os ciclos de vida dos planos, a mecânica de arquivos de sinal e a detecção de modo usando transições de Máquina de Estado Finito (FSM), tornando-o uma ferramenta essencial para fluxos de trabalho de IA eficientes com kasmos assigns e planner writes senti.

Melhor para

Perfeito para Agentes de Codificação de IA que necessitam de implementação automatizada baseada em ondas e gerenciamento de ciclo de vida de planos.

↓ Casos de Uso Práticos for kasmos-lifecycle

Automatizar transições do ciclo de vida do plano de pronto para planejamento e implementação
Gerar mecânica de arquivos de sinal para detecção de modo
Depurar transições do ciclo de vida do FSM para fluxos de trabalho de IA eficientes

! Segurança e Limitações

  • Exige que kasmos assigns um agente de planejamento ao plano
  • Somente válido para transições de FSM específicas (pronto para planejamento, planejamento para implementação)
  • Limitado ao ciclo de vida do plano, mecânica de arquivos de sinal e detecção de modo

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

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 & Installation Steps

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

? Frequently Asked Questions

What is kasmos-lifecycle?

Perfeito para Agentes de Codificação de IA que necessitam de implementação automatizada baseada em ondas e gerenciamento de ciclo de vida de planos. Resumo localizado: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install kasmos-lifecycle?

Run the command: npx killer-skills add kastheco/kasmos/kasmos-lifecycle. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for kasmos-lifecycle?

Key use cases include: Automatizar transições do ciclo de vida do plano de pronto para planejamento e implementação, Gerar mecânica de arquivos de sinal para detecção de modo, Depurar transições do ciclo de vida do FSM para fluxos de trabalho de IA eficientes.

Which IDEs are compatible with kasmos-lifecycle?

This skill is compatible with 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. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for kasmos-lifecycle?

Exige que kasmos assigns um agente de planejamento ao plano. Somente válido para transições de FSM específicas (pronto para planejamento, planejamento para implementação). Limitado ao ciclo de vida do plano, mecânica de arquivos de sinal e detecção de modo.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add kastheco/kasmos/kasmos-lifecycle. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use kasmos-lifecycle immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

kasmos-lifecycle

Resumo 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 is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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 tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumo 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
Inteligência Artificial

widget-generator

Logo of f
f

Resumo 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
Inteligência Artificial

flags

Logo of vercel
vercel

Resumo 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

Resumo 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
Desenvolvedor