Files
LabDataStorageEvaluation/docs/rules/meta-concise-questions.md
administrator b173ac82a9 fix(docs): fix formatting issues in README.md
- adapt meta-/code-/obs- rules to the local Python benchmark pipeline
- replace db-sql-ddl, code-config-env-scope, test-e2e-pytest with pipeline equivalents
- add code-python-style, data-determinism, data-naming-units, bench-methodology, build-pipeline-tasks
- normalize specs and README typography to ASCII per code-data-formatting
- rewrite root CLAUDE.md trigger table; add .cursorrules and .gitignore
- specs: pipeline plan and task specs 00-11
- rules: 19 binding rule files adapted for this project
- docs: CLAUDE.md rule-trigger table
- config: .cursorrules commit convention, .gitignore excluding out/ and .venv/
- docs: rewrite README.md with pipeline diagrams, setup guide, result placeholders
- config: requirements.txt for the closed dependency list
- datagen: make_lab_config.py writes out/config/lab_config.yaml and .done marker
2026-07-11 13:39:13 -04:00

1.3 KiB

Ask extremely short, concise questions

Binding on EVERY question put to the user.

Rules

  • One decision per question. Do not bundle unrelated questions.
  • Minimal context. State only what is needed to answer: the situation in one short clause, the concrete options, and what the answer changes. Nothing else.
  • No preamble. Do NOT precede a question with analysis, restated reasoning, background, evidence, or a summary of what you just did. The user has that context; if a fact is truly needed to decide, compress it to one clause.
  • Prefer the smallest form. A yes/no, or a 2-3 option pick. Put the question itself first or make it unmissable.
  • Self-contained but short. The options must be understandable without opening another document, but spell them out in a few words, not paragraphs.
  • No useless information. Every word must help the user decide. Delete anything that does not.

Anti-patterns

  • A multi-paragraph lead-in before the actual question.
  • Re-explaining the problem the user already stated.
  • Listing options with a paragraph of trade-offs each.
  • Asking two or more separate decisions in one run of prose.

Shape to aim for

<one-clause situation>. <Question>?
1. <option> - <few words>
2. <option> - <few words>