mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-11-16 20:45:33 -08:00
Update the workflow prompts and skill scripts for the orchestrator, and add the shared test-runs reference
AI Assisted
This commit is contained in:
1 parent
1f80fa6a7c
commit
2468027a5a
32 files changed
+289
-221
No files matched your search
@@ -41,6 +41,7 @@ Check for `./AGENTS.md` first:
|
||||
- Launched with a spec folder holding a `DIAGNOSIS-*.md`: read it first, as the bug's context (its cause and suggested fix are already found; re-run its reproduction before and after the fix). Once it passes, set the diagnosis `**Status:**` to `Fixed`; escalating, use that folder rather than asking for a name. Fixed, with nothing in the folder past the diagnosis (no `PLAN-CONVERSATION`, `PLAN-DRAFT`, `pathfinder/map.md` or `overview.md`)? It is done: run `node "<S>/specs.mjs" archive <spec> --dry-run` from the project root (`<S>` is `scripts/` beside this SKILL.md, `~/.agents/skills/plan2code-quick-task/scripts/` globally), show its `files`, ask "Archive it to `specs--completed/`? (yes / no)", and on yes run it without `--dry-run`. On no it stays on the dashboard as "Bug fixed".
|
||||
- Cause unclear or the fix big? Stop and suggest `/plan2code-diagnose`.
|
||||
- Read `references/building-habits.md` when the ask is a bug fix or a test fails unexpectedly, after a yes to "Write the test first?", and before a change meant to alter no behavior; follow it.
|
||||
- Read `references/test-runs.md` before the first test run: run the tests covering the changed files, and offer the full suite at sign-off when the change touched shared ground.
|
||||
|
||||
```
|
||||
⋅
|
||||
@@ -50,7 +51,7 @@ Check for `./AGENTS.md` first:
|
||||
╰┬─┬╯
|
||||
```
|
||||
|
||||
Ask what feature the user wants, then ask follow-up questions until 100% clear. Console: that first card carries `"templates": "idea"` (console.md → The kinds).
|
||||
Ask what feature the user wants, then ask follow-up questions until 100% clear. Console: that first card carries `"templates": "idea"` (console.md → A patch).
|
||||
|
||||
**Write the test first?** Ask it with the follow-ups (or on its own if there are none) only when the change alters behavior AND the project already has a test runner you can see (a `test` script in `package.json`, pytest config in `pytest.ini` or `pyproject.toml`, `go.mod` with `_test.go` files, or similar). Never for a pure refactor, a docs change, or a project with no runner. Console: one `confirm` card in the same batch as the other plan questions; terminal: one line in the same prompt. On yes, name the test spot in the plan's Verify section and follow the test-first habit.
|
||||
|
||||
@@ -144,7 +145,7 @@ Then tell user: "Created `specs/<feature-name>/PLAN-DRAFT-<date>.md`. Start new
|
||||
3. [Continue...]
|
||||
|
||||
### Verify
|
||||
- [ ] [How to test/confirm]
|
||||
- [ ] [Targeted: the command and the tests covering the changed files]
|
||||
- [ ] [Test first: the test spot, e.g. "test through `POST /votes`"]
|
||||
|
||||
---
|
||||
@@ -162,4 +163,4 @@ Ready to implement? (yes / modify / escalate / abort)
|
||||
|
||||
Work summary — tell user: task name, plan delivered (or PLAN-DRAFT created if escalated). After a build, offer: "Reply `show me` to see it running." **Show me it working** (offered, never required): start the app as `AGENTS.md` Commands says (missing: work it out from `package.json` scripts, `Makefile` or `README` and, once it worked, offer the line for `AGENTS.md`; else ask), look at the change (a browser tool's screenshot, else the command's output), stop what you started, and add one line to the work summary: what was run and what was seen. Screenshots go on the web console page only.
|
||||
|
||||
**On the web console:** a `__stop` action in a send is the person ending the session: see console-stop.md. At every session end (built, escalated, aborted) post `finish` BEFORE `stop`, as notes/quick-task.md describes. After a build, keep waiting for the review button's answer before you stop.
|
||||
**On the web console:** after a build, keep waiting for the review button's answer before you stop.
|
||||
Reference in new issue
Block a user