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
A daily style normalization review identified 42 out of 51 reporting workflows that do not follow the project's markdown formatting guidelines.
Review Period: Last 24 hours of active workflows Reviewed: 51 reporting workflows Non-compliant: 42 (82%) Compliant: 9 (18%)
Issues Found
Two categories of non-compliance were identified:
Prompt uses h1/h2 headers - Workflow prompts structure their own sections with # and ## headers. Per the Report Structure Guidelines, all report output headers should start at ### or lower.
No progressive disclosure guidance - Workflows generating reports do not instruct agents to wrap long lists/details in <details> blocks.
Non-Compliant Workflows
View all 42 non-compliant workflows
Workflow
h1 in prompt
h2 in prompt
Missing <details> guidance
Missing h3+ output guidance
audit-workflows.md
x
x
x
x
daily-agentrx-trace-optimizer.md
x
x
x
x
daily-ambient-context-optimizer.md
x
x
x
x
daily-aw-cross-repo-compile-check.md
x
x
x
x
daily-awf-spec-compiler-surfacing.md
x
x
x
x
daily-cache-strategy-analyzer.md
x
x
-
-
daily-cli-performance.md
x
x
x
x
daily-code-metrics.md
x
x
-
-
daily-community-attribution.md
x
x
x
x
daily-compiler-quality.md
x
x
x
x
daily-doc-healer.md
x
x
x
x
daily-experiment-report.md
x
x
x
x
daily-file-diet.md
x
x
x
x
daily-firewall-report.md
x
x
x
x
daily-formal-spec-verifier.md
x
x
x
x
daily-function-namer.md
x
x
x
x
daily-geo-optimizer.md
x
x
x
x
daily-hippo-learn.md
x
x
x
x
daily-issues-report.md
x
x
x
x
daily-mcp-concurrency-analysis.md
x
x
x
-
daily-model-inventory.md
x
x
x
x
daily-model-resolution.md
x
x
x
x
daily-multi-device-docs-tester.md
x
x
x
x
daily-news.md
x
x
x
x
daily-observability-report.md
x
x
x
x
daily-performance-summary.md
x
x
x
x
daily-regulatory.md
x
x
x
x
daily-reliability-review.md
x
x
x
x
daily-repo-chronicle.md
x
x
x
x
daily-safe-output-optimizer.md
x
x
x
x
daily-safe-outputs-conformance.md
x
x
x
x
daily-safeoutputs-git-simulator.md
x
x
x
x
daily-secrets-analysis.md
x
x
x
-
daily-sentrux-report.md
x
x
x
x
daily-skill-optimizer.md
x
x
x
x
daily-spdd-spec-planner.md
x
-
x
x
daily-syntax-error-quality.md
x
x
x
x
daily-team-evolution-insights.md
x
x
x
x
daily-team-status.md
x
x
-
-
daily-token-consumption-report.md
x
x
x
x
org-health-report.md
x
x
x
x
static-analysis-report.md
x
x
x
x
Legend: x = issue present, - = not applicable or partially addressed
Required Changes
For each non-compliant workflow, two types of changes are needed:
1. Replace h1/h2 prompt structure with h3+
Before:
# Daily Workflow Report## Mission
Describe goal...
## Output Format
After:
### Daily Workflow Report#### Mission
Describe goal...
#### Output Format
2. Add progressive disclosure guidance for report output
Add a ## Report Structure Guidelines section instructing the agent:
## Report Structure Guidelines- Use `###` (or lower) headers only.
- Keep summary and critical actions visible; move long detail into `<details>` blocks.
- Structure reports as: overview to key metrics/issues to collapsible detail to next actions.
Good Examples to Reference
daily-repo-chronicle.md - uses ### headers in output examples
daily-cache-strategy-analyzer.md - includes <details> guidance
Overview
A daily style normalization review identified 42 out of 51 reporting workflows that do not follow the project's markdown formatting guidelines.
Review Period: Last 24 hours of active workflows
Reviewed: 51 reporting workflows
Non-compliant: 42 (82%)
Compliant: 9 (18%)
Issues Found
Two categories of non-compliance were identified:
#and##headers. Per the Report Structure Guidelines, all report output headers should start at###or lower.<details>blocks.Non-Compliant Workflows
View all 42 non-compliant workflows
<details>guidanceaudit-workflows.mddaily-agentrx-trace-optimizer.mddaily-ambient-context-optimizer.mddaily-aw-cross-repo-compile-check.mddaily-awf-spec-compiler-surfacing.mddaily-cache-strategy-analyzer.mddaily-cli-performance.mddaily-code-metrics.mddaily-community-attribution.mddaily-compiler-quality.mddaily-doc-healer.mddaily-experiment-report.mddaily-file-diet.mddaily-firewall-report.mddaily-formal-spec-verifier.mddaily-function-namer.mddaily-geo-optimizer.mddaily-hippo-learn.mddaily-issues-report.mddaily-mcp-concurrency-analysis.mddaily-model-inventory.mddaily-model-resolution.mddaily-multi-device-docs-tester.mddaily-news.mddaily-observability-report.mddaily-performance-summary.mddaily-regulatory.mddaily-reliability-review.mddaily-repo-chronicle.mddaily-safe-output-optimizer.mddaily-safe-outputs-conformance.mddaily-safeoutputs-git-simulator.mddaily-secrets-analysis.mddaily-sentrux-report.mddaily-skill-optimizer.mddaily-spdd-spec-planner.mddaily-syntax-error-quality.mddaily-team-evolution-insights.mddaily-team-status.mddaily-token-consumption-report.mdorg-health-report.mdstatic-analysis-report.mdLegend: x = issue present, - = not applicable or partially addressed
Required Changes
For each non-compliant workflow, two types of changes are needed:
1. Replace h1/h2 prompt structure with h3+
Before:
After:
2. Add progressive disclosure guidance for report output
Add a
## Report Structure Guidelinessection instructing the agent:Good Examples to Reference
daily-repo-chronicle.md- uses###headers in output examplesdaily-cache-strategy-analyzer.md- includes<details>guidancedaily-architecture-diagram.md- compliant prompt structuredaily-security-red-team.md- compliant (uses h3+ headers)Next Steps
###/####for section headers<details>) guidance to output format sectionsdaily-repo-chronicle,daily-issues-report,daily-firewall-report,daily-observability-reportGenerated by workflow-normalizer
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.