Use this exact format when creating new roadmap feature files at docs/roadmap/features/<kebab-case-name>.md.
---
status: <Status>
issue: <issue number or empty>
---
# <Title>
## Problem
<What limitation, gap, or pain point this feature addresses.>
## What we're releasing
<How the feature solves the problem — the approach or architecture.>
## Expected outcome
<What users gain — the concrete benefit or outcome.>Every feature file starts with YAML frontmatter containing:
| Field | Required | Description |
|---|---|---|
status |
Yes | Current status — must match a value from scripts/conf/project.json |
issue |
No | GitHub issue number (leave empty if none) |
Status badge colors follow a darkwave/synthwave palette. Use these exact badge URLs based on feature status:




---
status: Planned
issue:
---
# Agent Harness
## Problem
In the first release, the Coding Agent Setup Doctor used a single agent to spot-check repositories for AI development setup issues, which limited the depth and consistency of findings.
## What we're releasing
Agent Harness introduces a coordinated agentic loop—similar to architectures used by Claude Code, Codex, and other coding agent platforms—allowing multiple specialized sub-agents to analyze repositories more thoroughly and validate findings collaboratively.
## Expected outcome
Users receive significantly more comprehensive and accurate setup diagnostics, with a system designed to continuously improve over time and serve as the foundation for reliable AI coding workflows.Convert the feature title to kebab-case:
- Lowercase all characters
- Replace spaces with hyphens
- Remove special characters (parentheses, colons, etc.)
- Collapse multiple hyphens into one
Examples:
| Title | Filename |
|---|---|
| Agent Harness | agent-harness.md |
| Coding Agent Setup Doctor | coding-agent-setup-doctor.md |
| GG Workflow | gg-workflow.md |
| Coding Agent Toolkit MCP (Serena) | coding-agent-toolkit-mcp.md |
| Secure Data Access Layer (unmcp) | secure-data-access-layer.md |
| [<Title>](./features/<filename>) | <Summary> |  | <issue> |
Where <issue> is either:
[#N](https://github.com/joggrdocs/home/issues/N)— linked GitHub issue-— no issue yet
For In progress in badge URLs, encode the space: In%20progress.