🎨 style(markdown): format all markdown files with prettier

- 使用 prettier 格式化所有 markdown 文件
- prose-wrap: always, print-width: 80
- 保持代码块和表格格式
- 提升可读性和一致性

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

codex/skills/create-plan/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: create-plan
-description: Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
+description:
+  Create a concise plan. Use when a user explicitly asks for a plan related to a
+  coding task.
 metadata:
   short-description: Create a plan
 ---
@@ -9,36 +11,42 @@ metadata:
 
 ## Goal
 
-Turn a user prompt into a **single, actionable plan** delivered in the final assistant message.
+Turn a user prompt into a **single, actionable plan** delivered in the final
+assistant message.
 
 ## Minimal workflow
 
-Throughout the entire workflow, operate in read-only mode. Do not write or update files.
+Throughout the entire workflow, operate in read-only mode. Do not write or
+update files.
 
 1. **Scan context quickly**
-
-   - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`, `ARCHITECTURE.md`).
+   - Read `README.md` and any obvious docs (`docs/`, `CONTRIBUTING.md`,
+     `ARCHITECTURE.md`).
    - Skim relevant files (the ones most likely touched).
-   - Identify constraints (language, frameworks, CI/test commands, deployment shape).
+   - Identify constraints (language, frameworks, CI/test commands, deployment
+     shape).
 
 2. **Ask follow-ups only if blocking**
-
    - Ask **at most 1–2 questions**.
-   - Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
+   - Only ask if you cannot responsibly plan without the answer; prefer
+     multiple-choice.
    - If unsure but not blocked, make a reasonable assumption and proceed.
 
 3. **Create a plan using the template below**
-
    - Start with **1 short paragraph** describing the intent and approach.
-   - Clearly call out what is **in scope** and what is **not in scope** in short.
+   - Clearly call out what is **in scope** and what is **not in scope** in
+     short.
    - Then provide a **small checklist** of action items (default 6–10 items).
-     - Each checklist item should be a concrete action and, when helpful, mention files/commands.
+     - Each checklist item should be a concrete action and, when helpful,
+       mention files/commands.
      - **Make items atomic and ordered**: discovery → changes → tests → rollout.
      - **Verb-first**: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
-   - Include at least one item for **tests/validation** and one for **edge cases/risk** when applicable.
+   - Include at least one item for **tests/validation** and one for **edge
+     cases/risk** when applicable.
    - If there are unknowns, include a tiny **Open questions** section (max 3).
 
-4. **Do not preface the plan with meta explanations; output only the plan as per template**
+4. **Do not preface the plan with meta explanations; output only the plan as per
+   template**
 
 ## Plan template (follow exactly)
 
@@ -54,12 +62,7 @@ Throughout the entire workflow, operate in read-only mode. Do not write or updat
 
 ## Action items
 
-[ ] <Step 1>
-[ ] <Step 2>
-[ ] <Step 3>
-[ ] <Step 4>
-[ ] <Step 5>
-[ ] <Step 6>
+[ ] <Step 1> [ ] <Step 2> [ ] <Step 3> [ ] <Step 4> [ ] <Step 5> [ ] <Step 6>
 
 ## Open questions
 
@@ -74,7 +77,8 @@ Good checklist items:
 
 - Point to likely files/modules: src/..., app/..., services/...
 - Name concrete validation: “Run npm test”, “Add unit tests for X”
-- Include safe rollout when relevant: feature flag, migration plan, rollback note
+- Include safe rollout when relevant: feature flag, migration plan, rollback
+  note
 
 Avoid: