Update the workflow prompts and skill scripts for the orchestrator, and add the shared test-runs reference

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-02 12:00:11 -08:00
1 parent 1f80fa6a7c
commit 2468027a5a
32 files changed
+289 -221

No files matched your search

+33
View File
@@ -0,0 +1,33 @@
# Choosing what to run
> Read by Document, Implement, Implement + Review, Quick Task, Review and Finalize before they write, run or offer tests. Never invoked as a skill.
## Three tiers
1. **Per task:** run the tests that cover what the task touched.
2. **Phase end:** run the phase file's `## Phase Testing` lines, plus tests for any other file the phase changed.
3. **Full suite:** only where the plan put it: a `Full suite:` line in a phase file, or Finalize's offer. A project's `AGENTS.md` saying "run `npm test`" (or any whole-suite command) does not put a full run in a phase.
## Finding the tests that cover a file
In this order:
1. `AGENTS.md`'s test map and its "run single test" command.
2. Otherwise match by name, folder and imports of the changed files.
A runner's own related-tests flag may be used when `AGENTS.md` records it. It is never required.
## Quick checks
Lint, a type check, a size check: run them at phase end only when the project or `AGENTS.md` shows them to be fast.
## Shared ground
A test helper or fixture, build or test config, a widely imported module, a shared type or schema. Touching any of these is the moment to offer a wider run: say what was touched and why it reaches wide, and let the person choose.
## Ask when unsure
When you cannot tell whether a check is fast, whether a change is shared ground, or which tests cover a file, ask the person. Never guess.
## Record honestly
Say which tests ran and which were skipped. Never report "tests pass" for a run that did not happen.