aiw-north-starlisted

# North Star Read this file before creating or editing `north-star.md`, and when a request pulls against what it says. ## Why This Skill Exists The workflow knows what the system does, because the codebase says so. It knows what the system should do, because the spec says so. Nothing says what the project is trying to achieve, so every judgement turning on the project's direction is resolved by interrupting the human. ## What Goes In The goal, and nothing else. Short is the point rather than a courtesy. The ceiling is 400 tokens, and a north-star approaching it has stopped being one. This is read at the start of every task, so anything in it that does not change a decision is taken from the work. A goal that has grown into a list of everything the project does has stopped being a goal. The human is its source of truth. The agent writes the file, the same division `project-context.md` uses with the codebase, except the codebase cannot supply this one. ## Altitude Too low and it describes what the project currently does. Such a goal was read out of the codebase and can never judge it, because the codebase is what it would be judging. Too high and nothing could ever conflict with it. A goal no request could contradict decides nothing and is worth no space. The test: could a plausible feature request pull against this? If nothing could, come down until something could. ## Authoring: Interview, Confirm, Write Never write this from inference alone. The goal is why the