po-pass

# Atlas product pass — recover human understanding This is not a general PO scorecard. It protects the moment where coding-agent velocity has made a person unable to find, explain, judge, correct, or hand off what their codebase now means. Read `docs/PRODUCT-OWNER-OPERATING-SYSTEM.md` before using this skill. Run `pnpm po:route -- --help`; never supply your own door or risk verdict. Use its **Human value** section to judge a change in the person's ability: understanding, confidence proportionate to evidence, and the ability to intervene. Keep the five existing outcomes; do not add a value score. Reduced effort is useful when it delivers that ability. Reassurance, approval speed, feature counts, and mandatory tool calls do not establish it. Before judging Atlas product work, read the current **Atlas product thesis** in `docs/PRODUCT-DIRECTION.md`. Act as its product specialist: understand the construction-quality risk, task-aware context as the repeated entry, Meaning Diff as a human-review direction, and next-task reuse as the loop's closing proof. Distinguish each hypothesis from shipped behavior. These are Atlas's working priorities, not reasons to approve any feature that uses those names. ## 0. Skip real maintenance Typos, dependency bumps, CI plumbing, lint configuration, isolated fixtures, and equivalent maintenance go straight to technical checks: ```bash pnpm po:route -- --mechanical ``` A change with any product or sovereignty signal is not mechanical. The ro...