mirror of
https://github.com/jparkerweb/plan2code.git
synced 2026-07-21 18:33:22 -07:00
8e0b1a2ab2
- install.js: split into 'I' (prompts + loop) and new 'A' (everything including bot + metrics); update prompt to (I, A, U, C, Q). - CHANGELOG: document complexity check (1.11.1) and expand 1.11.0 notes for the LLM-as-judge evaluation system. - version.json: 1.10.0 -> 1.11.1.
42 KiB
42 KiB
Changelog
All notable changes to Plan2Code will be documented in this file.
v1.11.1
🔧 Changed
- Task complexity check in Document workflow — Enhanced task writing guidance with lightweight cognitive complexity heuristics (inspired by PR #26)
- "Time-boxed" criterion now includes explicit split triggers: 5+ logic branches, 2+ integration points, or shared interface mutation
- New "Complexity check" prompt: before finalizing each task, LLM considers logic branches, distinct behaviors, integration points, shared interface impact, and error/edge cases
- Tasks complex on 3+ signals must be split; adjacent trivial tasks forming a cohesive unit should be combined
- Process step 7 updated to reinforce the complexity check during phase file authoring
v1.11.0
✨ Added
- plan2code-bot — New autonomous workflow test runner (
plan2code-bot/) that uses the Claude Agent SDK to simulate a human running the entire plan2code workflow end-to-end- Two auto-detected modes: new-project (generates an app idea, creates a subdirectory, runs init through finalize) and enhancement (scans existing codebase, proposes a realistic enhancement)
--ideaflag to seed the idea generator with a specific concept--resumeflag to continue incomplete runs from saved state — skips previously succeeded steps and restores idea, config, and implement pass counter- State file (
.plan2code-bot-state.json) saved after each step; automatically deleted on full success, preserved on failure for later resume - Resume auto-detects state files in current directory (enhancement mode) or immediate subdirectories (new-project mode)
- Artifact validation after each step (aborts on missing expected outputs)
- LLM-as-judge evaluation system — Always-on quality assessment that transforms bot from "yes-man" to authentic QA agent
- Intelligent decision making: Uses LLM to answer
AskUserQuestionprompts based on current observations (tools used, files created, errors) instead of hardcoded keyword matching - Post-step evaluation: Comprehensive quality assessment after each step using step-specific criteria (score 0-100, strengths, weaknesses, suggestions, critical issues)
- Observation tracking: Full execution history captured (tools, files, messages, errors, questions with LLM reasoning)
- Quality gate: Blocks finalization if average score < 60, ensuring minimum quality standards
- Evaluation artifacts: Creates
BOT-EVALUATION.md(quality assessments) andBOT-NOTES.md(execution observations) for metrics analysis - Color-coded output: Green (≥85), yellow (70-84), red (<70) score display in console
- Honest scoring: Evaluation criteria emphasize realistic assessment (most work scores 70-85, not inflated)
- Metrics-ready data: Structured
EvaluationResultandExecutionObservationin state file forplan2code-metricsanalysis
- Intelligent decision making: Uses LLM to answer
- Bot-friendly skill installation (copies plan2code skills with
disable-model-invocationstripped) - Implement step loops up to 10 passes until all phases are complete
- Installer integration:
C > Bmenu option to install bot CLI only
v1.10.0
✨ Added
- Retry logic with escalating timeouts in loop controller — Timed-out iterations now retry automatically instead of silently continuing
- Default base timeout reduced from 30 minutes to 3 minutes per attempt
- Up to 5 retry attempts per iteration (configurable via
maxRetries) - Each retry escalates timeout by +30 seconds (attempt 0 = base, attempt 1 = base + 30s, etc.)
- New
executeWithRetry()method wrapsexecuteIteration()with retry loop - Fatal timeout (all attempts exhausted) stops the loop cleanly with a logged error
- Spinner displays elapsed seconds during each attempt; retries show attempt count
maxRetriesfield added toSessionConfigandDEFAULT_CONFIG
🔧 Changed
- Append-only scratchpad enforcement in loop prompt templates — Both task-mode and phase-mode templates now explicitly prohibit editing or reorganizing existing scratchpad content
- Instruction changed from "append to scratchpad.md" to "add a new entry at the bottom"
- Added rule: "Never edit, reorganize, or insert into existing content — only append new entries to the end of the file"
- AGENTS.md restructured into progressive discovery format — AGENTS.md converted to a lightweight index with summaries and markdown links; full detail moved to
.agents-docs/section files.agents-docs/AGENTS-architecture.md— Architecture overview and key design decisions.agents-docs/AGENTS-code-style.md— Code style conventions.agents-docs/AGENTS-development-commands.md— Development commands and setup.agents-docs/AGENTS-plan2code-loop.md— Loop CLI architecture and commands.agents-docs/AGENTS-plan2code-metrics.md— Metrics toolchain detailsinit-updateprompt updated with.agents-docs/detection in pre-flight check
- Agents mode emoji updated — Loop controller agents-mode indicator changed from wheel to hammer
v1.9.1
✨ Added
- Pi (pi.dev) platform support — New target for the Pi terminal-based coding agent
- Local prompt templates installed to
.pi/prompts/(flat.mdwith YAMLdescriptionfrontmatter) - Global prompt templates installed to
~/.pi/agent/prompts/ - Pi users already get skill support via existing
.agents/skills/target; this adds native slash command access - No new helper functions needed — Pi uses the same flat-file-with-YAML pattern as Windsurf, Copilot CLI, and Codeium
- Local prompt templates installed to
📚 Documentation
AGENTS.mdPlatform-Specific File Formats table updated with Pi rowREADME.mdSupported Platforms list updated with Pi (pi.dev)
v1.9.0
✨ Added
- Progressive discovery for AGENTS.md — Init and init-update prompts now generate AGENTS.md as a lightweight index with summaries and markdown links, plus
.agents-docs/section files containing full detail- Init prompt — New
## Progressive Discoverysection defines index format, always-inline sections (Project Overview, Git Commit Messages, How to Use This File),.agents-docs/directory setup, grouping heuristics, and opt-in restructure offer for existing single-file AGENTS.md - Init-update prompt —
.agents-docs/detection in pre-flight check, legacy migration offer, edit routing (inline sections → AGENTS.md, detailed sections →.agents-docs/files), section file lifecycle (create, delete, orphan cleanup), enhanced summary with file count, new update rule 9 (route edits to correct file) - Reference templates updated in both prompts to include
.agents-docs/in the bullet list - "How to Use This File" added as a required content section in generated AGENTS.md files
- Init prompt — New
v1.8.2
🐛 Fixed
- Inflated metrics task counts — Metrics collector regex now matches only
**Task X.N:**checkbox items instead of all checkboxes, fixing ~100-200% count inflation from prerequisite and acceptance criteria checkboxescollectStep2(tasks_per_phase) uses Task-pattern-only regexcollectStep3(phaseTotal,phaseCompleted,blockerCount) all use Task-pattern-only regex- Step 4 overview fallback left unchanged (correctly counts Phase Checklist checkboxes)
🔧 Changed
- Document workflow — Checkbox format
- [ ]now restricted to Task items only; Prerequisites, Acceptance Criteria, and Success Criteria use plain bullet lists (no checkboxes) - Implement workflow — Prerequisite verification changed from checkbox-based (
[x]/[?]/[!]) to inline annotation approach (VERIFIED/ASSUMED: [reason]/BLOCKED: [reason]); added clarifying note that checkbox states apply to Task items and Phase Checklist only - Finalize workflow — Task completion audit now specifies counting only
**Task X.N:**checkbox items - Loop prompt templates — Both task-mode and phase-mode templates updated: prerequisites use plain bullets with inline annotations instead of checkboxes; Checkbox States section scoped to "Task items only"
v1.8.1
✨ Added
- User feedback collection — Optional 1-10 rating with reason, what went well, and what went poorly
- Finalize prompt (Step 5) asks for optional feedback before archival, writes structured table to
overview.md - Collector parses
## User Feedbacktable fromoverview.mdintoRunMetrics.user_feedback - Aggregator computes
avg_user_ratingandfeedback_countper cohort - CLI offers interactive feedback collection if none found during metrics collection
- Analysis and improvement prompts reference
avg_user_ratingmetric target (≥ 7.0) UserFeedbacktype exported from public API
- Finalize prompt (Step 5) asks for optional feedback before archival, writes structured table to
- Pipe-safe feedback parsing — User text containing
|characters is escaped on write and correctly unescaped on parse using negative lookbehind regex
🐛 Fixed
- Duplicate run files — Interactive feedback no longer creates a second run JSON; the original is deleted before re-collecting
- Finalize step ordering — Feedback collection moved to Step 5 (before archival at Step 6), ensuring
overview.mdis written while still in the active spec directory
v1.8.0
✨ Added
- plan2code-metrics — New recursive self-improvement toolchain for plan2code contributors (
plan2code-metrics/)- Fully interactive menu-driven CLI — no flags, all inputs collected via prompts
- Collect metrics from completed project specs (plan, document, implement, finalize steps)
- Import run data from other projects for cross-project aggregation
- View metrics status with health indicators and generation-over-generation deltas
- Analyze weak steps via AI-powered diagnosis (Claude Code or GitHub Copilot CLI)
- Generate surgical improvement proposals with automatic validation (char count limits, edit verification)
- Review and apply proposals with interactive diff review
- Cohort-based aggregation groups runs by prompt generation (SHA fingerprint of prompt files)
- Supports both Claude Code and GitHub Copilot CLI as AI backends
- Standalone TypeScript package with tsup build (ESM), installed via
npm link
🔧 Changed
- plan2code-4--finalize.md — Added "Metrics Capture (Contributors)" note in Step 6 directing contributors to run
plan2code-metricsafter finalization - plan2code-loop index.ts — Added dim hint "run plan2code-metrics" after session summary
v1.7.0
✨ Added
- 4 new platform targets — Gemini CLI, Crush, Amp, and OpenCode now supported
- Gemini CLI installs as TOML commands (
.gemini/commands/plan2code-*.toml) - Crush installs as skill subdirs (
~/.config/crush/skills/on Unix,%LOCALAPPDATA%\crush\skills\on Windows) - Amp and OpenCode covered via shared Agent Skills target (
.agents/skills/)
- Gemini CLI installs as TOML commands (
- Claude Code Skills format — Migrated from flat
.claude/commands/*.mdto.claude/skills/<skill-name>/SKILL.mdwithdisable-model-invocation: truefrontmatter - Agent Skills cross-tool target — Single
.agents/skills/install covers Amp, Gemini CLI, and OpenCode simultaneously - Legacy cleanup — Old
.claude/commands/plan2code-*.mdfiles automatically removed on install and uninstall - TOML generation — New
generateTomlContent()produces Gemini CLI command files using TOML literal multi-line strings
🔧 Changed
AGENTS.mdPlatform-Specific File Formats table expanded to 5 columns with 4 new platform rowsdocs/index.htmlhero section updated with 4 new platform pillsREADME.mdSupported Platforms list updated with 4 new platforms
v1.6.2
🔧 Changed
- Installer menu simplified — Replaced the 7-platform picker with a clean 4-option menu (I/U/C/Q)
I— Install Plan2Code for all platforms + loop CLIU— Uninstall (with confirmation prompt)C— CUSTOM sub-menu:L(local install instructions),O(loop CLI only),Q(back)Q— Quit- Any CLI arguments (e.g.
--dry-run,--platform) are now silently ignored; installer always runs interactively
- README installation section — npx install method promoted to primary recommended install path; updated menu example
🗑️ Removed
- CLI flags
--dry-run,--platform,--local,--uninstall,--help,--loop,--uninstall-loop(all removed; installer is always interactive) displayHelp()function removed frominstall.js
v1.6.1
✨ Added
- NPX installation support - Team members can now install directly from GitHub without cloning
- Added
name,version, andbinfields topackage.jsonfor npm compatibility - Installation via
npx git+ssh://git@github.com/jparkerweb/plan2code.git(SSH) - Installation via
npx git+https://github.com/jparkerweb/plan2code.git(HTTPS) - Installer runs from temporary location and cleans up automatically
- Updated README.md with Quick Start section showing both authentication methods
- Added
.npmignorefile to suppress npm warnings during npx execution
- Added
v1.6.0
🏎️ Improved
- Reduced workflow file sizes - All 4 over-target source prompts compressed to ≤ 11,000 characters for Windsurf IDE compatibility (12,000 char limit minus header buffer)
plan2code-3--implement.md- 14,806 → 8,533 chars (42% reduction)plan2code-1--plan.md- 13,587 → 10,348 chars (24% reduction)plan2code-4--finalize.md- 12,012 → 8,586 chars (29% reduction)plan2code-2--document.md- 11,842 → 9,031 chars (24% reduction)- All functional workflow behavior preserved
- Compression techniques: template-to-section-list specs, removed bad examples, consolidated redundant sections, simplified decorative boxes, imperative directives
🧪 Testing
- Pre-commit character count validation - Husky pre-commit hook prevents workflow files from exceeding 11,000 characters
scripts/validate-char-count.js- Cross-platform Node.js validation script using only built-in modules.husky/pre-commit- Git hook trigger calling the validation script- Root
package.jsonwith husky as sole devDependency (private: true) .gitignoreupdated withnode_modules/andpackage-lock.json
v1.5.4
✨ Added
- AI Assisted commit attribution - All git commit messages now include an
AI Assistedfooter for transparency- Init mode - Generated AGENTS.md files include a Git Commit Messages section instructing agents to always append
AI Assisted - Init-update mode - New "Git Commit Messages" menu option (option 7) for adding or modifying commit message conventions
- Loop task mode -
createTaskCommit()automatically appendsAI Assistedfooter to every commit - Loop phase mode - Prompt template instructs LLM to include
-m "AI Assisted"as final flag on every commit - Implement mode - User-facing git commit suggestions after phase approval include
-m "AI Assisted"
- Init mode - Generated AGENTS.md files include a Git Commit Messages section instructing agents to always append
🔧 Changed
- README loop install instructions - Replaced inline text with formatted code block showing both install options
v1.5.3
✨ Added
- Loop mode selection - Plan2Code Loop now asks users to choose between two loop modes:
- One task per loop (default) - Each agent invocation implements exactly one task. Node controller handles git commits after each task. Same behavior as before.
- One phase per loop - Each agent invocation implements all remaining tasks in the current phase. The LLM handles git commits after each task (with JIRA ticket ID). Ideal for related tasks and smart models with higher context windows.
- Phase-mode prompt template - New
LOOP_PROMPT_TEMPLATE_PHASEinstructs the LLM to complete all tasks in the current phase, create git commits per task, and outputTASK_COMPLETEmarkers for each - Multi-marker completion detection - New
checkForAllCompletions()function parses allTASK_COMPLETE,TASK_BLOCKED, andPREREQ_COMPLETEmarkers from a single agent output PHASE_COMPLETEmarker - New completion marker for phase mode indicating current phase is done (distinct fromLOOP_COMPLETEwhich means all phases done)loopModeconfig field - NewSessionConfig.loopModefield ('task' | 'phase') persisted in session state for resume support- Documentation auto-discovery - Documentation workflow now auto-discovers features to document
- Automatically finds
specs/*/PLAN-DRAFT-*.mdfiles - If only one feature exists, uses it without prompting
- If multiple features exist, presents list and asks user to choose
- Automatically reads
PLAN-CONVERSATION-*.mdif present (optional, for context)
- Automatically finds
- Documentation Verification Pass - Documentation workflow now cross-references against PLAN-DRAFT before finalizing
- New Process Step 7 with sub-steps: 7A (re-read PLAN-DRAFT), 7B (cross-reference sections), 7C (fix gaps), 7D (output summary)
- New "Documentation Verification Pass" section with mapping table showing which PLAN-DRAFT sections to verify against which spec files
- Gap handling: Missing items added with
<!-- VERIFICATION: Added - FR-X from PLAN-DRAFT -->markers - Session end output now includes verification summary table showing Items in PLAN-DRAFT / Covered / Added per section
- Added reminders: "Always run verification pass before finalizing" and "PLAN-DRAFT is the source of truth"
- Conversation Logging - Planning workflow now saves the full planning conversation before creating PLAN-DRAFT
- New file:
specs/<feature-name>/PLAN-CONVERSATION-<YYYYMMDD>.mdcreated in Phase 7 - Contains full conversation transcript organized by phase with speaker attribution (
[AGENT]vs[USER RESPONSE]) - Decision summary tables with user quotes, confirmed requirements, approved technologies, and assumptions
- Serves as source of truth for plan verification
- New file:
- PLAN-DRAFT Verification Pass - New STEP 7C verifies PLAN-DRAFT against conversation log
- Cross-references all requirements, tech decisions, risks, and assumptions
- Missing items added with
<!-- VERIFICATION: Added from Phase X -->markers - Outputs verification summary showing what was captured vs added
- Conversation Log field in PLAN-DRAFT - New header field links to the conversation log file
🔧 Changed
- Installer default option - Pressing Enter without selecting an option now defaults to
A(Install to ALL platforms + loop CLI) instead of quitting - Planning output location changed - PLAN-DRAFT and conversation log now created in feature subdirectory
- New location:
specs/<feature-name>/PLAN-DRAFT-<date>.mdandspecs/<feature-name>/PLAN-CONVERSATION-<date>.md - Date format: YYYYMMDD (e.g.,
20250204) instead of full timestamp - Uppercase
PLAN-CONVERSATIONfor consistency withPLAN-DRAFT - Feature directory created during planning (Step 1) instead of documentation (Step 2)
- Documentation step no longer archives PLAN-DRAFT (already in correct location)
- New location:
- Planning Phase 7 restructured - Now has three sub-steps:
- STEP 7A: Save Conversation Log (new)
- STEP 7B: Create PLAN-DRAFT (existing behavior, uses same timestamp)
- STEP 7C: Verification Pass (new)
- Session End example updated - Now shows both conversation log and PLAN-DRAFT files
- Important Reminders expanded - Added reminders about conversation log and verification pass
🐛 Fixed
.gitignoremissingspecs/entries in phase mode -ensureGitignore()only ran insidecreateTaskCommit(), which is never called in phase mode. MovedensureGitRepo()andensureGitignore()to run once at startup inController.run()as a pre-flight step, ensuring.gitignoreentries are set before the first iteration regardless of loop mode
v1.5.2
✨ Added
- AI Agent File Sync - Init and Init-Update workflows now detect and sync other AI agent config files
- Detects 6 file types: CLAUDE.md, GEMINI.md, .cursorrules, .github/copilot-instructions.md, .cursor/rules/, .windsurf/rules/
- Offers to replace with references to AGENTS.md as single source of truth
- User confirmation required before any modifications
- Correct relative paths for each file location (./AGENTS.md, ../AGENTS.md, ../../AGENTS.md)
- Knowledge Transfer - Init mode now uses existing CLAUDE.md content as context when creating new AGENTS.md
- Preserves project knowledge during migration to AGENTS.md
v1.5.1
✨ Added
- Prerequisite verification workflow - Agents now verify/complete prerequisites before starting phase tasks
- Implementation mode processes prerequisites in order: verify, complete, or mark assumed
- Loop prompt treats prerequisites as "Task 0.X" - one per iteration before tasks
- New completion markers:
PREREQ_COMPLETEandPREREQ_ASSUMED
- New checkbox state
[?]- "Assumed complete, couldn't verify" for prerequisites that can't be validated- Use when prerequisite cannot be programmatically verified (e.g., "Design approved by stakeholder")
- Agents skip
[?]items like[x]items
- Re-opened phase handling in Revision mode - Properly handle adding tasks to completed phases
- New "Re-opening" impact type (Medium-High risk) in impact assessment
- New tasks in completed phases get
🆕 ADDEDflag - Phase checkbox changes from
[x]to[ ]in overview.md when new tasks added - "Phases Re-opened" section in revision summary
- Consistency check now verifies phase completion status matches task completion
🔧 Changed
- Installer UI refresh - Cleaner, narrower layout for better terminal compatibility
- Narrower menu boxes (65 characters instead of 76)
- Smaller mascot display at end of installation
- Added first-time user documentation link after successful install
- Updated menu descriptions to show "+ loop CLI" for relevant options
- Planning workflow guardrails - Prevent users from skipping the documentation step
- Added critical reminder after Phase 7 to direct to
/plan2code-2--document - Added workflow order reminder in Session End section: Plan → Document → Implement → Finalize
- Updated example closing message to emphasize documentation as next step
- Added workflow order to Important Reminders section
- Added critical reminder after Phase 7 to direct to
- AGENTS.md pre-flight message - Improved guidance for new projects
- Message now explains that new projects can continue without AGENTS.md
- Suggests creating basic AGENTS.md first with rules can still be valuable
v1.5.0 - 2026-01-22
✨ Added
- Plan2Code Loop - New autonomous CLI tool for hands-off spec implementation
- Separate Node.js/TypeScript tool in
plan2code-loop/directory - LLM-driven task discovery - AI reads spec files and finds unchecked tasks
- Iterates through tasks one at a time, marking checkboxes as complete
- Structured completion markers:
TASK_COMPLETE: 1.1 - description - Session persistence with scratchpad and iteration logging
- Supports Claude Code and GitHub Copilot CLI agents
- Separate Node.js/TypeScript tool in
- Installer integration for loop CLI
- Option
Anow installs prompts to all platforms AND builds/links the loop CLI - Option
Obuilds and links plan2code-loop CLI only - Option
Uuninstalls prompts AND unlinks the loop CLI
- Option
📝 Documentation
- Updated README.md with "Autonomous Loop" section explaining when to use loop vs manual Step 3
- Updated QUICK-REFERENCE.md with loop commands and decision tree
- Updated AGENTS.md with loop architecture, commands, and completion markers
v1.4.0 - 2026-01-09
✨ Added
- Parallel Phase Execution - Run multiple implementation phases simultaneously in separate agent instances
- Documentation Mode auto-detects parallel-eligible phases based on file conflicts and dependencies
- Implementation Mode presents phase selection UI when parallel options are available
- New "Parallel Execution Groups" section in
overview.mdtracks which phases can run together - Conflict detection criteria: file overlap, prerequisite dependencies, data/output dependencies, shared state
- Users can start multiple
/plan2code-3--implementsessions to work on different parallel phases
- In-Progress Phase Tracking - Track which phases are actively being worked on
- New
[/]checkbox status indicates a phase is in-progress (between[ ]pending and[x]complete) - Phases marked
[/]when an agent starts working,[x]when user approves completion - Aborted phases stay
[/]to enable resume - never reset back to[ ] - Parallel selection UI shows
[IN PROGRESS]vs[AVAILABLE]status for each phase - Single in-progress phase prompts user to confirm resume (prevents accidental overlap)
- Supports multiple agent sessions on parallel phases with clear visibility of what's active
- New
🔧 Changed
- Documentation Mode process - Added step 6 "Analyze phases for parallel execution eligibility"
- Implementation Mode detection - Now checks for parallel siblings before starting phase
- Implementation Mode phase selection - 4-case decision logic for parallel, resume, auto-start scenarios
- Session end summaries - Documentation Mode now reports parallel execution groups
- Abort handling - Phases remain
[/]on abort with clear resume instructions
v1.3.3 - 2025-12-30
✨ Added
- Learning Capture Protocol - Replaced simple "Session Hint" with structured learning capture
- Auto-capture triggers checklist (undocumented commands, gotchas, patterns, workarounds)
- Formatted capture template with category, learning, and context
- Inline
AGENTS.mdupdates without requiring init-update mode switch - Applied to Implementation (Step 3) and Finalize (Step 4) modes
🔧 Changed
- Archive path includes timestamp - Specs now archived to
specs--completed/<feature-name>-<timestamp>/- Prevents overwriting when re-implementing same feature
- Preserves history of multiple implementation attempts
- Clearer session end instructions - Planning mode (Step 1) now explicitly says "ALWAYS tell the user"
- Simplified next command reference - Removed "or equivalent" from next step instructions
v1.3.2 - 2025-12-25
🔧 Changed
- Phase file naming convention - Changed from
Phase X.mdtophase-X.md(lowercase, hyphen instead of space)- Affects generated spec files in
specs/<feature-name>/ - Updated references in documentation, implementation, and finalization modes
- Affects generated spec files in
- PLAN-DRAFT auto-archiving - Planning documents are now automatically archived without prompting
- Moves
specs/PLAN-DRAFT-<timestamp>.mdtospecs/<feature-name>/PLAN-DRAFT.mdafter documentation step - Removed user prompt asking to delete/archive/keep
- Moves
📦 Updated
- Improved uniformity of Prompt files
v1.3.1 - 2025-12-19
✨ Added
- Init-update mode (
/plan2code---init-update) - Interactive workflow to update existing AGENTS.md files- Detects recent work context and suggests relevant additions
- Menu-driven update options: Commands, Architecture, Gotchas, Testing, Environment, General Rules
- Review and prune options for existing content
- Confirms changes before applying
- Prefix: None (utility command)
- Session hints in Steps 2, 3, 4 - Prompts to run
/plan2code---init-updateafter discovering project insights - AGENTS.md pre-flight check in Quick Task and Planning modes
- Checks for
./AGENTS.mdat session start - Offers to run
/plan2code---initbefore continuing if not found
- Checks for
- VS Code Copilot global support - New platform for VS Code's custom prompts feature
- Files installed to platform-specific VS Code config directory:
- Windows:
%APPDATA%\Code\User\prompts\ - macOS:
~/Library/Application Support/Code/User/prompts/ - Linux:
~/.config/Code/User/prompts/
- Windows:
- Uses VS Code custom prompt format with
agent: agentheader - File extension:
.prompt.md - Platform ID:
vscode-copilot
- Files installed to platform-specific VS Code config directory:
- Dynamic path resolution in install.js - Added helper functions for targets with platform-specific paths
getVSCodeCopilotDir()- Returns correct VS Code config path per platformresolveTargetDir()- Handles both static and dynamic directory configurationsgetDisplayPath()- Returns human-readable path for display
🔧 Changed
- install.js interactive menu - Now shows 6 platforms (added VS Code Copilot)
- Help text updated - Valid platform IDs now include
vscode-copilot - Merged
sync-prompts.jsintoinstall.js- Distribution files are now generated on-the-fly- No longer need to run a separate sync script before installation
dist/folder is now gitignored (generated dynamically)- Removed
src/sync-prompts.js(functionality merged intoinstall.js)
- Added
--localoption - Show instructions for project-level (local) installation- Generates
dist/local-commands/and displays copy/paste instructions - Available via
node install.js --localor interactive menu optionL
- Generates
- Updated interactive menu - Added "L. LOCAL" option for local installation instructions
🗑️ Removed
src/sync-prompts.js- No longer needed; functionality merged intoinstall.jsdist/from version control - Now generated dynamically during installation
v1.3.0 - 2025-12-18
✨ Added
- AGENTS.md Integration - All workflow prompts now check for and follow project-specific agent instructions
- Added rule: "If a
./AGENTS.mdfile exists, follow the rules, guidelines and documentation in it" - Applied to Steps 1, 2, 3, and 4 (plan, document, implement, finalize)
- Enables project-specific customization while maintaining consistent workflow methodology
- Added rule: "If a
- Init mode (
/plan2code---init) - New command to generate AGENTS.md files for projects- Analyzes codebase structure and common development commands
- Extracts important details from existing docs (README, PROJECT.md, etc.)
- Creates focused, actionable guidance for AI agents (under 500 lines)
- Prefix: None (utility command)
🔧 Changed
- Moved source prompts to
src/directory - Cleaner project structure separating source files from distribution- All
plan2code-*.mdfiles now live insrc/ sync-prompts.jsmoved tosrc/sync-prompts.js- Run with
node src/sync-prompts.js(wasnode sync-prompts.js) install.jsremains in project root
- All
- Sync script now cleans dist folders before syncing - Ensures no orphaned files from previous syncs
- Deletes
dist/local-commands/anddist/global-commands/before regenerating - Prevents old/renamed files from lingering in distribution
- Deletes
- Added
version.json- Centralized project metadata file- Contains name, version, description, author, license, etc.
- Version displayed in install.js TUI header
- Renamed Quick Task command -
plan2code-0--quick-task→plan2code---quick-task- Removed number prefix for better categorization (utility/standalone mode)
- Maintains same functionality (lightweight planning for small tasks)
- Renamed Revision command -
plan2code-1b--revise→plan2code-1b--revise-plan- Clearer name indicating it revises planning specs
- Maintains same functionality (modify specs mid-implementation)
📚 Documentation
- Commands table updated to reflect new naming convention
- README.md updated with new command references and
src/paths - QUICK-REFERENCE.md updated with new command names
- CLAUDE.md updated with new development commands and file locations
- Landing page updated (
docs/index.html)- Added terminal UI screenshot showing the interactive installer
- Added code block with full installation steps (clone, cd, run)
v1.2.1 - 2025-12-17
🔧 Changed
- Reorganized distribution files into
dist/folder - Cleaner project structure separating source from generated fileslocal-commands/→dist/local-commands/global-commands/→dist/global-commands/
- Updated
sync-prompts.js- Now outputs todist/local-commands/anddist/global-commands/ - Updated
install.js- Now reads fromdist/global-commands/ - Simplified implement/finalize workflow - Now only requires
overview.mdpath instead of bothoverview.mdandPhase X.md- Auto-detects next uncompleted phase from Phase Checklist in overview.md
- Automatically reads corresponding
Phase X.mdfile - Reduces user friction when continuing between phases
- Updated Next Steps sections across all prompts to show simplified workflow
- Step 2 (Document): Now instructs to provide only
overview.md - Step 1b (Revise): Now instructs to provide only
overview.md - Step 3 (Implement): Session end boxes updated with auto-detect messaging
- Step 4 (Finalize): Incomplete implementation box updated
- Step 2 (Document): Now instructs to provide only
📚 Documentation
- Updated CLAUDE.md with new
dist/paths for all references - Updated README.md installation commands (30+ path references updated for both Unix and Windows)
- Updated QUICK-REFERENCE.md commands table (Steps 3 & 4 now show
overview.mdas input) - Updated README.md workflow examples to show new
[Provide: overview.md]pattern - Updated README.md "What to Attach" table with simplified requirements
- Updated README.md troubleshooting section
v1.2.0 - 2025-12-14
✨ Added
- Quick Task mode (
/plan2code-0--quick-task) - Lightweight planning for small tasks that don't need the full 4-step workflow- Standalone mode (doesn't create spec files)
- Conversational output with implementation plan
- Scope validation with thresholds (≤3 components, ≤2 integrations, ≤15 tasks, ≤8 files)
- Escalation path to full planning - creates PLAN-DRAFT and hands off to Step 1
- Prefix:
🚀
- Revision mode (
/plan2code-1b--revise) - Structured way to modify specs mid-implementation- 5-step formal process: Change Analysis → Impact Assessment → Execute Revisions → Consistency Check → Summary
- Batch approval workflow
- Tracks revision history in overview.md
- Prefix:
🔄 [REVISION]
- Requirements Sign-Off gate in Planning Phase 1 - User must explicitly approve requirements before Phase 2
- Escalated PLAN-DRAFT recognition - Planning mode detects and resumes from Quick Task escalations
- Good/bad examples added to Steps 1, 3, and 4 for clearer AI guidance
- Clarification loop protocol in Step 1 with max 3 rounds per phase
- Devil's Advocate check in Planning Phase 5 (Architecture Design)
- Error recovery tables in all prompts' Abort Handling sections
- Quick Reference card (
QUICK-REFERENCE.md) for at-a-glance command reference - Revision reminders in Step 3 completion messages
- Copilot CLI global support - Now installs to
~/.copilot/agents/for global access install.js- New interactive installation script for global setup- Interactive menu when run without arguments
- Select individual platforms (1-5), multiple (comma-separated), or ALL (A)
- Uninstall option (U) to remove installed files
- Non-interactive flags:
--platform X,--dry-run,--uninstall
local-commands/directory - Pre-formatted files for project installationglobal-commands/directory - Pre-formatted files for home directory installation
🔧 Changed
- Standardized section headers across all prompts:
- Role → Rules → Examples → Process → Templates → Session End → Abort Handling → Recovery → Important Reminders
- Condensed templates for token efficiency (~30% reduction in template verbosity)
sync-prompts.jsrestructured - Now only writes tolocal-commands/andglobal-commands/(removed project root platform directories)- Removed platform directories from project root - No longer syncs to
.claude/,.cursor/, etc. in project root; users copy fromlocal-commands/orglobal-commands/instead - Updated README.md with Quick Reference section and new commands table
- Updated CLAUDE.md with new commands and response prefixes
📚 Documentation
- Added QUICK-REFERENCE.md with commands table, mode prefixes, file structure, and troubleshooting
- Expanded README.md workflow table to include Steps 0, 1b
- Updated all installation instructions to use
local-commands/andglobal-commands/ - Added interactive mode documentation for
install.js - Documented Copilot CLI global installation at
~/.copilot/agents/
v1.1.1 - 2025-12-11
🔧 Changed
- Phase approval prompt now uses ASCII box - The "Reply approved" request during implementation sign-off now matches the visual style of other important prompts
- Cursor: Switched from Rules to Commands - Now uses
.cursor/commands/(slash commands) instead of.cursor/rules/(MDC rules)- Commands support global installation at
~/.cursor/commands/ - Better aligns with how other tools handle workflows/slash commands
- Commands support global installation at
- Archived specs folder renamed - Changed from
specs/completed/tospecs--completed/- Simplifies folder structure by avoiding nested directories
- Eliminates need for exclusion rules when searching
specs/
📚 Documentation
- Corrected global installation support - Verified which tools actually support global installation:
- ✅ Claude Code:
~/.claude/commands/ - ✅ Cursor:
~/.cursor/commands/(commands, not rules) - ✅ Continue:
~/.continue/prompts/ - ✅ Windsurf:
~/.codeium/windsurf/global_workflows/ - ❌ GitHub Copilot: Project-only (
.github/agents/and.github/prompts/) - ❌ Antigravity: Project-only (
.agent/workflows/) - global path not well documented
- ✅ Claude Code:
- Updated Quick Start commands to only include tools that support global installation
- Added Windows-specific installation commands (PowerShell and Command Prompt)
- Added troubleshooting entry for unrecognized slash commands/workflows
v1.1.0 - 2025-12-11
✨ Added
- Testing Strategy support - Optional testing preferences during planning phase
- Test types selection (Unit, Integration, E2E, or None)
- Phase testing option (run tests at end of each phase)
- Coverage target selection (Critical paths, Moderate, Comprehensive)
- Testing tasks automatically added to phase specs when enabled
- User sign-off requirement for implementation phases
- Phases marked "Ready for Sign-Off" instead of auto-completing
- User must reply "approved" before phase is marked complete
- Test failure handling: user chooses to fix, document, or investigate
- Enhanced overview.md structure - Now includes:
- Architecture Pattern and Component Overview sections
- Risks and Mitigations table
- Success Criteria checklist
- Improved "Next Steps" formatting - ASCII box format for clearer guidance at workflow transitions
🔧 Changed
- Implementation mode no longer auto-marks phases complete; requires explicit user approval
- Self-review checklist now includes test execution verification
- Completion report format updated to show test results table when applicable
- Spec auto-detection now explicitly excludes
specs--completed/folder
📚 Documentation
- Added Testing Strategy section (2.4) to PLAN-DRAFT template
- Added Phase Testing task block template for phase specs
- Expanded special cases documentation for testing task generation
v1.0.4 - 2025-12-07
📦 Updated
- Added explicit transition check to
Planning Phase 6- when confidence >= 90%, the model now asks the user for confirmation before proceeding to create the PLAN-DRAFT document
v1.0.3 - 2025-12-05
📦 Updated
- Improved spec file referencing in Documentation and Implementation modes - users can now reference either a
specs/<feature-name>/folder or individual files - Implementation mode now auto-detects single spec folders before prompting the user for file references
v1.0.2 - 2025-12-05
🐛 Fixed
- Fixed pre-checked prerequisite checkbox in Phase template (
[x]→[ ]) - generated phase documents no longer appear with prerequisites already complete
📦 Updated
- Added Session Start logic to Planning Mode - automatically detects and resumes from existing
PLAN-DRAFT-*.mdfiles - Replaced vague scope indicators with measurable criteria (phases, requirements, components, integrations)
- Added Large Project checkpoint workflow - projects meeting Large thresholds now checkpoint at Phase 3 and resume in a new conversation
- Added output economy rule - keeps phase responses concise, reserving detailed schemas/APIs for final PLAN-DRAFT
- Updated PLAN-DRAFT template with new status options:
Draft | Phase 3 Complete - Resume at Phase 4 | Complete
v1.0.1 - 2025-12-05
📦 Updated
- Added Initial Context Check to
Planning Phase 1- Model now asks about additional files, reference materials, and external integrations before analyzing requirements - Added user verification checklist and git checkpoint to
Implementation Phase 3- Phase completion reports now guide users through verification and git checkpointing before starting the next phase
v1.0.0 - 2025-12-04
✨ Added
- Initial 4-step workflow methodology for AI-assisted development
- Step 1: Planning mode with 90% confidence threshold
- Step 2: Documentation mode for structured implementation specs
- Step 3: Implementation mode with phase-by-phase execution
- Step 4: Finalization mode for validation and archiving
- Multi-platform support with pre-configured workflow files:
- Claude Code CLI (
.claude/commands/) - Cursor AI (
.cursor/rules/) - GitHub Copilot CLI (
.github/agents/) - VS Code Copilot (
.github/prompts/) - Windsurf IDE (
.windsurf/workflows/) - Google Antigravity (
.agent/workflows/) - Continue extension (
.continue/prompts/)
- Claude Code CLI (
sync-prompts.jsutility to propagate source prompts to all platform directories