Files
redsen-lean-harness/templates/questionnaire.md
T
mozempkandCopilot 383129f571 feat: scaffold redsen-lean-harness v0.1.0
Recovered from crashed session (Node OOM). Repo contains full P0-P6
scaffold: plugin.json/marketplace.json, AGENTS.md, ADRs 0001-0006,
lh CLI (init/index/graph/lane/run/memory/host/report/doctor), 10
.github/agents, 12 CLI skills, instructions, context7 mcp.json, and
unit/e2e test suite.

Fixed: run.mjs read --in-tokens/--out-tokens but tests and CLI docs
use --input-tokens/--output-tokens, so telemetry totals were always 0.
Now accepts both forms.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-09-09 22:44:15 +02:00

1.7 KiB

Design questionnaire: {{TITLE}}

Edit answers in place, keep one numbered answer per question, then say "go". Recommended answers are marked.

1. Primary goal?

  1. Recommended: Implement smallest complete behaviour that satisfies acceptance criteria.
  2. Explore architecture only; no code changes.
  3. Prototype disposable spike.

Answer: 1

2. Risk tolerance?

  1. Recommended: Conservative; preserve existing contracts and APIs.
  2. Moderate; allow internal refactors when verified.
  3. Aggressive; redesign if simpler.

Answer: 1

3. Compatibility target?

  1. Recommended: Backward compatible unless requirement says otherwise.
  2. Breaking changes allowed with migration notes.
  3. New surface only; no compatibility promise.

Answer: 1

4. Verification depth?

  1. Recommended: Run targeted tests plus configured verify commands that cover changed behaviour.
  2. Run targeted tests only.
  3. Full suite required before completion.

Answer: 1

5. Documentation updates?

  1. Recommended: Update docs directly tied to changed behaviour.
  2. No docs unless tests require them.
  3. Full architecture/conventions refresh.

Answer: 1

6. Parallelism?

  1. Recommended: Use read-only fan-out for independent research; serialize writes by scope.
  2. Single-lane implementation.
  3. Maximize lanes even for moderate coupling.

Answer: 1

7. External services?

  1. Recommended: Avoid new external calls unless existing workflow requires them.
  2. Use documented services when helpful.
  3. Ask user before any external call.

Answer: 1

8. Secret handling?

  1. Recommended: Never write secrets; require env vars or existing secret stores.
  2. Allow local uncommitted secret files.
  3. Inline placeholders only.

Answer: 1