jparkerweb/plan2code
1
0
Fork 0
mirror of https://github.com/jparkerweb/plan2code.git synced 2026-07-21 18:33:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

Sync upstream workflow improvements (v1.15.3): session-end summaries, Sync & Maintain in init-update, plan research steps, ls-based spec discovery, revision/commit guardrails; bump version to v1.15.3

Browse Source 
AI Assisted
This commit is contained in:
Justin Parker
2026-06-28 11:41:19 -07:00
parent 20a9e2f040
commit 1015b99a6a
13 changed files with 204 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/plan2code-3-implement.md
+16 -5
View File
@@ -21,6 +21,8 @@ Senior software engineer implementing solutions exactly as specified. Follow spe
## Required Context
⚠️ IMPORTANT: `specs/` is gitignored — NEVER use Glob (silently fails). Shell only: `ls specs/` (Bash) or `Get-ChildItem specs/` (PS).
Need implementation spec files to proceed.
**IMPORTANT:** Never look in `specs--completed/` (archived only). Only check active spec folders under `specs/`.
@@ -200,11 +202,20 @@ Sections: Summary (2-3 sentences), Tasks Completed (Y/Z + blocked list), Test Re
On user "approved":
1. Mark `[/]` → `[x]` in overview.md, update phase-X.md status to "Complete"
2. Show Planny art with completion message
3. Provide: `git add -A && git commit -m "Complete Phase X: [Phase Name]" -m "<JIRA-Ticket-ID>" -m "AI Assisted"` (derive JIRA ticket ID from branch name)
4. **If more phases:** "NEXT STEP: Start NEW conversation and run: `/plan2code-3-implement`"
5. **If final phase:** "NEXT STEP: Start NEW conversation and run: `/plan2code-4-finalize`"
6. Mention `/plan2code-1b-revise-plan` option
7. Suggest: "Optional: run `/plan2code-review` for a post-phase code review -- recommended after key features or milestones."
3. Work summary — tell user: phase name, tasks completed, key files created/modified
4. **Upcoming phases** — read overview.md Phase Checklist, find next 2-3 pending (`[ ]`) phases. For each, peek at its `phase-X.md` for task count and goal. Present a table so the user can assess stopping points and review gates:
| Phase | Tasks | Goal |
|-------|-------|------|
| Phase X: [Name] | Y | [One-sentence goal] |
| Phase X+1: [Name] | Z | [One-sentence goal] |
5. Provide: `git add -A && git commit -m "<subject>" -m "<JIRA-Ticket-ID>" -m "AI Assisted"` (derive JIRA ticket ID from branch name)
- **Subject ≤100 chars. EXACTLY THREE -m flags — no body. NEVER add bullet bodies, paragraph descriptions, or multi-line explanations.** If a phase spec file contains a longer commit-message template, use only its subject line. The diff is the body; the PR is the explanation.
6. **If more phases:** "NEXT STEP: Start NEW conversation and run: `/plan2code-3-implement`"
7. **If final phase:** "NEXT STEP: Start NEW conversation and run: `/plan2code-4-finalize`"
8. Mention `/plan2code-1b-revise-plan` option
9. Suggest: "Optional: run `/plan2code-review` for a post-phase code review -- recommended after key features or milestones."
Planny (continuing):
```