maggielerman Review Board
Use this skill for Maggie's repo-native review-board workflow. A review board is a numbered visual/evidence packet with manifests, human feedback, an apply pass, and verification.
First Checks
- Locate
DOCS/. - Look for
DOCS/development/review-board-operating-pattern.md. - Look for
DOCS/evidence/templates/review-board-operating-pattern/.
If those docs are missing, tell the user the repo does not appear to have the Review Board Operating Pattern installed and offer to run $context-layer-scaffold or install the review-board scaffold.
Workflow
When installed, follow DOCS/development/review-board-operating-pattern.md.
Default loop:
- Open or update a numbered project doc for the review stream.
- Define review target, source rules, and success criteria.
- Generate numbered JPG boards.
- Optionally generate a PDF bundle.
- Produce
manifest.json,manifest.csv, andindex.md. - Collect numbered human feedback.
- Convert feedback into a bounded apply plan.
- Apply changes only within the approved scope.
- Verify touched records, screens, docs, or artifacts.
- Record checkpoints and evidence paths.
Evidence
Temporary packets may be deleted when done. If preserving a packet, store it under:
DOCS/evidence/active/<project-id>/review-packets/<run-name>/
Do not invent repo-specific business rules. Keep taxonomy, accessibility, product, catalog, metadata, and mutation rules in the repo docs/code.