mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-11-17 04: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
@@ -6,6 +6,10 @@ Start all REVISION MODE responses with '🔄 [REVISION]'
|
||||
|
||||
Senior software architect updating implementation specs when requirements change mid-project. **Output: spec-file edits only — never implementation.**
|
||||
|
||||
## Interface
|
||||
|
||||
The FIRST thing you do, before anything else in this file — before Step 1, before reading a spec: ask **web console** (browser page, suggested) or **terminal**? Console → run `node "<D>/console.mjs" open --workflow revise-plan` before reading (<D>: references/web-console/ beside this SKILL.md — ~/.agents/skills/plan2code-1b-revise-plan/references/web-console/ globally — or the dir in ~/.plan2code/console/console-dir; add `--spec specs/<feature-name>` if known, else post `specDir` later), then <D>/console.md → Revision; the Step 1 confirmation, the Step 2 approval and every cleanup question go through it. Switchable anytime. If the argument already says which — `--web` or `Use the web console for this session.` — take it and do not ask; drop the flag. Launched by the dashboard? Its session is already open — resume it (console.md → Launches), then Step 1.
|
||||
|
||||
## Rules
|
||||
|
||||
- Follow `./AGENTS.md` if it exists
|
||||
@@ -17,6 +21,7 @@ Senior software architect updating implementation specs when requirements change
|
||||
- This mode modifies **`specs/` paths only** — do NOT implement code or modify any file outside `specs/`
|
||||
- **Allowed file paths:** ONLY paths under `specs/`. Forbidden: `skills/`, `src/`, `.claude/`, `.agents/`, `.codeium/`, configs, source code. Creating, modifying, or deleting any file outside `specs/` is a violation.
|
||||
- **Question options:** Never offer 'execute', 'implement', or any execution-shaped synonym. Implementation lives in `/plan2code-quick-task` and `/plan2code-3-implement` only.
|
||||
- **Web console exception:** the console's temporary payload files (outside the repo, in the system temp directory) are the one allowed write outside `specs/`. They are messages to the page, never project files.
|
||||
|
||||
## Required Context
|
||||
|
||||
@@ -81,9 +86,9 @@ Present findings and confirm understanding before continuing.
|
||||
```
|
||||
⋅
|
||||
╭───╮
|
||||
│ ● │
|
||||
│ ~ │ Here's the plan. What do you think?
|
||||
╰───╯
|
||||
│ ★ │╱
|
||||
╱│ ~ │ Here's the plan. What do you think?
|
||||
╰┬─┬╯
|
||||
```
|
||||
|
||||
Approve the spec-update plan? (approve / refine / abort). Implementation of any new/modified tasks runs separately via /plan2code-3-implement.
|
||||
@@ -175,9 +180,9 @@ Report and resolve issues before continuing.
|
||||
```
|
||||
⋅
|
||||
╭───╮
|
||||
│ ★ │
|
||||
╲│ ★ │╱
|
||||
│ ◡ │ All revised! Ready to continue!
|
||||
╰───╯
|
||||
╰┬─┬╯
|
||||
|
||||
╔═══════════════════════════════════════════════════════════════════╗
|
||||
║ REVISION COMPLETE ║
|
||||
@@ -186,7 +191,7 @@ Report and resolve issues before continuing.
|
||||
║ Specs have been updated. To continue implementation: ║
|
||||
║ ║
|
||||
║ 1. Start a NEW conversation ║
|
||||
║ 2. Use command: /plan2code-3-implement ║
|
||||
║ 2. Use command: /plan2code-3-implement --web ║
|
||||
║ 3. Provide path: specs/<feature-name>/overview.md ║
|
||||
║ ║
|
||||
║ The command will auto-detect the next Phase to implement. ║
|
||||
@@ -232,4 +237,6 @@ Work summary — tell user: change type, tasks added/modified/removed, phases re
|
||||
|
||||
**Pending phases after revision** — read overview.md Phase Checklist, list all pending (`[ ]`) or re-opened phases with task counts so the user can plan next implementation sessions.
|
||||
|
||||
Returning context: Revised specs in `specs/<feature-name>/`. Run `/plan2code-3-implement` in a new conversation to continue implementation.
|
||||
Returning context: Revised specs in `specs/<feature-name>/`. Run `/plan2code-3-implement --web` in a new conversation to continue implementation.
|
||||
|
||||
**On the web console:** a `__stop` action in a send is the person ending the session: see console.md → Stop requests. Specs change only at Step 3, so a stop before then saves nothing and needs none. At every session end post `finish` BEFORE `stop`: `"command": "/plan2code-3-implement specs/<feature-name>/overview.md"` when revised, or the revise-plan command on an abort. The closing box above is printed to a terminal the browser user is not watching.
|
||||
Reference in new issue
Block a user