bptools-writer-expert

Bptools question authoring

Overview

Use this skill to author regular bptools-based Python generators in biology-problems. Follow the repo's shared generator patterns and verify output with small local runs.

Required reading (load before any bptools edit)

1. references/docs/QUESTION_AUTHORING_GUIDE.md
   • Primary authoring workflow, TEMPLATE.py conventions, required structure.
2. bptools.py at the target repo root (this skill is only invoked inside biology-problems, so the file is reachable at the repo-root path returned by git rev-parse --show-toplevel).
   • Canonical helper API. Copying signatures from memory drifts fast; read the live file so formatBB_*, collect_and_write_questions, make_outfile, and anti-cheat flags match what is actually defined.

Do not summarize from memory. Exception: if you already Read both in this session, say so and continue.

Domain-specific guides in references/docs/problems/ must be loaded when the task touches that domain (matching sets, PUBCHEM, MC statements, pedigrees, phylogenetic trees). See references/docs.md for the full index.

Workflow

1. Classify the request and detect project state
   • Use references/topic_index.md as the routing front door: match the request to a row and load the named guide before opening any generator file.
   • Use references/task_selection.md to classify question family, output format, randomization scope, and anti-cheat policy before writing any code.
   • Use references/project_workflow.md to detect whether the target repo is greenfield (no generator exists for this question type) or existing (generators already present). Greenfield: start from TEMPLATE.py, write the authoring contract, implement with bptools primitives, validate with a small run, prove reproducibility. Existing repo: inspect-first (read live bptools.py, inventory generators), identify the current design, make one generator change at a time, then collect the three proof artifacts (before/after sample, seed log, anti-cheat audit).