refactor: replace {installed_path} with relative paths in quick-dev skill

Skills resolve paths relative to the skill root directory per the
open agent standard, so the installed_path variable is unnecessary.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-01-clarify-and-route.md

@@ -48,5 +48,5 @@ spec_file: '' # set at runtime before leaving this step
 
 ## NEXT
 
-- One-shot / ready-for-dev: Read fully and follow `{installed_path}/steps/step-03-implement.md`
-- Plan-code-review: Read fully and follow `{installed_path}/steps/step-02-plan.md`
+- One-shot / ready-for-dev: Read fully and follow `./steps/step-03-implement.md`
+- Plan-code-review: Read fully and follow `./steps/step-02-plan.md`

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-02-plan.md

@@ -2,7 +2,7 @@
 name: 'step-02-plan'
 description: 'Investigate, generate spec, present for approval'
 
-templateFile: '{installed_path}/tech-spec-template.md'
+templateFile: './tech-spec-template.md'
 wipFile: '{implementation_artifacts}/tech-spec-wip.md'
 deferred_work_file: '{implementation_artifacts}/deferred-work.md'
 ---
@@ -36,4 +36,4 @@ Present summary. If token count exceeded 1600 and user chose [K], include the to
 
 ## NEXT
 
-Read fully and follow `{installed_path}/steps/step-03-implement.md`
+Read fully and follow `./steps/step-03-implement.md`

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-03-implement.md

@@ -32,4 +32,4 @@ Otherwise (`execution_mode = "plan-code-review"`): hand `{spec_file}` to a sub-a
 
 ## NEXT
 
-Read fully and follow `{installed_path}/steps/step-04-review.md`
+Read fully and follow `./steps/step-04-review.md`

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-04-review.md

@@ -46,7 +46,7 @@ Do NOT `git add` anything — this is read-only inspection.
    - **reject** — noise. Drop silently. When unsure between defer and reject, prefer reject — only defer findings you are confident are real.
 3. Process findings in cascading order. If intent_gap or bad_spec findings exist, they trigger a loopback — lower findings are moot since code will be re-derived. If neither exists, process patch and defer normally. Increment `{specLoopIteration}` on each loopback. If it exceeds 5, HALT and escalate to the human. On any loopback, re-evaluate routing — if scope has grown beyond one-shot, escalate `execution_mode` to plan-code-review.
    - **intent_gap** — Root cause is inside `<frozen-after-approval>`. Revert code changes. Loop back to the human to resolve, then re-run steps 2–4.
-   - **bad_spec** — Root cause is outside `<frozen-after-approval>`. Before reverting code: extract KEEP instructions for positive preservation (what worked well and must survive re-derivation). Revert code changes. Read the `## Spec Change Log` in `{spec_file}` and strictly respect all logged constraints when amending the non-frozen sections that contain the root cause. Append a new change-log entry recording: the triggering finding, what was amended, the known-bad state avoided, and the KEEP instructions. Read fully and follow `{installed_path}/steps/step-03-implement.md` to re-derive the code, then this step will run again.
+   - **bad_spec** — Root cause is outside `<frozen-after-approval>`. Before reverting code: extract KEEP instructions for positive preservation (what worked well and must survive re-derivation). Revert code changes. Read the `## Spec Change Log` in `{spec_file}` and strictly respect all logged constraints when amending the non-frozen sections that contain the root cause. Append a new change-log entry recording: the triggering finding, what was amended, the known-bad state avoided, and the KEEP instructions. Read fully and follow `./steps/step-03-implement.md` to re-derive the code, then this step will run again.
    - **patch** — Auto-fix. These are the only findings that survive loopbacks.
    - **defer** — Append to `{deferred_work_file}`.
    - **reject** — Drop silently.
@@ -54,4 +54,4 @@ Do NOT `git add` anything — this is read-only inspection.
 
 ## NEXT
 
-Read fully and follow `{installed_path}/steps/step-05-present.md`
+Read fully and follow `./steps/step-05-present.md`

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/workflow.md

@@ -81,10 +81,9 @@ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `
 
 ### 2. Paths
 
-- `installed_path` = the directory containing this workflow.md file (the skill's base directory)
-- `templateFile` = `{installed_path}/tech-spec-template.md`
+- `templateFile` = `./tech-spec-template.md`
 - `wipFile` = `{implementation_artifacts}/tech-spec-wip.md`
 
 ### 3. First Step Execution
 
-Read fully and follow: `{installed_path}/steps/step-01-clarify-and-route.md` to begin the workflow.
+Read fully and follow: `./steps/step-01-clarify-and-route.md` to begin the workflow.