critique-form

name	critique-form
description	Red-team review of a draft Questionnaire before publish. Checks for redundancy, reading-level issues, burden, missing red-flag screens, license problems, and bias. Use when the user says "review this form" or as a self-check before proposing a major change.

Critique form

When to use this

• The user explicitly asks for a review.
• You're about to propose a heavy edit and want to sanity-check it first (write to notes.md, don't surface to the user unless they asked).
• A form is being moved from draft → active.

Checklist

Redundancy

• Does any pair of items measure the same construct? (e.g. PHQ-2 inside a form that already has PHQ-9.)
• Are demographic items duplicated across groups?

Reading level

• Aim for 6th-grade English on patient-facing text.
• Avoid clinical jargon ("dyspnea" → "shortness of breath"; "syncope" → "fainting").
• Run any candidate text through a basic Flesch-Kincaid mental estimate.

Burden

• Total item count after enableWhen pruning at the median patient.
• Estimated time to complete (ballpark: 4-6 sec/item for booleans, 10-15 sec/item for free text, more for thinking-heavy items).
• Flag forms above ~10 minutes; suggest splitting or moving items to follow-up.

Red-flag screens

• For symptom-focused forms (headache, chest pain, abdominal pain, shortness of breath): is there a red-flag screen?
• Are the questions actionable (drives a triage decision) vs data-collection-only?

License

• Any inlined items from copyrighted instruments?
• Attribution preserved on instruments that require it?
• Any modifications to copyrighted items (forbidden)?

Bias / safety

• Any item that pathologizes normal experience?
• Pediatric / geriatric / pregnancy-specific items in a form intended for the general adult population (or vice versa)?
• Trauma-relevant questions: is there an opt-out or a content warning?

Technical

• All linkIds unique and kebab-case.
• All required items have plausible coding.
• enableWhen targets reference linkIds that exist.
• No mixing of enableWhen and enableWhenExpression on the same item.

Output

Write findings to output/issues.json:

[
  {
    "severity": "warning",
    "category": "redundancy",
    "linkId": "phq2",
    "message": "PHQ-2 is a subset of PHQ-9, which already appears at section-3."
  }
]

Severities: info | warning | error. Drop linkId for form-level issues.

Pitfalls

• Critiquing without reading the whole form. Read all sections before listing issues.
• Confusing "burden" with "thoroughness." A 50-question form may be the right answer for a comprehensive intake. State the use-case before flagging burden.
• Confidently asserting a license issue without checking. If unsure, flag as info and ask in reply.md.