Summary
Daily normalization review of agentic workflow prompts found 26 report-generating workflows (out of 50 active in the last 24h that create issues/discussions/comments) that don't fully follow the project's markdown style guidelines for reports (see .github/skills/reporting/SKILL.md).
Two consistently good references to model changes on:
daily-repo-chronicle.mdaudit-workflows.md
Non-Compliant Workflows
| Workflow file |
H1/H2 headers found |
<details> used? |
Notes |
pr-sous-chef.md |
8 |
yes (2) |
Body still uses #/## — should be ###+ |
test-quality-sentinel.md |
8 |
yes (4) |
Same header issue |
impeccable-skills-reviewer.md |
6 |
yes (1) |
Same header issue |
mattpocock-skills-reviewer.md |
6 |
yes (5) |
Same header issue |
design-decision-gate.md |
10 |
yes (8) |
Same header issue |
squad-implement-worker.md |
5 |
none |
Missing progressive disclosure |
issue-monster.md |
9 |
yes (2) |
Same header issue |
squad.md |
7 |
none |
Missing progressive disclosure |
auto-triage-issues.md |
9 |
yes (3) |
Same header issue |
contribution-check.md |
10 |
yes (1) |
Same header issue |
aw-failure-investigator.md |
9 |
none |
Missing progressive disclosure |
pr-triage-agent.md |
6 |
yes (1) |
Same header issue |
daily-safe-outputs-conformance.md |
11 |
yes (2) |
Same header issue |
daily-news.md |
7 |
yes (2) |
Same header issue |
designer-drift-audit.md |
4 |
yes (2) |
Same header issue |
cli-version-checker.md |
10 |
yes (2) |
Same header issue |
static-analysis-report.md |
7 |
yes (2) |
Same header issue |
squad-game-planner.md |
3 |
none |
Missing progressive disclosure |
constraint-solving-potd.md |
5 |
yes (1) |
Same header issue |
sergo.md |
7 |
none |
Missing progressive disclosure |
daily-mcp-concurrency-analysis.md |
14 |
yes (2) |
Same header issue |
daily-function-namer.md |
16 |
yes (2) |
Same header issue |
daily-aw-cross-repo-compile-check.md |
16 |
yes (1) |
Same header issue |
daily-experiment-report.md |
17 |
yes (5) |
Same header issue |
daily-community-attribution.md |
13 |
yes (2) |
Same header issue |
agent-job-health.md |
7 |
yes (2) |
Same header issue |
Required Changes
For each workflow above:
- Header levels: Rewrite report/output-format sections so the highest heading level used is
### (h3). Demote any #/## headings to ###/####.
- Progressive disclosure: For workflows with 0
<details> usages (squad-implement-worker.md, squad.md, aw-failure-investigator.md, squad-game-planner.md, sergo.md), add <details><summary><b>...</b></summary> blocks around any long lists/logs so summaries stay scannable.
- Report structure guidance: Where the prompt doesn't already point at
.github/skills/reporting/SKILL.md, add an explicit reference (e.g. "Use the reporting skill when producing a report...") so the header/details rules are enforced consistently, matching daily-repo-chronicle.md and audit-workflows.md.
Example: Progressive Disclosure Pattern
### Summary
3 issues found needing attention.
<details>
<summary><b>View Full Details</b></summary>
- [ ] Issue A: ...
- [ ] Issue B: ...
- [ ] Issue C: ...
</details>
Design Principles
Per the Style Guidelines (Airbnb-inspired): keep critical information visible, push long detail behind <details>, and structure reports as overview → key metrics/issues → collapsible detail → next actions. Consistency across all 26 workflows above will make daily/weekly reports easier to scan and trust.
Next Steps
Generated by 🔧 Workflow Normalizer · auto · 40.3 AIC · ⌖ 2.1 AIC · ⊞ 11.3K · ◷
Summary
Daily normalization review of agentic workflow prompts found 26 report-generating workflows (out of 50 active in the last 24h that create issues/discussions/comments) that don't fully follow the project's markdown style guidelines for reports (see
.github/skills/reporting/SKILL.md).Two consistently good references to model changes on:
daily-repo-chronicle.mdaudit-workflows.mdNon-Compliant Workflows
<details>used?pr-sous-chef.md#/##— should be###+test-quality-sentinel.mdimpeccable-skills-reviewer.mdmattpocock-skills-reviewer.mddesign-decision-gate.mdsquad-implement-worker.mdissue-monster.mdsquad.mdauto-triage-issues.mdcontribution-check.mdaw-failure-investigator.mdpr-triage-agent.mddaily-safe-outputs-conformance.mddaily-news.mddesigner-drift-audit.mdcli-version-checker.mdstatic-analysis-report.mdsquad-game-planner.mdconstraint-solving-potd.mdsergo.mddaily-mcp-concurrency-analysis.mddaily-function-namer.mddaily-aw-cross-repo-compile-check.mddaily-experiment-report.mddaily-community-attribution.mdagent-job-health.mdRequired Changes
For each workflow above:
###(h3). Demote any#/##headings to###/####.<details>usages (squad-implement-worker.md,squad.md,aw-failure-investigator.md,squad-game-planner.md,sergo.md), add<details><summary><b>...</b></summary>blocks around any long lists/logs so summaries stay scannable..github/skills/reporting/SKILL.md, add an explicit reference (e.g. "Use thereportingskill when producing a report...") so the header/details rules are enforced consistently, matchingdaily-repo-chronicle.mdandaudit-workflows.md.Example: Progressive Disclosure Pattern
Design Principles
Per the Style Guidelines (Airbnb-inspired): keep critical information visible, push long detail behind
<details>, and structure reports as overview → key metrics/issues → collapsible detail → next actions. Consistency across all 26 workflows above will make daily/weekly reports easier to scan and trust.Next Steps
###+ in the 26 workflows listed<details>blocks to the 5 workflows with nonereportingskill in prompts lacking explicit report-structure guidancegh aw compile/make recompile)