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

v1.0.0
GitHub

このスキルについて

自動化された波動ベースの実装とプランライフサイクル管理が必要なAIコーディングエージェントに最適 ローカライズされた概要: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

機能

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

# 主なトピック

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

Skill Overview

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

自動化された波動ベースの実装とプランライフサイクル管理が必要なAIコーディングエージェントに最適 ローカライズされた概要: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

このスキルを使用する理由

プランライフサイクル、シグナルファイルメカニズム、モード検出を簡素化し、有限状態機械（FSM）遷移を使用することで、kasmos assignsとプランナー書き込みsentiを備えた効率的なAIワークフローにとって不可欠なツールとなる

おすすめ

自動化された波動ベースの実装とプランライフサイクル管理が必要なAIコーディングエージェントに最適

↓ 実現可能なユースケース for kasmos-lifecycle

プランライフサイクルを準備から計画および実装への遷移を自動化する
モード検出のためのシグナルファイルメカニズムを生成する
効率的なAIワークフローを実現するためのプランライフサイクルFSM遷移のデバッグ

! セキュリティと制限

  • kasmos assignsがプランにプランエージェントを割り当てる必要がある
  • 特定のFSM遷移（準備から計画、計画から実装）のみ有効
  • プランライフサイクル、シグナルファイルメカニズム、モード検出のみに限定

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.

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 とインストール手順

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

? よくある質問

kasmos-lifecycle とは何ですか？

自動化された波動ベースの実装とプランライフサイクル管理が必要なAIコーディングエージェントに最適 ローカライズされた概要: Covers plan lifecycle FSM, signal file mechanics, and mode detection only. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

kasmos-lifecycle はどうやって導入しますか？

次のコマンドを実行してください: npx killer-skills add kastheco/kasmos/kasmos-lifecycle。Cursor、Windsurf、VS Code、Claude Code など19以上のIDEで使えます。

kasmos-lifecycle の主な用途は？

主な用途は次のとおりです: プランライフサイクルを準備から計画および実装への遷移を自動化する, モード検出のためのシグナルファイルメカニズムを生成する, 効率的なAIワークフローを実現するためのプランライフサイクルFSM遷移のデバッグ。

kasmos-lifecycle に対応するIDEは？

このスキルは 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 に対応しています。統一された導入には Killer-Skills CLI を使えます。

kasmos-lifecycle に制限はありますか？

kasmos assignsがプランにプランエージェントを割り当てる必要がある. 特定のFSM遷移（準備から計画、計画から実装）のみ有効. プランライフサイクル、シグナルファイルメカニズム、モード検出のみに限定.

↓ このスキルの導入方法

  1. 1. ターミナルを開く

    プロジェクトディレクトリでターミナルまたはコマンドラインを開きます。

  2. 2. インストールコマンドを実行

    npx killer-skills add kastheco/kasmos/kasmos-lifecycle を実行してください。CLI がIDEまたはエージェントを自動検出し、スキルを設定します。

  3. 3. スキルを使い始める

    このスキルはすぐに有効になります。現在のプロジェクトで kasmos-lifecycle をすぐ使えます。

! 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

ローカライズされた概要: 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.

関連スキル

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

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

ローカライズされた概要: 🦞 # 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
AI

widget-generator

Logo of f
f

ローカライズされた概要: 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 Windsurf

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

ローカライズされた概要: 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
ブラウザ

pr-review

Logo of pytorch
pytorch

ローカライズされた概要: 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
開発者