kadai

Create a kadai item (epic, feature, story, or task) with prompts for missing fields

Disable kadai in the current project. Hooks no-op, mutating CLI commands error, MCP mutating tools refuse, web viewer shows a DISABLED banner. Reads still work.

Re-enable kadai in the current project. Hooks resume gating, mutating commands work again, web banner clears.

Pick a kadai story for active work (sets it as picked AND transitions to in_progress)

Render all descendant story plans of an epic, feature, or story as one composite markdown document.

Use INSTEAD OF superpowers:brainstorming when working in any repository that contains a `.kadai/` directory. Runs the full brainstorming flow (explore → questions → approaches → design → user approval → spec → self-review) AND then plumbs the result into the kadai spine: auto-creates the epic if missing, creates a feature, attaches the spec to the feature as `spec.md`. The single visible artifact at the end is a feature in `.kadai/epics/<E>/features/<F>/` with `spec.md` attached, NOT a free-floating `docs/superpowers/specs/*.md`. If you load `superpowers:brainstorming` in a kadai repo, you'll write specs into the wrong place and lose the spec → plan → implementation provenance kadai is designed to capture.

Use when verifying that kadai's full integration (skill auto-trigger + PreToolUse/PostToolUse hooks + MCP server + change capture + status updates) works end-to-end. Spawns a fresh `claude -p` session in a temp dir to exercise the Path A acceptance test from the kadai design spec §10. Useful after kadai upgrades, install changes, or when something feels off about hooks/MCP/skill behavior.

Autonomous executor for kadai-tracked work. Picks up where kadai-writing-plans leaves off — walks the picked story's plan task-by-task, dispatches an implementer subagent for each ### Task block, runs spec + code-quality reviews per task, marks tasks done as it goes. Pauses for human review at story boundaries. When an implementer reports BLOCKED with reason `needs-feature: <desc>`, surfaces a prompt to plan a fast-follow-up unblocker via kadai-brainstorming, executes the unblocker, then resumes the original story. State persisted in `.kadai/runner.json`; resumable across sessions via `kadai run --resume`.

Use INSTEAD OF superpowers:writing-plans when writing implementation plans inside a kadai-tracked repo (`.kadai/` present). Decomposes the feature into kadai stories, writes one `plan.md` per story directly into the spine (`.kadai/.../stories/<id>/plan.md`), and creates one real kadai task for each `### Task N` block. Auto-picks the first story when done. Without this wrapper you'll produce a single freeform plan that someone has to translate into spine items by hand.

Required when working in any repository that contains a `.kadai/` directory — including brainstorming, designing, scoping, planning, building, or implementing anything (MVPs, features, prototypes, fixes, websites, scripts). Load this skill at the START of the session, before invoking brainstorming/writing-plans or writing any files. Kadai enforces a guardrail (edits outside the spine + allowlist are blocked when no story is picked) and tracks the spec→plan→implementation trail in `.kadai/`. If you skip this skill, you'll write specs/plans into the wrong place and lose the provenance kadai is designed to capture.