Phase-End Self-Check

Walk through these six questions. For each, answer "yes/no/n-a" and act on the "yes" answers before moving on.

Iron-1 trigger: Did the user's most recent intent contain "逐個 / 仔細 / 全部 / 不要省略 / thoroughly / each / all / every", or was the task security-related? If yes → for the rest of this work, no shortcuts.
Subagent hygiene (Iron-2): Did you call a subagent in this phase, or are you about to? If yes → confirm the prompt has both: (a) a word cap appropriate to the depth (≤200 / ≤800 / ≤2000) and (b) an escape clause "but report anomalies in full regardless of cap".
Repeated edits (Iron-3): Did you make the same string edit twice or more? If yes → switch to perl -i -pe 's|old|new|g' files... and run git diff.
Templating (Habit): Did you plan N similar tasks? If yes → look for the largest common factor; if templatable, validate on one sample before bulk producing.
Context size: Is the conversation context noticeably large or are you crossing a phase boundary? If yes → consider /compact to drop early raw output.
Memory candidate: Is there an observation from this phase worth long-term memory — a rule learned, a decision rationale, an external resource pointer, a project-state change? If yes → write it as a feedback / project / reference memory, with a "why" line so future sessions can judge if it's still load-bearing.

phase-self-check