Retro process reflection should include evaluation criteria for suggestions

[wtmoose]

Friction

Retro process reflection suggestions were naive — proposing reminders for rules that already exist, scoping fixes to the wrong system level, and proposing workarounds instead of identifying structural gaps. The retro guide asks for "concrete suggestions" but provides no criteria for evaluating whether a suggestion is sound.

Suggestion

Add evaluation criteria to the process reflection step. Before proposing a suggestion, the LLM should verify:

1. Does a rule already cover this? If so, this is a compliance failure, not a system gap — don't propose a new rule.
2. At what level does this belong? (policy = universal rule, guide = workflow-specific process, integration doc = project-specific values)
3. Is the suggestion addressing a structural gap, or is it a reminder/workaround?

Affected files

Guides/Process/dev-retro.md — Step 6 (Process reflection).

[wtmoose]

Implemented via working-docs/ticket-planning.md Phases A–F; closing as completed. See CHANGELOG.md Unreleased entries (2026-02-27/28).