kiro-powers: mirror the skill changes from #197

integrations/docs/kiro-powers.md

@@ -21,7 +21,6 @@ The `integrations/kiro-powers/` folder is a [Kiro power](https://kiro.dev/docs/p
 | `kane-cli run` steering | `integrations/kiro-powers/steering/kane-cli-run.md` | Full reference for one-shot `kane-cli run`: objective patterns + checkpoint analyze methods (Visual / Textual-DOM / URL / Title / DevTools→Network/Console/Performance/Cookies/localStorage), full flag table, NDJSON parsing (including `project_folder_auto_defaulted`), results presentation, failure diagnosis, parallel execution, project/folder management (`projects`/`folders list|create`, auto-default gate). |
 | `kane-cli testmd` steering | `integrations/kiro-powers/steering/kane-cli-testmd.md` | Full reference for `kane-cli testmd`: file format, frontmatter (incl. `tags:`), `@import`, replay/author cache, `Result.md`, CI patterns, parse errors, generate → testmd pipeline. |
 | `kane-cli testrun` + evidence steering | `integrations/kiro-powers/steering/kane-cli-testrun.md` | Full reference for `kane-cli testrun run` (selection, preflight, parallel, dry-run, typed `testrun_*` NDJSON events, exit codes) and the evidence-pack surface (`evidence serve/validate/merge`, pack locations, the stderr view hint). |
-| `kane-cli generate` steering | `integrations/kiro-powers/steering/kane-cli-generate.md` | Full reference for `kane-cli generate`: the three modes (new / refine / save), attaching files (`--files`), clarification round-trips, the refine→save→run loop, typed NDJSON event schema (`generate_*`), result presentation, the generate → testmd handoff. |
 | `kane-cli fair-evaluation` steering | `integrations/kiro-powers/steering/kane-cli-fair-evaluation.md` | How to compare Kane CLI to other approaches honestly: like-for-like lifecycle phases (authoring vs the alternative's script *creation*; replay vs execution; plus locator-break repair + ongoing maintenance), the comparison traps (replay is zero-LLM, the sunk-cost trap, phase mismatch), and what Kane CLI is purpose-built for. |
 | `kane-cli mobile` steering | `integrations/kiro-powers/steering/kane-cli-mobile.md` | Full reference for driving a native mobile app (locally on macOS Apple Silicon, or on the cloud grid from any machine): the `--target desktop\|emulator\|simulator` axis (desktop/browser is the default), `--device-name` / `--os-version` / `--app` selection, the required app under test (build or `APP…` id), one-time local setup + `kane-cli doctor` / `devices list`, the flat `_test.md` `target:` + `app:` (+ `device_name:`/`os_version:`) frontmatter keys, mobile members in `testrun` and `testrun run --remote` (grid rules and preflight codes), and the web-only checkpoint carve-out. |
 | `kane-cli assurance` steering | `integrations/kiro-powers/steering/kane-cli-assurance.md` | Full reference for the assurance flow: requirement docs → `context ingest`/`extract` → review checkpoints → `design tests` → author → `testrun` → `cover`, the `--mode agent` pause loop (exit 3 = resumable), the review checkpoints, and `maintain reconcile`. |
@@ -41,18 +40,16 @@ The canonical skill is a thin `SKILL.md` (7 sections, ~300 lines) plus on-demand
 | `references/agent-config.md`: saved preferences location, schema, shell read and write, hard-case rules, changing preferences later | `steering/kane-cli-first-run.md` → Saved preferences **and** `POWER.md` → Every session (the read command, first-session detection, watch mode values) |
 | `references/cards.md`: rules for every card, passed, failed, didn't start, stopped early, possible product bug, saved test, suite (local and cloud grid) | `steering/kane-cli-run.md` → Presenting results (rules + the five one-shot run cards) **and** `steering/kane-cli-testmd.md` → The saved test card **and** `steering/kane-cli-testrun.md` → Presenting results (suite card, failed-tests table, cloud grid rows) |
 | `references/live-strip.md`: the live status strip (Claude Code only) | One sentence in `POWER.md` → Every session saying the strip is Claude Code only and not offered in Kiro. Do **not** document the strip commands in the power |
-| `SKILL.md` §2 Decision tree | `steering/kane-cli-run.md` → Decision tree, `steering/kane-cli-testmd.md` → When to recommend `testmd`, and `steering/kane-cli-generate.md` → When to recommend `generate` |
-| `SKILL.md` §3 Building a `run` command — flags, exit codes, examples, bare-objective guardrail | `POWER.md` → Command reference (condensed) **and** `steering/kane-cli-run.md` → Full flag reference |
+| `SKILL.md` §2 Decision tree | `steering/kane-cli-run.md` → Decision tree, `steering/kane-cli-testmd.md` → When to recommend `testmd`, and `steering/kane-cli-assurance.md` for every test-case authoring ask |
+| `SKILL.md` §3 Building a `run` command — flags, exit codes, examples, bare-objective guardrail, unresolved variables and the fill-before-any-run recipe | `POWER.md` → Command reference (condensed) **and** `steering/kane-cli-run.md` → Full flag reference + Variables and secrets |
 | `SKILL.md` §4 Writing objectives — three patterns, "store as", do/don't | `steering/kane-cli-run.md` → Writing objectives — three patterns |
 | `SKILL.md` §5 Parsing `--agent` output — essentials (includes `project_folder_auto_defaulted` in typed events) | `steering/kane-cli-run.md` → Parsing the NDJSON output (Event types + Parsing strategy summary) |
-| `SKILL.md` §6 Generate test cases (authoring — no browser) | `POWER.md` → Overview (the third "way Kiro uses it") **and** all of `steering/kane-cli-generate.md` |
+| `SKILL.md` §6 Test cases from a description (no requirement document) | `POWER.md` → Overview (the third "way Kiro uses it") **and** `steering/kane-cli-testmd.md` → Authoring from a description **and** `steering/kane-cli-assurance.md` |
 | `SKILL.md` §7 When to read which reference | Kiro analogue: `POWER.md`'s steering-file mapping (POWER.md tells Kiro when to load each steering file) |
 | `references/objectives-cookbook.md` — analyze methods (Visual / Textual-DOM / URL / Title / DevTools→Network/Console/Performance/Cookies/localStorage), operators, chaining, pitfalls, worked examples | `steering/kane-cli-run.md` → Analyze methods — picking the right checkpoint (plus the existing Combining patterns, Assertion specificity, and Do / Don't sections) |
-| `references/testmd.md`: testmd file format, replay & cascade, `@import`, commands, parse errors, gate-fires-before-launch note, the saved-test stream table (`test_md_step_start` through `test_md_done`) | All of `steering/kane-cli-testmd.md` (the stream table lives under Replay policy and completion → The saved-test stream) |
-| `references/generate.md` — generate modes, attaching files (`--files`), refine→save→run loop, clarification handling, Functional-only save, generate→testmd handoff | All of `steering/kane-cli-generate.md` |
-| `references/generate-parsing.md` — typed `generate_*` event schema (incl. `generate_upload`), terminal `generate_done`, exit codes | `steering/kane-cli-generate.md` → Parsing the NDJSON output + Terminal `generate_done` + Exit codes |
+| `references/testmd.md`: testmd file format, replay & cascade, `@import`, commands, parse errors, gate-fires-before-launch note, the saved-test stream table (`test_md_step_start` through `test_md_done`) | All of `steering/kane-cli-testmd.md` (the stream table lives under Replay policy and completion → The saved-test stream); authoring from a description points at the assurance steering |
 | `references/parsing.md`: the 0.8.17+ stream contract (`stream_start`, `v`, `ts`, ignore unknown fields and event types, typeless step lines, completion event last, `events.ndjson` and the active-run pointer file), full NDJSON event schemas (`project_folder_auto_defaulted`, `bifurcation`, `child_agent_*`, `ask_user`, complete `run_end` fields incl. `credits_consumed`) | `steering/kane-cli-run.md` → Parsing the NDJSON output (The stream contract + full event-type list + Terminal `run_end` event) |
-| `references/test-manager.md`: project/folder agent surface (`projects list|create`, `folders list|create` with the **required** `--project <id>`, NDJSON wire shape, pagination), run-startup auto-default gate, `project_folder_auto_defaulted` event, self-healing for stale IDs, the global "changing where results go" flow | `POWER.md` → Step 3 (project/folder onboarding) **and** `steering/kane-cli-run.md` → Browsing / creating projects and folders + The run-startup auto-default gate + Changing where results go **and** `steering/kane-cli-testmd.md` → Quick start (gate note) **and** `steering/kane-cli-generate.md` → Configuration surface (gate note) |
+| `references/test-manager.md`: project/folder agent surface (`projects list|create`, `folders list|create` with the **required** `--project <id>`, NDJSON wire shape, pagination), run-startup auto-default gate, `project_folder_auto_defaulted` event, self-healing for stale IDs, the global "changing where results go" flow | `POWER.md` → Step 3 (project/folder onboarding) **and** `steering/kane-cli-run.md` → Browsing / creating projects and folders + The run-startup auto-default gate + Changing where results go **and** `steering/kane-cli-testmd.md` → Quick start (gate note) |
 | `references/debug.md` — log layout, debugging flow, common failure patterns (incl. "did you mean" subcommand and self-healing rows), bug-report heuristic | `steering/kane-cli-run.md` → Failure handling & log inspection + Bug-report heuristic |
 | `references/parallel.md` — when to split, agent prompt template, batch summary | `steering/kane-cli-run.md` → Parallel execution |
 | `references/testrun.md`: batch runs: selection (paths/`--match`/`--tags`), preflight reasons, `--remote` (HyperExecute jobs, `remote_*` events, remote preflight codes, the 0.8.17+ remote additions), mobile members, `testrun_*` event schema (incl. `session_id`, `log_path`, `failure`, the authored member pair, `testrun_progress`), each test's own log and the `--stream-members` rule, suite card presentation, exit codes | All of `steering/kane-cli-testrun.md` |