untangle-area

Installation
SKILL.md

Untangle one area

Run this only when a person asked for it by name. If you loaded it on your own, stop and ask first. Area: $ARGUMENTS (if empty, step 0 picks one after the map).

Core question, for every piece: should these pieces change together?

A codebase too big to hold at once gets untangled one area at a time. A whole-repo pass fails when thousands of files cannot fit in context; this version buys evidence with scripts and spends context on one area plus its direct import neighbours.

The output is a decision log and its tickets, not a stack of drive-by fixes. A fix lands through a lane and the gate, with a production-copy proof that the numbers did not move.

0. Set the area

Take the area from the argument. If none is given, run the map and pick the highest hotspot area with no completed decision log.

An area is a feature, not a folder: the screens, the services behind them, and their direct import neighbours.

Write docs/untangle/<area>.md as the primary handoff and the only durable memory of this area's run. A new session resumes from that file, not from a previous conversation. docs/untangle/cross-area.md is a separate shared index of links that cross areas (step 2), not part of this area's log.

Done when: the area name, its files, and the decision-log path are written at the top of docs/untangle/<area>.md.

Installs
1
First Seen
3 days ago