work-concernlisted

# Work / 5. Concern Answer this question: > What about the current implementation gives you pause? Identify only concrete > risks, weak assumptions, or user-facing failure modes supported by the code > and actual flow. What should be verified next before trusting it? Read [../QUALITY.md](../QUALITY.md) first. This is a lightweight, read-only judgment pass. Do not spawn agents, create goals, edit files, commit, deploy, or produce a full fix plan. Use `$work-audit` when the user wants exhaustive review, severity-ranked findings, or a detailed executor-ready remediation plan. ## Inspect 1. Use the target named by the user. Otherwise inspect the current diff, implementation discussed in the conversation, or the smallest relevant feature and its consumers. 2. Read local instructions, the implementation, existing tests, public APIs, call sites, and the actual user flow before forming a concern. 3. Check only material axes supported by the target: correctness, reliability, data integrity, permissions, security, destructive actions, persistence, error recovery, usability, maintainability, and meaningful test coverage. 4. Distinguish a verified concern from an unknown, tradeoff, taste judgment, or preference. Do not turn uncertainty into a finding. ## Judgment - Prefer two strong concerns over ten speculative ones. - Cite the exact path, symbol, behavior, test, or observation behind each concern. - Explain the realistic consequence, not an imaginary catastroph