231 lines
4.2 KiB
Markdown
231 lines
4.2 KiB
Markdown
# Closer Question Quality Checklist v2
|
|
|
|
**See also:** [QUESTION_CONTENT_GUIDE.md](QUESTION_CONTENT_GUIDE.md) — writing philosophy, voice & tone | [QUESTION_SCHEMA.md](QUESTION_SCHEMA.md) — JSON schema & validation rules | [QUESTION_REWRITE_PLAN.md](QUESTION_REWRITE_PLAN.md) — rewrite checklist & category order
|
|
|
|
## Purpose
|
|
|
|
This checklist prevents technically valid but boring questions from reaching the app.
|
|
|
|
Passing JSON validation is not enough.
|
|
|
|
Every question must also feel human, useful, and worth answering.
|
|
|
|
## Automatic Rejects
|
|
|
|
Reject any question that contains or strongly resembles:
|
|
|
|
* Describe...
|
|
* Reflect on...
|
|
* Discuss...
|
|
* Evaluate...
|
|
* In what ways...
|
|
* How satisfied are you...
|
|
* What boundary around...
|
|
* Explore your feelings...
|
|
* Identify the ways...
|
|
* Rate the effectiveness...
|
|
* Communication style
|
|
* Emotional processing
|
|
* Conflict framework
|
|
* Relationship dynamic
|
|
|
|
These are therapy worksheet patterns.
|
|
|
|
Burn them politely.
|
|
|
|
## Duplicate Pattern Rejects
|
|
|
|
Reject the question if it repeats too much of a previous question:
|
|
|
|
* same opening phrase
|
|
* same option list
|
|
* same emotional goal
|
|
* same situation
|
|
* same answer pattern
|
|
* same wording with one noun swapped
|
|
|
|
A file can be valid and still feel like a cursed spreadsheet.
|
|
|
|
## Opening Variety
|
|
|
|
No category should overuse any opening.
|
|
|
|
Watch for overuse of:
|
|
|
|
* What should we...
|
|
* What do you...
|
|
* Which...
|
|
* How much...
|
|
* What makes...
|
|
|
|
These are allowed, but not as the backbone of the pack.
|
|
|
|
## Consumer Test
|
|
|
|
Ask:
|
|
|
|
Would a real couple answer this voluntarily on a Friday night?
|
|
|
|
Reject if the honest answer is no.
|
|
|
|
## Conversation Test
|
|
|
|
A question should create at least one of these:
|
|
|
|
* a laugh
|
|
* a story
|
|
* a decision
|
|
* a date idea
|
|
* a compliment
|
|
* a surprise
|
|
* a memory
|
|
* a useful truth
|
|
* a follow up question
|
|
|
|
Reject questions that only collect data.
|
|
|
|
## Premium Test
|
|
|
|
Reject the question if it does not feel worth paying for.
|
|
|
|
A premium question should feel:
|
|
|
|
* specific
|
|
* warm
|
|
* memorable
|
|
* useful
|
|
* fun
|
|
* relationship focused
|
|
|
|
## Option Quality
|
|
|
|
For multi_choice and single_choice:
|
|
|
|
* use 4 to 6 options
|
|
* avoid obvious correct answers
|
|
* avoid overlapping options
|
|
* avoid vague options like "other"
|
|
* avoid all negative options
|
|
* avoid options that shame either partner
|
|
* keep options short
|
|
* make options feel realistic
|
|
|
|
## Written Question Gate
|
|
|
|
A written question is allowed only when typing creates more value than choices.
|
|
|
|
Reject written questions that ask for:
|
|
|
|
* basic preference
|
|
* yes or no
|
|
* generic reflection
|
|
* long emotional labor
|
|
* forced vulnerability
|
|
|
|
Written questions should create stories, memories, or meaningful appreciation.
|
|
|
|
## Scale Question Gate
|
|
|
|
Use scale only when intensity matters.
|
|
|
|
Good scale uses:
|
|
|
|
* How close does this feel?
|
|
* How comfortable are you?
|
|
* How often does this happen?
|
|
* How important is this?
|
|
* How ready are we?
|
|
|
|
Bad scale uses:
|
|
|
|
* random preferences
|
|
* jokes
|
|
* simple choices
|
|
* topics better served by options
|
|
|
|
## Emotional Safety
|
|
|
|
Reject questions that pressure users to:
|
|
|
|
* confess
|
|
* forgive
|
|
* reveal trauma
|
|
* admit guilt
|
|
* justify boundaries
|
|
* defend needs
|
|
* disclose sexual details before consent context
|
|
* compare partners cruelly
|
|
|
|
The app should open doors, not corner people.
|
|
|
|
## Fun Requirement
|
|
|
|
Every category must include playful moments.
|
|
|
|
Even serious categories need:
|
|
|
|
* small humor
|
|
* soft wording
|
|
* hopeful prompts
|
|
* low pressure options
|
|
* practical repair ideas
|
|
|
|
No category should feel like 250 tiny court summons.
|
|
|
|
## Category Fit
|
|
|
|
Every question must clearly belong to its category.
|
|
|
|
Reject questions that could fit anywhere.
|
|
|
|
Example:
|
|
|
|
Bad for Gratitude:
|
|
|
|
* What do you like most about us?
|
|
|
|
Better:
|
|
|
|
* What's one small thing I do that deserves more credit?
|
|
|
|
## Relationship Anchor
|
|
|
|
Every question should connect to the couple.
|
|
|
|
Prefer:
|
|
|
|
* us
|
|
* we
|
|
* you and me
|
|
* our life
|
|
* our future
|
|
* our memories
|
|
|
|
Avoid generic survey voice.
|
|
|
|
## Final Human Read
|
|
|
|
Before committing a pack, read 30 random questions aloud.
|
|
|
|
Reject the pack if it sounds:
|
|
|
|
* robotic
|
|
* repetitive
|
|
* clinical
|
|
* boring
|
|
* too similar
|
|
* too heavy
|
|
* too generic
|
|
|
|
## Final Approval
|
|
|
|
A pack is ready only when:
|
|
|
|
* schema passes
|
|
* counts pass
|
|
* duplicate checks pass
|
|
* tone review passes
|
|
* category fit passes
|
|
* consumer test passes
|
|
* no obvious AI patterns remain
|