Merge pull request #1175 from Kiln-AI/dchiang/fix-spec-skill-path

Fix skill spec path reference

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

@@ -52,7 +52,7 @@ If the target phase is already complete (checkbox checked in `implementation_pla
 
 Spawn a new coding sub-agent using the Initial Coding Prompt template below.
 
-→ 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.
 
 The coding agent returns either:
 - A summary indicating it's ready for code review
@@ -69,7 +69,7 @@ The coding agent returns either:
    - Spawn a new CR sub-agent, passing prior feedback in a `<prior_cr_feedback>` block
    - Repeat until CR returns clean
 
-→ 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.
 
 ### Step 3: Commit
 
@@ -114,7 +114,7 @@ You are a coding agent implementing a phase of a spec-driven project.
 **Phase:** [N]
 **Project specs:** [specs/projects/PROJECT_NAME/]
 
-Read `skill/references/coding_phase_prompt.md` for your full instructions. Follow them precisely.
+Read `.cursor/skills/specs/references/coding_phase_prompt.md` for your full instructions. Follow them precisely.
 
 Return a short summary of what you built when implementation is complete and ready for code review.
 ```
@@ -144,7 +144,7 @@ Return the commit message you used.
 ```
 Review code changes for phase [N] of the project at [specs/projects/PROJECT_NAME/].
 
-Read `skill/references/cr_agent_prompt.md` for your full review instructions. Follow them precisely.
+Read `.cursor/skills/specs/references/cr_agent_prompt.md` for your full review instructions. Follow them precisely.
 ```
 
 For re-reviews, append:
@@ -167,6 +167,6 @@ When the manager receives a roadblock message:
 
 ## References
 
-- [references/spawning_subagents.md](references/spawning_subagents.md) — How to spawn and resume sub-agents
-- [references/coding_phase_prompt.md](references/coding_phase_prompt.md) — Full instructions for coding sub-agents
-- [references/cr_agent_prompt.md](references/cr_agent_prompt.md) — Full instructions for CR sub-agents
+- [spawning_subagents.md](.cursor/skills/specs/references/spawning_subagents.md) — How to spawn and resume sub-agents
+- [coding_phase_prompt.md](.cursor/skills/specs/references/coding_phase_prompt.md) — Full instructions for coding sub-agents
+- [cr_agent_prompt.md](.cursor/skills/specs/references/cr_agent_prompt.md) — Full instructions for 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/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 skill/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: