You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| "create docs for...", "document this feature" | **Auto-chain** (see below) | `router.md` → `outline-generator.md` → `drafter.md` |
116
-
| "how do I update docs with this?", "update docs with this", "how should I update the documentation?" | **Auto-chain** (see below) | `router.md` → `outline-generator.md` → `drafter.md` |
117
-
| User provides source material (PR, diff, spec) + asks to document/update it | **Auto-chain** (see below) | `router.md` → `outline-generator.md` → `drafter.md` |
| "how do I update docs with this?", "update docs with this", "how should I update the documentation?" | **Auto-chain** (see below) | `router.md` → `outline-generator.md` → `drafter.md` → `outline-checker.md` + `style-checker.md` |
123
+
| User provides source material (PR, diff, spec) + asks to document/update it | **Auto-chain** (see below) | `router.md` → `outline-generator.md` → `drafter.md` → `outline-checker.md` + `style-checker.md` |
118
124
| User provides spec/story/ticket without instructions | **Router** (Create Mode) | `router.md` |
119
125
| User pastes Markdown without instructions | Ask: review or create? | — |
120
126
@@ -162,9 +168,32 @@ Step 2: DISPATCH targets (process in priority order: primary → required → op
162
168
└─ FOR EACH optional target:
163
169
└─ RUN Drafter in Micro-edit mode → produce Micro-edit artifact
164
170
165
-
Step 3: OUTPUT all deliverables as separate artifacts
171
+
Step 3: OUTPUT all Drafter deliverables as separate artifacts
172
+
173
+
Step 4: SELF-REVIEW (automatic, no pause)
174
+
├─ FOR EACH Drafter output:
175
+
│ ├─ Read outline-checker.md spec
176
+
│ ├─ RUN Outline Checker (template compliance)
177
+
│ ├─ IF action was create_page:
178
+
│ │ ├─ Read outline-ux-analyzer.md spec
179
+
│ │ └─ RUN UX Analyzer (reader experience)
180
+
│ ├─ Read style-checker.md spec
181
+
│ └─ RUN Style Checker (12 Rules compliance)
182
+
│
183
+
└─ COLLECT all review reports
184
+
185
+
Step 5: AUTO-CORRECT (conditional, max 1 retry per target)
186
+
├─ IF any review report contains errors:
187
+
│ ├─ FOR EACH target with errors:
188
+
│ │ ├─ Inject review report(s) as context
189
+
│ │ └─ RE-RUN Drafter (same mode) with corrections
2. **Do NOT stop after the Router to ask "should I continue?"** — the chain is automatic. Only pause for `ask_user` or critical errors.
174
203
3. **Output each deliverable as a separate Markdown artifact** with a descriptive title (e.g., "Routing Report — MCP Server feature", "Draft — cms/features/mcp-server.md").
175
204
4. **State the chain upfront.** At the start, tell the user what will run:
5. **Style Checker is deferred by default.** In auto-chain, the goal is to produce drafts quickly. Offer the Style Checker as a follow-up after delivery, unless the user explicitly asked for a "full review".
5. **Self-review runs automatically after the Drafter.** The Outline Checker, UX Analyzer (for `create_page` targets), and Style Checker run on every Drafter output. If errors or warnings are found, the Drafter re-runs once with the review reports as context. Suggestions are appended as review notes but do not trigger a retry. Maximum 1 retry per target — never more.
178
207
6. **Handle multiple targets sequentially.** Process primary targets first, then required, then optional.
179
208
7. **Respect `conditional` targets.** Do not process them until the condition is resolved.
209
+
8. **Self-review severity threshold.** `[error]` and `[warning]` findings trigger a Drafter retry. Only `[suggestion]` findings are reported without causing re-runs. This prevents infinite loops while catching clear rule violations (e.g., "easy/simple" slipping through, missing backticks on file paths, procedures not in numbered lists).
180
210
181
211
### When Outline Generator is needed vs. straight to Drafter
182
212
@@ -240,7 +270,7 @@ Always tell the user which prompt is executing and in which mode:
240
270
241
271
> "Running **Style Checker** on `account-billing.md`..."
> "Running **Outliner** (Full Review: Checker + UX Analyzer) on `admin-configuration-customization.md` — new file, 1103 lines..."
246
276
@@ -831,6 +861,6 @@ tags: [...]
831
861
6. **[ux-low]** Nice-to-have UX improvement
832
862
```
833
863
834
-
**Create / Update Mode output:** A series of artifacts produced by the auto-chain (Routing Report, Outline Report if applicable, Draft/Patch/Micro-edit for each target). No consolidated report — each artifact stands alone.
864
+
**Create / Update Mode output:** A series of artifacts produced by the auto-chain (Routing Report, Outline Report if applicable, Draft/Patch/Micro-edit for each target, Self-Review Report). Each artifact stands alone. The Self-Review Report consolidates findings from Outline Checker, UX Analyzer, and Style Checker. If errors triggered a Drafter retry, the corrected artifacts replace the originals and the Self-Review Report notes which targets were corrected.
835
865
836
-
**Behavioral rules:** Determine mode first. State mode explicitly. Execute prompts in sequence. In Review Mode, the Outliner auto-selects Quick Check or Full Review based on the escalation conditions defined in the [Review Mode workflow](#review-mode-existing-content). In auto-chain mode, do not pause between steps unless `ask_user` is set. Deduplicate issues across prompts. Prioritize errors → warnings → ux-high → suggestions → ux-medium → ux-low.
866
+
**Behavioral rules:** Determine mode first. State mode explicitly. Execute prompts in sequence. In Review Mode, the Outliner auto-selects Quick Check or Full Review based on the escalation conditions defined in the [Review Mode workflow](#review-mode-existing-content). In auto-chain mode, do not pause between steps unless `ask_user` is set. After the Drafter, run Self-Review automatically (Outline Checker + UX Analyzer for new pages + Style Checker). If errors are found, re-run the Drafter once per target with review reports as context. Deduplicate issues across prompts. Prioritize errors → warnings → ux-high → suggestions → ux-medium → ux-low.
| "create docs for...", "document this feature" |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`|
110
-
| "how do I update docs with this?", "update docs with this", "how should I update the documentation?" |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`|
111
-
| User provides source material (PR, diff, spec) + asks to document/update it |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`|
115
+
| "create docs for...", "document this feature" |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`→ `outline-checker.md` + `style-checker.md`|
116
+
| "how do I update docs with this?", "update docs with this", "how should I update the documentation?" |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`→ `outline-checker.md` + `style-checker.md`|
117
+
| User provides source material (PR, diff, spec) + asks to document/update it |**Auto-chain** (see below) |`router.md` → `outline-generator.md` → `drafter.md`→ `outline-checker.md` + `style-checker.md`|
112
118
| User provides spec/story/ticket without instructions |**Router** (Create Mode) |`router.md`|
113
119
| User pastes Markdown without instructions | Ask: review or create? | — |
114
120
@@ -156,9 +162,32 @@ Step 2: DISPATCH targets (process in priority order: primary → required → op
156
162
└─ FOR EACH optional target:
157
163
└─ RUN Drafter in Micro-edit mode → produce Micro-edit artifact
158
164
159
-
Step 3: OUTPUT all deliverables as separate artifacts
165
+
Step 3: OUTPUT all Drafter deliverables as separate artifacts
166
+
167
+
Step 4: SELF-REVIEW (automatic, no pause)
168
+
├─ FOR EACH Drafter output:
169
+
│ ├─ Read outline-checker.md spec
170
+
│ ├─ RUN Outline Checker (template compliance)
171
+
│ ├─ IF action was create_page:
172
+
│ │ ├─ Read outline-ux-analyzer.md spec
173
+
│ │ └─ RUN UX Analyzer (reader experience)
174
+
│ ├─ Read style-checker.md spec
175
+
│ └─ RUN Style Checker (12 Rules compliance)
176
+
│
177
+
└─ COLLECT all review reports
178
+
179
+
Step 5: AUTO-CORRECT (conditional, max 1 retry per target)
180
+
├─ IF any review report contains errors:
181
+
│ ├─ FOR EACH target with errors:
182
+
│ │ ├─ Inject review report(s) as context
183
+
│ │ └─ RE-RUN Drafter (same mode) with corrections
2.**Do NOT stop after the Router to ask "should I continue?"** — the chain is automatic. Only pause for `ask_user` or critical errors.
168
197
3.**Output each deliverable as a separate Markdown artifact** with a descriptive title (e.g., "Routing Report — MCP Server feature", "Draft — cms/features/mcp-server.md").
169
198
4.**State the chain upfront.** At the start, tell the user what will run:
5.**Style Checker is deferred by default.**In auto-chain, the goal is to produce drafts quickly. Offer the Style Checker as a follow-up after delivery, unless the user explicitly asked for a "full review".
5.**Self-review runs automatically after the Drafter.**The Outline Checker, UX Analyzer (for `create_page` targets), and Style Checker run on every Drafter output. If errors or warnings are found, the Drafter re-runs once with the review reports as context. Suggestions are appended as review notes but do not trigger a retry. Maximum 1 retry per target — never more.
172
201
6.**Handle multiple targets sequentially.** Process primary targets first, then required, then optional.
173
202
7.**Respect `conditional` targets.** Do not process them until the condition is resolved.
203
+
8.**Self-review severity threshold.**`[error]` and `[warning]` findings trigger a Drafter retry. Only `[suggestion]` findings are reported without causing re-runs. This prevents infinite loops while catching clear rule violations (e.g., "easy/simple" slipping through, missing backticks on file paths, procedures not in numbered lists).
174
204
175
205
### When Outline Generator is needed vs. straight to Drafter
176
206
@@ -234,7 +264,7 @@ Always tell the user which prompt is executing and in which mode:
234
264
235
265
> "Running **Style Checker** on `account-billing.md`..."
> "Running **Outliner** (Full Review: Checker + UX Analyzer) on `admin-configuration-customization.md` — new file, 1103 lines..."
240
270
@@ -825,6 +855,6 @@ tags: [...]
825
855
6.**[ux-low]** Nice-to-have UX improvement
826
856
```
827
857
828
-
**Create / Update Mode output:** A series of artifacts produced by the auto-chain (Routing Report, Outline Report if applicable, Draft/Patch/Micro-edit for each target). No consolidated report — each artifact stands alone.
858
+
**Create / Update Mode output:** A series of artifacts produced by the auto-chain (Routing Report, Outline Report if applicable, Draft/Patch/Micro-edit for each target, Self-Review Report). Each artifact stands alone. The Self-Review Report consolidates findings from Outline Checker, UX Analyzer, and Style Checker. If errors triggered a Drafter retry, the corrected artifacts replace the originals and the Self-Review Report notes which targets were corrected.
829
859
830
-
**Behavioral rules:** Determine mode first. State mode explicitly. Execute prompts in sequence. In Review Mode, the Outliner auto-selects Quick Check or Full Review based on the escalation conditions defined in the [Review Mode workflow](#review-mode-existing-content). In auto-chain mode, do not pause between steps unless `ask_user` is set. Deduplicate issues across prompts. Prioritize errors → warnings → ux-high → suggestions → ux-medium → ux-low.
860
+
**Behavioral rules:** Determine mode first. State mode explicitly. Execute prompts in sequence. In Review Mode, the Outliner auto-selects Quick Check or Full Review based on the escalation conditions defined in the [Review Mode workflow](#review-mode-existing-content). In auto-chain mode, do not pause between steps unless `ask_user` is set. After the Drafter, run Self-Review automatically (Outline Checker + UX Analyzer for new pages + Style Checker). If errors are found, re-run the Drafter once per target with review reports as context. Deduplicate issues across prompts. Prioritize errors → warnings → ux-high → suggestions → ux-medium → ux-low.
0 commit comments