migrate kickstart skill to mosaic-first paths

skills/kickstart/SKILL.md

@@ -38,7 +38,7 @@ Parse the argument (if any) provided after `/kickstart`:
 List open milestones and ask the user to choose:
 
 ```bash
-~/.claude/scripts/git/milestone-list.sh -s open
+"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/milestone-list.sh" -s open
 ```
 
 Present the results and ask:
@@ -69,7 +69,7 @@ ls docs/orchestrator-learnings.json 2>/dev/null
 git branch -r | grep -E 'origin/(develop|main)' | head -1
 ```
 
-Read the project's `CLAUDE.md` (if it exists) and scan for:
+Read the project's `AGENTS.md` first (and `SOUL.md` if present). If only `CLAUDE.md` exists, use it as compatibility fallback. Scan for:
 - Quality gate commands (look for `pnpm`, `npm`, `pytest`, `lint`, `typecheck`, `test`)
 - Branch conventions
 - Task prefix conventions
@@ -98,10 +98,10 @@ Ask the user to confirm or override any detected values.
 
 ```bash
 # Get all open issues in this milestone
-~/.claude/scripts/git/issue-list.sh -m "<milestone-name>" -s open
+"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-list.sh" -m "<milestone-name>" -s open
 
 # For each issue, get details (labels, description)
-~/.claude/scripts/git/issue-view.sh -i <number>
+"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-view.sh" -i <number>
 ```
 
 Categorize issues by labels (feature, bug, task, security, etc.) to determine phasing.
@@ -109,7 +109,7 @@ Categorize issues by labels (feature, bug, task, security, etc.) to determine ph
 ### For issue target
 
 ```bash
-~/.claude/scripts/git/issue-view.sh -i <number>
+"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-view.sh" -i <number>
 ```
 
 Read the issue description, labels, and any linked milestone.
@@ -130,10 +130,10 @@ Report status to user before continuing.
 **CRITICAL:** Read the full orchestrator guide:
 
 ```
-Read ~/.claude/agent-guides/orchestrator.md
+Read ~/.mosaic/guides/orchestrator.md
 ```
 
-Also load skills relevant to the project's tech stack from the dispatch table in `~/.claude/CLAUDE.md`. For example:
+Also load skills relevant to the project's tech stack from project docs (`AGENTS.md`/`SOUL.md`) plus `~/.mosaic/STANDARDS.md`. For example:
 - NestJS project → load `nestjs-best-practices`
 - Next.js project → load `next-best-practices`, `vercel-react-best-practices`
 - Python project → load `fastapi`, `python-performance-optimization`
@@ -199,14 +199,14 @@ Next task: MS-SEC-009 — "Add input validation to API endpoints"
 
 ## Step 5: Begin Orchestration
 
-You are now the **orchestrator**. Follow the protocol from `~/.claude/agent-guides/orchestrator.md` exactly.
+You are now the **orchestrator**. Follow the protocol from `~/.mosaic/guides/orchestrator.md` exactly.
 
 ### Standing Orders (baked in — user never needs to specify these)
 
 1. **All coding changes go through workers** — you NEVER edit source code directly
 2. **All coding changes require** code review, security review, and QA passing before completion
 3. **Linting is mandatory** — workers MUST run the project linter and fix ALL violations in files they touch. Zero lint errors. No disabling rules. No skipping files. This is non-negotiable.
-4. **Completed issues are closed** in the repo via `~/.claude/scripts/git/issue-close.sh`
+4. **Completed issues are closed** in the repo via `"${MOSAIC_HOME:-$HOME/.mosaic}/rails/git/issue-close.sh"`
 5. **tasks.md is the single source of truth** — you are the sole writer
 6. **Branch from `develop`** (or whatever was detected/confirmed in Step 1) as the upstream
 7. **Max 2 parallel workers** at any time
@@ -258,7 +258,7 @@ do NOT skip files. If you changed it, you lint it.
 
 ### Skills
 Read these before starting:
-- ~/.claude/skills/{relevant-skill}/SKILL.md
+- ~/.mosaic/skills/{relevant-skill}/SKILL.md
 
 ### Report Format
 When done, report as JSON:
@@ -282,7 +282,7 @@ To resume, run:
 /kickstart resume
 
 Or programmatically:
-claude -p "Read ~/.claude/skills/kickstart/SKILL.md then kickstart resume for project at $(pwd)"
+[runtime command] "Read ~/.mosaic/skills/kickstart/SKILL.md then kickstart resume for project at $(pwd)"
 
 State: docs/tasks.md (committed and pushed)
 Progress: X/Y tasks complete
@@ -295,7 +295,7 @@ Then STOP COMPLETELY. Do not continue working.
 
 ## Quality Gate Detection
 
-If the project CLAUDE.md doesn't specify quality gates, check for these patterns:
+If project docs (`AGENTS.md`/`SOUL.md`/`CLAUDE.md`) don't specify quality gates, check for these patterns:
 
 | File | Likely Quality Gates |
 |------|---------------------|
@@ -321,5 +321,5 @@ Examples: "pnpm lint && pnpm typecheck && pnpm test"
 
 - This skill transforms the current session — after kickstart, the agent IS the orchestrator
 - The skill itself is just setup instructions — the orchestrator guide has the full execution protocol
-- For programmatic use: `claude -p "Read ~/.claude/skills/kickstart/SKILL.md then kickstart milestone X for project at /path"`
-- Local-only skill (not in agent-skills repo) because it references `~/.claude/` paths
+- For programmatic use: pass this skill file path to your active runtime and request kickstart for the target repo.
+- This skill is runtime-agnostic and expects Mosaic rails/guides at `~/.mosaic`.