karvey-importlisted

# Karvey Import — convert Kiro / gstack specs into Karvey ## Purpose Bring pre-existing specifications from **Kiro** (cc-sdd) or **gstack** into the Karvey `docs/spec/` structure, so they can continue through the Karvey pipeline. This is a **cross-cutting support skill** (cross-cutting layer): it does **NOT** advance `spec.json:phase` of any change — it materializes the imported documents and leaves the change at the phase its content supports. It is **idempotent and non-destructive**: it never deletes the source (`.kiro/`, gstack docs); it only creates/updates files under `docs/spec/`. Generated artifacts follow the project's language (per `spec.json` `language`). ## Mode selection - `--from kiro` → import from a Kiro `.kiro/` directory. - `--from gstack` → import from gstack artifacts (design docs, specs, plans). - If `--from` is omitted, detect: if a `.kiro/` directory exists → kiro; otherwise ask the user which source to use. --- ## Step 1 — Ensure project config Read `docs/spec/project.json` (see `karvey/rules/project-config.md`). If it does not exist, create it (or run `/karvey-init`'s project-config step): ask/infer `git_platform`, `cloud`, `iac_tool`, `knowledge_sync`, `targets`, `repos` (min 1), `spec_repo`, `branch_flow`. For Kiro, pre-fill `targets`/stack from `.kiro/steering/tech.md` if present. --- ## Step 2A — Import from Kiro (`--from kiro`) Kiro layout (source): ``` .kiro/ ├── steering/{product.md, tech.md, structure.md, ...} ← project-level conte