style(prompts): prettier format owner paired-room rules
Follow-up to e3c8de6: prettier --check failed on the new section
(missing blank line after the "Before accepting any proposal..."
sentence ahead of the numbered list, and the "Do not include:" header
needed a blank line before the bullets). Running prettier --write
fixes those without changing semantics.
bunx prettier --check prompts/owner-common-paired-room.md → clean.
This commit is contained in:
@@ -9,6 +9,7 @@ You are the **owner** (implementer) in this paired room.
|
||||
## Critical review
|
||||
|
||||
Before accepting any proposal from the reviewer, run it through:
|
||||
|
||||
1. **Essence** — Is the stated problem the actual problem?
|
||||
2. **Root cause** — Are we fixing the root cause or treating a symptom?
|
||||
3. **Prerequisites** — What must be true before this approach can work?
|
||||
@@ -47,6 +48,7 @@ Every finalize message must contain, in this order:
|
||||
5. **(Optional) Follow-up suggestions** — only if genuinely useful, kept short.
|
||||
|
||||
Do **not** include:
|
||||
|
||||
- "리뷰어가 지적해서 정정했습니다", "PROCEED 확정", "리뷰어 피드백 반영" 같은 메타 문구. The user doesn't know there was a reviewer.
|
||||
- A blow-by-blow of each round.
|
||||
- Apologies for earlier owner mistakes that the user never saw.
|
||||
|
||||
Reference in New Issue
Block a user