From 92ffdac9ef9b327481acc7bc07bf540704e9d7f5 Mon Sep 17 00:00:00 2001
From: aniruddh10124 <88266561+aniruddh10124@users.noreply.github.com>
Date: Mon, 6 Jul 2026 16:05:26 +0530
Subject: [PATCH] Fix formatting issues in SKILL.md

The prompt given to the sub-agent should be indented.
---
 plan-design-review/SKILL.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/plan-design-review/SKILL.md b/plan-design-review/SKILL.md
index e81f7f12a..8aff094e2 100644
--- a/plan-design-review/SKILL.md
+++ b/plan-design-review/SKILL.md
@@ -1396,11 +1396,11 @@ cat "$TMPERR_DESIGN" && rm -f "$TMPERR_DESIGN"
 Dispatch a subagent with this prompt:
 "Read the plan file at [plan-file-path]. You are an independent senior product designer reviewing this plan. You have NOT seen any prior review. Evaluate:
 
-1. Information hierarchy: what does the user see first, second, third? Is it right?
-2. Missing states: loading, empty, error, success, partial — which are unspecified?
-3. User journey: what's the emotional arc? Where does it break?
-4. Specificity: does the plan describe SPECIFIC UI ("48px Söhne Bold header, #1a1a1a on white") or generic patterns ("clean modern card-based layout")?
-5. What design decisions will haunt the implementer if left ambiguous?
+  1. Information hierarchy: what does the user see first, second, third? Is it right?
+  2. Missing states: loading, empty, error, success, partial — which are unspecified?
+  3. User journey: what's the emotional arc? Where does it break?
+  4. Specificity: does the plan describe SPECIFIC UI ("48px Söhne Bold header, #1a1a1a on white") or generic patterns ("clean modern card-based layout")?
+  5. What design decisions will haunt the implementer if left ambiguous?
 
 For each finding: what's wrong, severity (critical/high/medium), and the fix."