mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-11-16 20:45:33 -08:00
Sync upstream v2.4.0 (web console, dashboard skill, implement-review, global launcher) with 24 review fixes and a look-around wake-up for Planny
AI Assisted
This commit is contained in:
1 parent
eefa7082ed
commit
0d7c2e140b
523 files changed
+339802
-401
No files matched your search
@@ -98,5 +98,5 @@ Nothing decided in the range? Keep the file honest: "No decisions were recorded
|
||||
- **Scraper safety, same as the PLAN-DRAFT:** no `%`, no raw `NN/25` scores, and no bare `Requirements` / `Feasibility` / `Integration` / `Risk` followed by a number anywhere in the file. The plain-English confidence line is the only rendering permitted.
|
||||
- **Standing `specs/` rules apply:** no loop tokens, no `- [ ]` checkboxes, no `METRICS_JSON`.
|
||||
- **Rejections are one line each.** The brief summarizes; the question file argues. The closing pointer line covers readers who want the full reasoning.
|
||||
- **BRIEF mode does not count as question work.** One-question-per-session accounting is untouched; no claim is ever taken.
|
||||
- **BRIEF mode does not count as question work.** It does not count toward the session's decision cadence; no claim is ever taken.
|
||||
- **Do not edit an old brief to "update" it.** Yesterday's brief reflects yesterday's map — write today's instead. Same-day overwrite only.
|
||||
@@ -52,11 +52,11 @@ Two round trips, not six. Three probes each — exactly the cap, so neither batc
|
||||
|
||||
Batch 2 bends the independence test on purpose. The arrival signal (5) can shift under the smallest arrival (4), so strictly it should be held back — but holding it costs a third round trip to catch a conflict that is rare and cheap to spot. The trade is to send them together and reconcile at the recap: if the smallest arrival comes back materially smaller than the artifact you were told about, re-check the arrival signal against it before writing the destination. A knowing trade here, not a licence to batch dependent probes elsewhere.
|
||||
|
||||
**Both batches go through the structured question tool.** Give each probe genuine candidate options with trade-offs and a recommendation; the built-in `Other` path is where the human composes the actor, boundary, arrival signal, or forcing-function detail in their own words. A clicked option is not written verbatim as the destination — the recap-confirmation tool call turns all six answers into the agreed one-or-two-line destination before disk write.
|
||||
**Both batches go through the structured question tool.** Give each probe genuine candidate options with trade-offs and a recommendation; the built-in `Other` path is where the human composes the actor, a further feature to leave out, the arrival signal, or forcing-function detail in their own words. A clicked option is not written verbatim as the destination — the recap-confirmation tool call turns all six answers into the agreed one-or-two-line destination before disk write.
|
||||
|
||||
**Probe 1 — the artifact**
|
||||
|
||||
> "When this map is cleared, what exists that does not exist now: a plan you hand to `/plan2code-1-plan`, a decision locked before anyone plans, or a change already made in the codebase? My guess: a plan."
|
||||
> "When we are done here, what exists that does not exist now: a plan you hand to `/plan2code-1-plan`, a decision recorded before anyone plans, or a change already made in the codebase? My guess: a plan."
|
||||
|
||||
*Fishing for:* the shape of the destination. Push back if the answer is "the feature working" — that is past the edge of every pathfinder map. Say so plainly: "That is the build. The map ends at the plan for the build."
|
||||
|
||||
@@ -68,29 +68,31 @@ Batch 2 bends the independence test on purpose. The arrival signal (5) can shift
|
||||
|
||||
**Probe 3 — the sacrificial boundary**
|
||||
|
||||
> "Name one thing a reasonable person would assume is part of this that you are willing to say is NOT part of it."
|
||||
> "Which of these features are we leaving out this time?"
|
||||
|
||||
*Fishing for:* the first `## Out of scope` bullet. This probe does more work than any other. A destination nobody has excluded anything from has not been thought about. If the human cannot name one, offer two candidates and make them reject one.
|
||||
Deliver it as a multi-select (`multi` on the web console) of 3–5 features a reasonable person might expect to be included. Every option names a feature ("Scheduled exports"), never a rule to keep ("Exports stay manual"). Each option's description ends "(Leaving this out = …)", naming what that leaves. Offer a recommended preset of the ones you would leave out; the free-text path lets them name another feature.
|
||||
|
||||
*Fishing for:* the first `## Out of scope` bullets — the ticked features become them. This probe does more work than any other. If nothing is ticked, push once: a destination nobody has excluded anything from has not been thought about. The preset is the push.
|
||||
|
||||
**Probe 4 — the smallest arrival**
|
||||
|
||||
> "What is the smallest version that would still count as arriving? If only that existed, would you call it done or would you feel cheated?"
|
||||
> "What is the smallest version that would still count? If only that existed, would you call it done or would you feel cheated?"
|
||||
|
||||
*Fishing for:* the difference between the destination and the wish list. Everything above the smallest arrival is a candidate for out of scope or for a later effort.
|
||||
|
||||
**Probe 5 — the arrival signal**
|
||||
|
||||
> "How do you know you have arrived — what do you look at?"
|
||||
> "How will you know it's done — what do you look at?"
|
||||
|
||||
*Fishing for:* a checkable condition. "It feels right" is not one. "Every open decision has an answer and I can hand the draft to planning without re-litigating format" is one.
|
||||
|
||||
**Probe 6 — the forcing function**
|
||||
|
||||
> "What made this surface now? A deadline, an incident, an audit, a customer?"
|
||||
> "What made this come up now? A deadline, an incident, an audit, a customer?"
|
||||
|
||||
*Fishing for:* constraints that will shape half the questions and that nobody volunteers unprompted. A regulatory deadline changes the delivery question, the testing posture question, and the out-of-scope line all at once.
|
||||
|
||||
**The probe names above are internal labels, not headings the human reads.** Head each Q block plainly — *What you end up with*, *Who uses it*, *What's not included*, *Smallest version that counts*, *How you know it's done*, *Why now* — and keep the probe text itself as plain as the quotes above. "The sacrificial boundary" and "the arrival signal" mean something to this playbook and nothing to the person answering. Full rule in the grilling playbook, *Say it in plain English*.
|
||||
**The probe names above are internal labels, not headings the human reads.** Head each Q block plainly — *What you end up with*, *Who uses it*, *Leave for later*, *Smallest version that counts*, *How you know it's done*, *Why now* — and keep the probe text itself as plain as the quotes above. "The sacrificial boundary" and "the arrival signal" mean something to this playbook and nothing to the person answering. Full rule in the grilling playbook, *Say it in plain English*.
|
||||
|
||||
### Worked example — same idea, two destinations
|
||||
|
||||
|
||||
@@ -65,7 +65,7 @@ Every probe gets read once, by a busy human, in a terminal. Write it the way you
|
||||
| "this is a `grill · HITL`" | "this one is yours to call" |
|
||||
| "the frontier holds two takeable questions" | "two things we can decide right now" |
|
||||
| "graduating this out of the fog" | "this is sharp enough to write down as a real question now" |
|
||||
| "the sacrificial boundary" | "name one thing people would assume is included that you are willing to cut" |
|
||||
| "the sacrificial boundary" | "which of these features are we leaving out this time?" |
|
||||
| "shall I set `Locked: yes`?" | "worth recording why we picked this, so nobody re-opens it in six months?" |
|
||||
| "Q3 is blocked by 02" | "the export format question has to land before this one" |
|
||||
| "the UI cannot handle this question" | nothing — put context before the tool and preserve `Other` |
|
||||
@@ -74,6 +74,8 @@ Every probe gets read once, by a busy human, in a terminal. Write it the way you
|
||||
|
||||
**No metaphor where a fact fits.** Maps, fog, and trails belong in the footer and the mascot. Inside a probe they cost a translation step: "three things here are still undecided" beats "the fog is thick in this quarter of the map."
|
||||
|
||||
**On a what-to-drop question, name the thing dropped.** Whenever a question asks what gets dropped, left out or cut, every option names the thing being dropped, never a rule to keep. Otherwise ticking an option reads as a double negative, and the person has to work out whether a tick means yes or no. Bad: "☐ Exports stay manual" · Good: "☐ Scheduled exports (Leaving this out = someone runs each export by hand)"
|
||||
|
||||
The same discipline covers everything else the human reads — the recap turn in *Landing the grill*, the option labels and descriptions in the structured tool, the sketch probes, and the HITL checklists in the resolution playbook. Plain in the question, precise in the term that carries the decision.
|
||||
|
||||
### The independence test
|
||||
@@ -125,7 +127,7 @@ Fallback ONLY when the structured question tool does not exist or its call fails
|
||||
**Copy this shape exactly.** The blank lines are load-bearing, not decoration:
|
||||
|
||||
````markdown
|
||||
Three independent decisions are open. Answer in any order, skip any you want to punt — "Q2: b, Q3: the hybrid" is a perfectly good reply.
|
||||
Three independent decisions are open. Answer in any order, skip any you want to punt — "Q2: a, c; Q3: the hybrid" is a perfectly good reply.
|
||||
|
||||
---
|
||||
|
||||
@@ -143,15 +145,18 @@ When a custodian exports a year of a channel, what do they get back?
|
||||
|
||||
---
|
||||
|
||||
**Q2 — What's not included**
|
||||
**Q2 — Leave for later**
|
||||
|
||||
Name one thing a reasonable person would assume is part of this that you are willing to say is NOT part of it.
|
||||
Which of these features are we leaving out this time? Tick any number.
|
||||
|
||||
*Why it matters:* this becomes the first thing written down as out of scope, and every later "is that in or out?" call is measured against it. A destination nobody has excluded anything from has not been thought about.
|
||||
*Why it matters:* the ones you tick become the first things written down as out of scope, and every later "is that in or out?" call is measured against them. A destination nobody has excluded anything from has not been thought about.
|
||||
|
||||
*Recommendation:* none — this one is yours. If nothing comes to mind, I will offer two candidates and you reject one.
|
||||
*Recommendation:* **(a)** and **(c)** — neither is needed for the first review hand-off.
|
||||
|
||||
*(free text — no options on this one)*
|
||||
- **a)** Scheduled exports (Leaving this out = someone runs each export by hand)
|
||||
- **b)** Exports of deleted messages (Leaving this out = anything already purged stays out of the file)
|
||||
- **c)** Export to a cloud bucket (Leaving this out = the file downloads to the custodian's machine only)
|
||||
- **d)** Redaction inside the export (Leaving this out = the review vendor redacts after ingest)
|
||||
````
|
||||
|
||||
Number them, keep the numbers stable across turns and sessions, and say out loud that partial answers are welcome — the invitation is what makes the skip visible instead of silent.
|
||||
|
||||
@@ -77,7 +77,7 @@ Part 2 answers exactly one question for the human: **is this turn over, or is it
|
||||
|
||||
```
|
||||
NEXT STEP · start a new conversation and run:
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder`
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder --web`
|
||||
```
|
||||
|
||||
The path is always relative and always ends `/pathfinder` — that is exactly the argument this skill's Auto-Discovery resolves an idea from, so the human pastes it back with zero edits. Fill `<idea>` from the active map's directory; never leave the `<spec-folder>` placeholder in a rendered footer.
|
||||
@@ -86,9 +86,9 @@ The command target follows the map's status, but the sentence is always the same
|
||||
|
||||
| Status | Command |
|
||||
|---|---|
|
||||
| `Charting` / `Working` | `/plan2code-0-pathfinder specs/<idea>/pathfinder` |
|
||||
| `Cleared` | `/plan2code-1-plan` — point at the PLAN-DRAFT the Clearing Gate wrote |
|
||||
| `Cleared`, but `## Ground rules` records `AGENTS.md` **absent** | `/plan2code-init` FIRST (offer `questions/00-codebase-context.md`), then `/plan2code-1-plan` |
|
||||
| `Charting` / `Working` | `/plan2code-0-pathfinder specs/<idea>/pathfinder --web` |
|
||||
| `Cleared` | `/plan2code-1-plan --web` — point at the PLAN-DRAFT the Clearing Gate wrote |
|
||||
| `Cleared`, but `## Ground rules` records `AGENTS.md` **absent** | `/plan2code-init` FIRST (offer `questions/00-codebase-context.md`), then `/plan2code-1-plan --web` |
|
||||
|
||||
#### Form B — the turn asks the human something
|
||||
|
||||
@@ -113,7 +113,7 @@ First print the stop branch, clearly labeled:
|
||||
|
||||
```
|
||||
OR START FRESH · new conversation, paste:
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder`
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder --web`
|
||||
```
|
||||
|
||||
Then invoke the structured question tool (header `Next step`) asking: "Continue here, or start fresh? Everything is saved." Options: up to three takeable question names, then `Start fresh`. Put each question's gist / newly-unblocked note in its description. The automatic `Other` path lets the human name another frontier question not shown. Mark one option's description `RECOMMENDED` — early in the session that is a question; at the checkpoint it is `Start fresh`.
|
||||
@@ -168,7 +168,7 @@ Q2 Ceiling behaviour past the cap (re-ask) · Q3 Who sees the truncation warning
|
||||
Confidence: not yet — Feasibility, Risk still need work.
|
||||
|
||||
NEXT STEP · start a new conversation and run:
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder`
|
||||
`/plan2code-0-pathfinder specs/audit-log-export/pathfinder --web`
|
||||
```
|
||||
|
||||
**Cleared** — every stop walked, fog empty, command hands off:
|
||||
@@ -179,7 +179,7 @@ NEXT STEP · start a new conversation and run:
|
||||
Confidence: solid.
|
||||
|
||||
NEXT STEP · start a new conversation and run:
|
||||
`/plan2code-1-plan`
|
||||
`/plan2code-1-plan --web`
|
||||
```
|
||||
|
||||
At `Cleared` the named legend is optional — the destination is reached and the PLAN-DRAFT is the thing to point at. Keep the confidence line; the Clearing Gate leaned on it.
|
||||
|
||||
Reference in new issue
Block a user