Files
gstack/plan-eng-review/sections/checklist.md
Garry Tanandcapy-ai[bot] ab79e55119 v1.91.78.0 feat(review): plan reality rows, sideways review and cso sweep, investigate recipes (multi-agent wave PR D) (#3119)
* v1.91.70.0 feat(unattended): artifact contract, unattended session kind, findings-derived review log, gate list

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* v1.91.72.0 feat(autoplan): unattended runner next|submit, pluggable outside voice, review checklists, spec-loop cap

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(b-runner): atomic lock creation in spend-ledger, judge bundle skips runner-only sections, fixture env spelling

- lib/spend-ledger.ts: create the lock by linking a complete temp file so a
  contender never reads an empty lock and breaks a live owner (CI admitted 20
  of a cap of 8 under contention); unreadable locks break only by mtime age.
- test/helpers/workflow-judge-input.ts: exclude manifest runner_only sections
  (the B4 checklists) from the judge bundle; the judge rates the interactive
  workflow. test/workflow-judge-input.test.ts expects the same set.
- test/helpers/autoplan-run-fixture.ts: spell the runner's session kind
  without the literal the free-suite environment scan rejects.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* v1.91.74.0 feat(review): plan reality rows, sideways review and cso sweep, investigate recipes

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: register the investigate carve case and map Reality rows to real headings in the review checklists

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: pin the corrected Reality rows obligation rows

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(investigate): use allowlisted placeholders in the flake and polluter fences; select the investigate carve case on PTY changes

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-10-11 02:14:23 +00:00

35 lines
1.6 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!-- AUTO-GENERATED from checklist.md.tmpl — do not edit directly -->
<!-- Regenerate: bun run gen:skill-docs -->
## Checklist (runner profile)
Eng phase steps and required outputs for `bin/gstack-autoplan` (unattended or
`light` runs); interactive runs read `sections/review-sections.md` in full.
### Steps
1. Scope Challenge (A assess, B selectors, C findings) with the decision
procedure; every prior-phase consensus is in the prompt before review.
A ends with the reality rows: one `REALITY:` line per applicable row
(`gstack-plan-reality rows --phase eng`), each with a file:line receipt.
2. Sections 1–4 in order: architecture, code quality, test, performance
(`perf` scope). Continue after the outside voice.
3. Final planning decisions, then the finish sequence below in order.
### Required outputs → producing section
| Output | Produced by | Scope |
|---|---|---|
| Review body | Output reference — review body | always |
| Reality rows (`REALITY:` lines, `PLAN_REALITY` check) | Reality rows (why each exists) | always |
| NOT in scope | "NOT in scope" section | always |
| What already exists | "What already exists" section | always |
| Diagrams | Diagrams | always |
| Failure modes | Failure modes | always |
| Worktree parallelization strategy | Worktree parallelization strategy | always |
| Test Plan | 3. Test review | always |
| Performance findings | 4. Performance review | perf |
| Unresolved decisions | Unresolved decisions | always |
| Completion summary | Completion summary | always |
| Review log row | Review Log | always |
| Next-skill handoff | Next Steps — Review Chaining | always |
| Learnings | Learning hooks | always |