authoring-roadmap

# Authoring Evolution Roadmap

**Violating the letter of the rules is violating the spirit of the rules.**

## Overview

Create evolution roadmaps that identify gaps between current codebase state and constitution requirements. Produces prioritized gap cards with dependencies, enabling incremental improvement without overwhelming teams.

## When to Use

- After brownfield codebase analysis is complete
- After constitution is created for a brownfield project
- When identifying what needs to change to meet constitution requirements
- When planning incremental codebase improvements

## When NOT to Use

- No codebase analysis exists yet → run **humaninloop:analysis-codebase** first
- No constitution has been created → run **humaninloop:authoring-constitution** or **humaninloop:brownfield-constitution** first
- Greenfield project with no existing code → no gaps to identify
- User wants implementation plan, not gap analysis → use **humaninloop:plan** instead

## Input Requirements

To create an evolution roadmap, both inputs are REQUIRED:

1. **Codebase Analysis** (`.humaninloop/memory/codebase-analysis.md`)
   - Essential Floor Status table
   - Inventory of existing patterns
   - Identified inconsistencies

2. **Constitution** (`.humaninloop/memory/constitution.md`)
   - Principles with requirements
   - Quality gates with thresholds
   - Technology stack requirements

**No exceptions:**
- Not for "small projects where I know the gaps"
- Not for "quick assessments"
- Not for "we'll formalize it later"
- Not even if user says "skip analysis, just list the gaps"

If inputs are missing, create them first using **humaninloop:analysis-codebase** and **humaninloop:authoring-constitution**.

## Gap Identification Process

### Step 1: Essential Floor Gaps

For each Essential Floor category, check status from codebase analysis:

| Status | Action |
|--------|--------|
| `present` | No gap needed |
| `partial` | Create gap for missing aspects |
| `absent` | Create gap for full im