Problem
docs/memory/feature-flows.md is the index of vertical-slice flow docs and is meant to stay minimal and navigable. The /sync-feature-flows skill (Step 6) flags the index when it exceeds 400 lines and asks for a condensation pass.
As of 2026-06-26 the index is 527 lines — ~32% over the guideline. This is a long-standing, accumulating condition: each new feature appends a verbose multi-sentence row to the Recent Updates table (which never gets pruned), in addition to its category-table row. Individual sync runs correctly keep their own additions to one row, but no pass ever condenses the backlog, so the index grows unbounded.
Why it matters
- The index is loaded for navigation/orientation; a bloated index defeats its "minimal, navigable" purpose.
- The Recent Updates rows duplicate detail that already lives in the linked flow docs (the index should point, not narrate).
Proposed fix
- Trim the Recent Updates table — cap it at the most recent N entries (e.g. last ~15–20); older rows are already discoverable via their category-table entry + the flow doc itself.
- Shorten Recent Updates descriptions to one line that points at the flow doc, moving the multi-sentence detail (where not already there) into the doc.
- Re-check line count is back under 400 after the pass.
Acceptance criteria
Context
Surfaced during the /sync-feature-flows run for #1332. Not blocking that work — the #1332 entry itself stayed to a single row. This is the standing index-hygiene follow-up.
Problem
docs/memory/feature-flows.mdis the index of vertical-slice flow docs and is meant to stay minimal and navigable. The/sync-feature-flowsskill (Step 6) flags the index when it exceeds 400 lines and asks for a condensation pass.As of 2026-06-26 the index is 527 lines — ~32% over the guideline. This is a long-standing, accumulating condition: each new feature appends a verbose multi-sentence row to the Recent Updates table (which never gets pruned), in addition to its category-table row. Individual sync runs correctly keep their own additions to one row, but no pass ever condenses the backlog, so the index grows unbounded.
Why it matters
Proposed fix
Acceptance criteria
wc -l docs/memory/feature-flows.md< 400Context
Surfaced during the
/sync-feature-flowsrun for #1332. Not blocking that work — the #1332 entry itself stayed to a single row. This is the standing index-hygiene follow-up.