Levix0501/kiko-skills

`create-spec` turns the design into a build-ready spec — the delivery
contract a fresh context can implement and verify.

## 1. Locate the spec directory

Run `scripts/check-kiko` with the opened project root's absolute path as its
only argument, and use the returned path as `KIKO_ROOT`.

- Exit 3: ask the user to run the `setup-kiko` skill at the project root,
  then retry.
- Any other nonzero exit: report the error and stop.

Do not initialize or repair `.kiko`.

Orchestrate implementation from a spec: the controller dispatches fresh roles (subagents) to implement and review. The controller never implements, reviews, or fixes anything itself.

## 1 Workflow

Start with Step 1.

### Step 1: Check kiko workspace

Set `PROJECT_ROOT` to the opened project root's absolute path. Run `scripts/check-kiko` with `$PROJECT_ROOT` as its only argument, and use the returned path as `KIKO_ROOT`.

- Exit 3: ask the user to run the `setup-kiko` skill at the project root, then retry.
- Any other nonzero exit: report the error and stop.

Do not initialize or repair `.kiko`. On success, continue to Step 2.

## Workspace

Run `scripts/check-kiko` with the opened project root's absolute path as its only argument, and use the returned path as `KIKO_ROOT`. On exit 3, ask the user to run the `setup-kiko` skill at the project root, then retry. On any other nonzero exit, report the error and stop. Do not initialize or repair `.kiko`, and suggest no substitute for `setup-kiko`.

## Cut and pick

Take the request the user brings, which may be empty, together with what is waiting in `$KIKO_ROOT/TODO.md` as one whole, and cut it vertically into outcomes that are each verifiable on their own: a narrow but complete path through every layer it touches, never one layer of the whole. An outcome waits on the outcomes without which it cannot be delivered and accepted, and on no others; importance never overrides a dependency.

Importance is the mark an outcome carries: `[P0]` for what must ship for the work to count, `[P1]` for what must follow, `[P2]` for what can wait. An outcome inherits the highest mark among the outcomes that wait on it. Propose a mark for every outcome that has none.

Show the user the outcomes in the shape `$KIKO_ROOT/TODO.md` takes:

```md
# TODO

Run the bundled `scripts/init-kiko <project-root>` with the opened project root and report the path it prints. The script is idempotent: it creates any missing part of `.kiko/{TODO.md,docs/,.implement/,.gitignore}` while preserving existing artifacts and custom ignore content, so rerunning it also repairs an incomplete layout.

Initialize the root the user intends to work in — not a subdirectory and not a parent that happens to contain it. If the opened directory is ambiguous, ask the user to confirm the root first.

If the script warns that the root is not inside a Git worktree, tell the user Git has not been initialized there and the kiko artifacts are local-only; never run `git init` for them.

If the script exits with an error, show its message and stop; never create or repair `.kiko` by hand.