Summary
Apply the unified branding agent to all Markdown files in the repository. Fix broken, duplicate, or missing footers, headers, and badges. Validate all outputs against the schema from Wave 4D and ensure consistency with category-based rules.
Related Issues
Parent planning:
Upstream work:
- #[4C] — Current-state audit (remediation recommendations)
- #[4D] — Schema & config implementation
- #[4E] — Unified branding agent
Execution sequence:
- Previous: #[4E] (agent implementation)
- Current issue: 4F (remediation & validation)
- Final: Schema compliance across repository ✅
Objectives
Scope
In Scope
- Applying the branding agent to all
.md files
- Fixing duplicates and inconsistent patterns from Wave 4C audit
- Adding missing footers/headers where expected by category
- Validating all outputs against schema
- Updating frontmatter categories where needed
- Creating validation/remediation report
Out of Scope
- Further schema changes (Wave 4D is final)
- Agent implementation changes (Wave 4E is final)
- Non-Markdown branding logic
Deliverables
-
Remediated .md Files
- All files with fixed, category-appropriate footers/headers/badges
- Frontmatter updated where categories were missing or incorrect
- 100% schema validation passing
- No duplicate or malformed patterns
-
Remediation Report (remediation-report.md)
- Summary of changes by priority tier
- Files remediated by category
- Common patterns fixed
- Before/after examples
- Validation results
-
Validation Report (validation-report.md)
- Schema compliance metrics
- All files passing validation
- Any fallback rules applied
- Category distribution post-remediation
-
Frontmatter Audit (if needed)
- Files needing category frontmatter additions
- Path-based category inference accuracy
- Fallback rules applied
Acceptance Criteria
Definition of Done
Owner
Claude Code (AI Team - Review & UX)
Dependencies
Awaits:
- #[4E] (agent implementation) — COMPLETE
- Wave 4E agent must be working and testable
Effort Estimate
3–4 hours (scanning, applying agent, validating, reporting)
Summary
Apply the unified branding agent to all Markdown files in the repository. Fix broken, duplicate, or missing footers, headers, and badges. Validate all outputs against the schema from Wave 4D and ensure consistency with category-based rules.
Related Issues
Parent planning:
Upstream work:
Execution sequence:
Objectives
.mdfilesScope
In Scope
.mdfilesOut of Scope
Deliverables
Remediated
.mdFilesRemediation Report (
remediation-report.md)Validation Report (
validation-report.md)Frontmatter Audit (if needed)
Acceptance Criteria
.mdfiles scanned for branding complianceDefinition of Done
.mdfilesOwner
Claude Code (AI Team - Review & UX)
Dependencies
Awaits:
Effort Estimate
3–4 hours (scanning, applying agent, validating, reporting)