webwork-writer-expert

WebWork question authoring

Overview

Use this skill to author or adjust PG/PGML problems with the local WebWork renderer, repo rules, and the docs in references/.

Required reading (load before any PGML edit)

1. references/docs/HOW_TO_LINT.md
2. references/docs/PG_COMMON_PITFALLS.md
3. references/docs/WEBWORK_PROBLEM_AUTHOR_GUIDE.md

Do not summarize from memory. Do not skip because "you already know PGML." Agents that skip these docs ship problems with well-known pitfalls that fail renderer lint and waste human review time.

Exception: if you have already Read all three files earlier in the same session, you do not need to re-read them. State explicitly that you already loaded them this session before continuing.

Workflow

1. Classify the request using references/task_selection.md, then route to the correct guide via references/topic_index.md. Both files must be consulted before opening any PG/PGML file.
2. Determine project shape using references/project_workflow.md:
   • Greenfield: no existing .pg/.pgml files in the target repo. Write the WebWork design contract first, then scaffold problems following the greenfield path.
   • Improve existing: existing .pg/.pgml files are present. Inspect the existing files, renderer harness, and OPL headers first; then apply changes one category at a time following the existing-repo path.
3. Satisfy the Required reading block above. This is step zero of editing; nothing else happens first.
4. Identify the target repo and file, then read any additional relevant doc references from references/docs.md for the question type at hand.
5. Apply the PGML structure and rules from the WebWork author guide.
6. Make edits in the problem file and update docs/CHANGELOG.md directly when this skill runs as a standalone task; under delegate-manager-to-subagents, dispatch a docs subagent to add the entry.
7. Render with -r using the local renderer API to visually confirm layout and checkbox behavior (prerequisite).
8. Lint or render with the local renderer API when the change affects PGML output.
9. Validate against the oracles in references/testing_and_oracles.md: lint output clean, visual render correct, grading test passes, seed reproducible.