fix path

Author: chiang-daniel

.cursor/skills/specs/references/cmd_code_review.md

@@ -17,9 +17,9 @@ If something important is only in conversation history, that's a bug in the proc
 
 Always run as a sub-agent — spawned fresh, no prior context from coding.
 
-→ Read [references/spawning_subagents.md](references/spawning_subagents.md) for how to spawn sub-agents.
+→ Read [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) for how to spawn sub-agents.
 
-Pass the prompt from [references/cr_agent_prompt.md](references/cr_agent_prompt.md), plus scope description.
+Pass the prompt from [cr_agent_prompt.md](.cursor/skills/specs/references/cr_agent_prompt.md), plus scope description.
 
 ### Example invocation
 
@@ -65,5 +65,5 @@ The loop continues until clean.
 
 ## References
 
-- [references/spawning_subagents.md](references/spawning_subagents.md) — How to spawn sub-agents
-- [references/cr_agent_prompt.md](references/cr_agent_prompt.md) — Prompt passed to CR sub-agent
+- [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) — How to spawn sub-agents
+- [cr_agent_prompt.md](.cursor/skills/specs/references/cr_agent_prompt.md) — Prompt passed to CR sub-agent

.cursor/skills/specs/references/cmd_implement.md

@@ -63,8 +63,8 @@ You're willing to flag when a requirement leads to bad technical outcomes — bu
 7. **Run tests**. Iterate until passing.
 8. **Run automated checks again** (tests/fixes may introduce lint/format issues). Iterate until clean.
 9. **Self code-review via sub-agent**:
-   - → Read [references/spawning_subagents.md](references/spawning_subagents.md) for how to spawn
-   - Pass the prompt from [references/cr_agent_prompt.md](references/cr_agent_prompt.md) to the sub-agent
+   - → Read [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) for how to spawn
+   - Pass the prompt from [cr_agent_prompt.md](.cursor/skills/specs/references/cr_agent_prompt.md) to the sub-agent
    - Include: "A coding agent just implemented phase N of [project]. Review the changes using `git diff`. The spec for this project can be found [here](link_to_spec_folder)."
    - Iterate per CR Iteration Loop below
 10. **Run automated checks one final time** (CR fixes may introduce issues). Iterate until clean.
@@ -99,7 +99,7 @@ A lightweight coordinator that runs all remaining phases in sequence.
 
 1. Get next incomplete phase from `implementation_plan.md`
 2. Spawn a sub-agent with clean context to run the single-phase implementation flow above
-   - → Read [references/spawning_subagents.md](references/spawning_subagents.md) for how to spawn
+   - → Read [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) for how to spawn
    - Pass: phase number, project path, instruction to follow single-phase implementation
 3. **Auto-commit**: `"Phase N implementation of [project name]\n\n[description of work in phase]"`
 4. Show the phase summary from the subagent to the user
@@ -114,10 +114,10 @@ CR happens inside each phase's implementation loop, not at coordinator level.
 
 ### Passed to Phase Sub-Agents
 
-For implement-all, pass the content of [references/coding_phase_prompt.md](references/coding_phase_prompt.md) to each phase sub-agent. This prompt contains the full single-phase implementation instructions.
+For implement-all, pass the content of [coding_phase_prompt.md](.cursor/skills/specs/references/coding_phase_prompt.md) to each phase sub-agent. This prompt contains the full single-phase implementation instructions.
 
 ## References
 
-- [references/spawning_subagents.md](references/spawning_subagents.md) — How to spawn sub-agents
-- [references/coding_phase_prompt.md](references/coding_phase_prompt.md) — Prompt passed to coding sub-agents
-- [references/cr_agent_prompt.md](references/cr_agent_prompt.md) — Prompt passed to CR sub-agents
+- [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) — How to spawn sub-agents
+- [coding_phase_prompt.md](.cursor/skills/specs/references/coding_phase_prompt.md) — Prompt passed to coding sub-agents
+- [cr_agent_prompt.md](.cursor/skills/specs/references/cr_agent_prompt.md) — Prompt passed to CR sub-agents

.cursor/skills/specs/references/cmd_new_project.md

@@ -103,7 +103,7 @@ If they approve, mark `status: complete`. If they want changes, make them and as
 
 ## Step 2: Functional Spec
 
-→ Read [references/step_functional_spec.md](references/step_functional_spec.md) and follow it.
+→ Read [step_functional_spec.md](.cursor/skills/specs/references/step_functional_spec.md) and follow it.
 
 ## Step 3: UI Design (Conditional)
 
@@ -117,11 +117,11 @@ If they confirm, skip to Step 4.
 
 If UI is needed:
 
-→ Read [references/step_ui_design.md](references/step_ui_design.md) and follow it.
+→ Read [step_ui_design.md](.cursor/skills/specs/references/step_ui_design.md) and follow it.
 
 ## Step 4: Architecture
 
-→ Read [references/step_architecture.md](references/step_architecture.md) and follow it.
+→ Read [step_architecture.md](.cursor/skills/specs/references/step_architecture.md) and follow it.
 
 ## Step 5: Component Designs (Conditional)
 
@@ -132,7 +132,7 @@ During the architecture step, you'll decide whether component designs are needed
 
 If component designs are needed:
 
-→ Read [references/step_component_designs.md](references/step_component_designs.md) and follow it.
+→ Read [step_component_designs.md](.cursor/skills/specs/references/step_component_designs.md) and follow it.
 
 If not needed, proceed directly to Step 6.
 

.cursor/skills/specs/references/coding_phase_prompt.md

@@ -54,7 +54,7 @@ status: draft
 4. Run tests. Iterate until passing.
 5. Run automated checks again. Iterate until clean.
 6. Self code-review via sub-agent:
-   - Read `spec/references/cr_agent_prompt.md` for the CR process
+   - Read `.cursor/skills/specs/references/cr_agent_prompt.md` for the CR process
    - Spawn a CR sub-agent with clean context
    - Pass: "A coding agent just implemented phase N of [project]. Review using `git diff`."
    - Iterate per CR loop below
@@ -64,7 +64,7 @@ status: draft
 
 ## CR Iteration Loop
 
-1. Spawn CR sub-agent with the CR prompt from `spec/references/cr_agent_prompt.md`
+1. Spawn CR sub-agent with the CR prompt from `.cursor/skills/specs/references/cr_agent_prompt.md`
 2. CR returns feedback with severity labels
 3. If issues exist:
    - Fix each issue (or add a code comment explaining technical rationale)

.cursor/skills/specs/references/spawning_subagents.md

@@ -27,7 +27,7 @@ The sub-agent sees only what you pass it (a prompt) plus the repo. No conversati
 Use the `Task()` tool or equivalent sub-agent mechanism:
 
 ```python
-Task("Review this code using the guidelines in spec/references/cr_agent_prompt.md")
+Task("Review this code using the guidelines in .cursor/skills/specs/references/cr_agent_prompt.md")
 ```
 
 ### Cursor

.cursor/skills/specs/references/step_architecture.md

@@ -88,7 +88,7 @@ Communicate this decision to the user:
 
 ## Pushback
 
-→ Load [references/pushback.md](references/pushback.md) if not already loaded.
+→ Load [pushback.md](.cursor/skills/specs/references/pushback.md) if not already loaded.
 
 Challenge technical decisions:
 

.cursor/skills/specs/references/step_functional_spec.md

@@ -78,7 +78,7 @@ If you're unsure about something, ask. Don't guess.
 
 ## Pushback
 
-→ Load [references/pushback.md](references/pushback.md) if not already loaded.
+→ Load [pushback.md](.cursor/skills/specs/references/pushback.md) if not already loaded.
 
 After drafting the spec, review it and challenge:
 

.cursor/skills/specs/references/step_ui_design.md

@@ -54,7 +54,7 @@ Follow platform conventions. Users already know how standard patterns work — d
 
 ## Pushback
 
-→ Load [references/pushback.md](references/pushback.md) if not already loaded.
+→ Load [pushback.md](.cursor/skills/specs/references/pushback.md) if not already loaded.
 
 Challenge UX decisions: