Design-phase orchestrator for a single spec. Precondition: requirements.md already exists for {feature-name} (produced by /kiro-start or /kiro-spec-requirements). Acts as an orchestrator: the controller handles deterministic resolution, the precondition gate, the default-branch guard, the initial commit, and an interactive design discussion, while delegating design generation + design validation to a single non-interactive subagent. Portable across repos: deterministically resolves the specs root, skill base directory, git remote, and default branch (fixed priority orders, no guessing). Does NOT create branches or worktrees — feature branches are supplied by the Claude Code harness worktree. When the current branch is the repository default branch it STOPs and asks the developer to re-run inside the harness worktree (a non-default working branch); otherwise it runs kiro-spec-design (with -y), runs kiro-validate-design non-interactively, commits the generated design to the current branch without pushing, and t
Post-discovery single-spec entry point. Precondition: /kiro-discovery has already created {specs-root}/{feature-name}/brief.md, so the feature name is already confirmed. Acts as an orchestrator: the controller handles deterministic resolution, the precondition gate, the default-branch guard, the initial commit, and an interactive requirements discussion, while delegating spec init + requirements generation + gap analysis to a single non-interactive subagent. Portable across repos: deterministically resolves the specs root, skill base directory, git remote, and default branch (fixed priority orders, no guessing). Does NOT create branches or worktrees — feature branches are supplied by the Claude Code harness worktree. When the current branch is the repository default branch it STOPs and asks the developer to re-run inside the harness worktree (a non-default working branch); otherwise it initializes the spec via kiro-spec-init (which consumes brief.md), runs kiro-spec-requirements, runs kiro-validate-gap, commi
pasta-ghost-authoring
ekicyou/pasta
Pasta DSL文法リファレンスと辞書制作パターン集。ゴースト（「伺か」デスクトップマスコット）の 辞書ファイル（.pasta）を作成・編集する際に、自然言語の指示からPasta DSLコードへの変換を サポートする。 USE FOR: pasta, Pasta DSL, .pasta, ゴースト, 辞書, トーク作成, シーン作成, アクション行, 単語定義, 変数, イベントハンドラ, ランダムトーク, アクター辞書, さくらスクリプト, 伺か, ukagaka, ghost authoring, dictionary file, talk creation, scene definition, pasta script, pasta code generation, 時報, OnHour, 時報変数, 日時変数, date variables, hour variables. DO NOT USE FOR: pasta料理, cooking pasta, Pasta DSLパーサー開発, pasta_dsl crate, pasta_lua crate, pasta_core crate, Rustクレート実装, SHIORIプロトコル実装, Luaランタイム開発, pasta言語仕様の設計変更.
pasta-lua-coding
ekicyou/pasta
pasta.dll Luaランタイム APIリファレンスとコーディング規約。 ゴーストの scripts/ 配下のカスタムLuaスクリプトや、 Pasta DSL内のLuaブロック実装を支援する。 USE FOR: pasta lua, pasta_lua, Lua API, Luaスクリプト, scripts/, pasta_scripts/, 単語辞書一括投入, WORD.create, イベントハンドラ, REG, RES, 永続化, @pasta_persistence, save, @pasta_search, @pasta_config, @pasta_sakura_script, @enc, @pasta_log, ロギング, logging, log, trace, debug, info, warn, error, ACT, SCENE, STORE, GLOBAL, SAVE, lua_test, luacheck, mocks, lua_test.mocks, モックライブラリ, mock install, mock reset, pasta lua coding, pasta runtime API. DO NOT USE FOR: Pasta DSL文法, .pastaファイル編集, pasta_dsl crate, pasta_core crate, Rustクレート実装, 汎用Luaプログラミング, SHIORIプロトコル実装.
