aiw-housekeepinglisted

Makes keeping the project clean and well organised a step in the workflow rather than something that happens when someone notices. Use this skill at the done gate, third after aiw-verification and aiw-validation, before presenting any work for the human's done decision, and on every task including one that set out to remove or move nothing. It asks whether anything the task caused should now be removed or moved: a code path the change orphaned, a file the work left behind, a thing sitting in the wrong place. Use it also on its own, over the whole repository, when the human asks what has built up, asks for a cleanup or a tidy-up or an audit of the repository, wonders what all these leftover files are, or when a session-start note reports the repository hiding paths through a local exclude rule. In that mode it examines the whole repository and hands back a ranked list for the human to approve, rather than acting on what it finds. It owns the footprint that bounds what may be acted on, the tiering that sets wha
philippe-ths/ai-coding-workflow · ★ 0 · AI & Automation · score 66

Install: claude install-skill philippe-ths/ai-coding-workflow

# Housekeeping Read this file at the done gate, after aiw-verification and aiw-validation, before presenting work for the human's done decision. ## Why This Skill Exists The workflow already knows how to remove things safely. aiw-ground-truth gives a delete its oracle, the absence of remaining dependencies. aiw-verification's Delete modality gives that oracle its search. ai-workflow.md says what to do with a finding outside the task. Every one of those fires only once the agent has already decided to remove something. Nothing asks. So a task ends with the paths it killed still standing, because removing them was never anyone's job at the moment they died. That moment is the cheap one, and it is the only point where someone still holds the reason the thing became dead. A session later a dead path and a deliberate extension point are indistinguishable, and telling them apart costs more than the mess does. What is not removed then is removed in a sitting, or never. This skill is the asking. It adds no rules about how to remove; it delegates that. ## Two Ways In **At the done gate**, on every task, over the footprint below. This is the ordinary case, and the rest of this file assumes it unless a section says otherwise. **Invoked on its own**, over the whole repository. The human asking is what puts you here and is sufficient by itself, and a session-start note is the other way in. A task may well be in flight; the audit is simply not about it. The footprint does not appl