create-feature

# Create Feature Orchestrates complete feature creation using a 6-phase workflow. **Architecture Reference:** @../_shared/patterns.md ## Hook Marker (Required) Before editing any feature files, activate the skill marker so the PreToolUse hook allows edits: ```bash touch /tmp/.claude-kmpilot-skill-active ``` After Phase 5 completes (or on any early exit), remove it: ```bash rm -f /tmp/.claude-kmpilot-skill-active ``` ## Workflow **Phase 0** → **Phase 1** → **Phase 2** → [USER CONFIRMS] → **Phase 3** → [USER CONFIRMS] → **Activate marker** → **Phase 4** → **Phase 5** → **Remove marker** → Done ### Phase 0: Context Discovery (Auto) Detect: `PKG_PREFIX`, `INIT_KOIN_PATH`, `NAV_HOST_PATH` from existing features. See: @phases/phase-0-context.md ### Phase 1: Design Artifact Detection Check for a Stitch design blueprint: 1. **Check blueprint exists**: `.claude/docs/{featurename}/designs/{featurename}_blueprint.md` 2. **Check stitch-project.json**: `.claude/docs/_project/stitch-project.json` — read `features[featurename].blueprintConsumed` 3. **Determine mode**: | Blueprint exists? | `blueprintConsumed` | Mode | |-------------------|---------------------|------| | Yes | `false` | **Design-aware mode** — blueprint drives UI layer | | Yes | `true` | Normal mode — blueprint already consumed | | No | N/A | Normal mode — no design artifact | If entering **design-aware mode**, log: ``` Design artifact detected: .claude/docs/{featurename}/designs/{featurename}_blueprint.md Enteri...