Compare commits

..
30 Commits
Author SHA1 Message Date
jparkerweb b942b2b9f0 v1.5.4 2026-02-17 09:13:23 -08:00
jparkerweb 725af08c90 spacing 2026-02-03 20:32:18 -08:00
jparkerweb c10354abff v1.5.2 2026-01-27 12:11:00 -08:00
jparkerweb b1502edfb2 v1.3.3: Learning Capture Protocol and improved session instructions 2025-12-31 13:07:27 -08:00
jparkerweb 87b6b643f0 naming and prompt cleanup 2025-12-25 22:02:24 -08:00
jparkerweb d6354099a9 docs 2025-12-25 21:45:41 -08:00
jparkerweb 582cfccdf5 docs
Updated README to include new workflow details and installation instructions.
2025-12-25 21:45:05 -08:00
jparkerweb b3369e5f76 docs 2025-12-23 17:23:23 -08:00
jparkerweb 0cbacb2a37 improved build and install process 2025-12-23 15:42:35 -08:00
jparkerweb 1eeab9cbb3 Delete .windsurf directory 2025-12-22 09:11:18 -08:00
jparkerweb 7ec47ba7b1 Delete .github directory 2025-12-22 09:11:10 -08:00
jparkerweb 61bad114ec Delete .cursor directory 2025-12-22 09:11:00 -08:00
jparkerweb d8369a0b8c Delete .continue directory 2025-12-22 09:10:49 -08:00
jparkerweb bdebbe30ae Delete .claude directory 2025-12-22 09:10:40 -08:00
jparkerweb bb76590667 Delete .agent directory 2025-12-22 09:10:27 -08:00
jparkerweb e88f467b40 v1.0.4 - Added explicit transition check to Planning Phase 6 2025-12-07 17:52:40 -08:00
jparkerweb 6c04256274 v1.0.3 2025-12-05 21:44:21 -08:00
jparkerweb b2a2ddfc43 v1.0.2 2025-12-05 15:41:23 -08:00
jparkerweb ef30ff0858 - 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
2025-12-05 10:43:58 -08:00
jparkerweb 06f8f78e89 docs 2025-12-04 21:30:41 -08:00
jparkerweb 3dc6681151 docs 2025-12-04 20:51:05 -08:00
jparkerweb 0727988616 docs 2025-12-04 20:28:25 -08:00
jparkerweb 5703ecf8bd update website 2025-12-04 20:23:33 -08:00
jparkerweb fb945f3084 Revise README for Plan2Code workflow updates
Updated the README to reflect changes in the Plan2Code workflow, including new file references and installation instructions.
2025-12-04 18:10:42 -08:00
jparkerweb 47574f78cb docs 2025-12-04 18:09:23 -08:00
jparkerweb 7888f06f11 Create CNAME 2025-12-04 17:47:20 -08:00
jparkerweb 38bd676afa Update and rename plan2code.html to index.html 2025-12-04 17:42:27 -08:00
jparkerweb 7bca4bf9b7 docs 2025-12-04 17:36:20 -08:00
jparkerweb 1bd05b2fe5 v1.0.0 2025-12-04 17:34:22 -08:00
jparkerweb 89437d36b4 Initial commit 2025-12-02 20:59:19 -08:00
7 changed files with 20 additions and 20 deletions

No files matched your search

+2 -2
View File
@@ -185,11 +185,11 @@ When modifying workflow prompts in `src/`:
- Loop task mode: `createTaskCommit()` in `plan2code-loop/src/utils/git.ts` appends the footer automatically - Loop task mode: `createTaskCommit()` in `plan2code-loop/src/utils/git.ts` appends the footer automatically
- Loop phase mode: Prompt template instructs the LLM to add `-m "AI Assisted"` as the final flag - Loop phase mode: Prompt template instructs the LLM to add `-m "AI Assisted"` as the final flag
- Implement mode: User-facing commit suggestions in `src/plan2code-3--implement.md` include the footer - Implement mode: User-facing commit suggestions in `src/plan2code-3--implement.md` include the footer
- **Init workflow:** `src/smarsh2code---init.md` generates AGENTS.md files with a Git Commit Messages section that includes this convention by default - **Init workflow:** `src/plan2code---init.md` generates AGENTS.md files with a Git Commit Messages section that includes this convention by default
## Mascot ## Mascot
The project has a mascot called "Smarshy" - an ASCII art robot that appears in installer output and workflow prompts. Mascot variants are defined in `MASCOT` constant in `install.js` and appear in workflow markdown files. The project has a mascot called "Planny" - an ASCII art robot that appears in installer output and workflow prompts. Mascot variants are defined in `MASCOT` constant in `install.js` and appear in workflow markdown files.
``` ```
╭───╮ ╭───╮
+4 -4
View File
@@ -219,10 +219,10 @@ The `overview.md` includes a "Parallel Execution Groups" section that identifies
After running `node install.js`, use the slash commands directly in your AI tool: After running `node install.js`, use the slash commands directly in your AI tool:
``` ```
/smarsh2code-1--plan # Start planning a new feature /plan2code-1--plan # Start planning a new feature
/smarsh2code-2--document # Create implementation docs from plan /plan2code-2--document # Create implementation docs from plan
/smarsh2code-3--implement # Begin/continue implementation /plan2code-3--implement # Begin/continue implementation
/smarsh2code-4--finalize # Wrap up after all phases complete /plan2code-4--finalize # Wrap up after all phases complete
``` ```
--- ---
+3 -3
View File
@@ -23,11 +23,11 @@ async function selectSpec(cwd: string = process.cwd()): Promise<string | null> {
logger.info(''); logger.info('');
logger.info('To get started:'); logger.info('To get started:');
logger.info(''); logger.info('');
logger.info('1. Create a spec using `smarsh2code-1--plan`'); logger.info('1. Create a spec using `plan2code-1--plan`');
logger.info(' command in our AI Agent'); logger.info(' command in our AI Agent');
logger.info(''); logger.info('');
logger.info('2. Come back here and run `smarsh2code-loop`'); logger.info('2. Come back here and run `plan2code-loop`');
logger.info(' as an alternative to `smarsh2code-3--implement`'); logger.info(' as an alternative to `plan2code-3--implement`');
logger.info(''); logger.info('');
return null; return null;
} }
+1 -1
View File
@@ -18,7 +18,7 @@ Interactive Q&A flow to update an existing `AGENTS.md` with new learnings and pr
Check if `AGENTS.md` exists in project root. Check if `AGENTS.md` exists in project root.
**If missing:** "No AGENTS.md found. Create one from scratch? I can analyze the codebase and generate an initial file." Stop and wait. If yes, use `smarsh2code---init.md` workflow. **If missing:** "No AGENTS.md found. Create one from scratch? I can analyze the codebase and generate an initial file." Stop and wait. If yes, use `plan2code---init.md` workflow.
**If exists:** Read and summarize: **If exists:** Read and summarize:
- Main sections (bullets) - Main sections (bullets)
+1 -1
View File
@@ -37,7 +37,7 @@ If no PLAN-DRAFT found and user hasn't provided one, ask for:
If no plan exists and user wants to skip: If no plan exists and user wants to skip:
> "Documentation transforms planning into specs. Without a plan, either: > "Documentation transforms planning into specs. Without a plan, either:
> 1. Run planning first (`/smarsh2code-1--plan`) > 1. Run planning first (`/plan2code-1--plan`)
> 2. Describe requirements so I can help create a minimal plan" > 2. Describe requirements so I can help create a minimal plan"
## Phase Sizing ## Phase Sizing
+7 -7
View File
@@ -103,7 +103,7 @@ These phases can run in parallel:
Which phase? (1/2/3) Which phase? (1/2/3)
┌─────────────────────────────────────────────────────────────────────────┐ ┌─────────────────────────────────────────────────────────────────────────┐
│ TIP: Run another agent instance with /smarsh2code-3--implement to work │ │ TIP: Run another agent instance with /plan2code-3--implement to work │
│ on a different phase simultaneously. │ │ on a different phase simultaneously. │
│ │ │ │
│ IN PROGRESS phases may be running in another session - selecting one │ │ IN PROGRESS phases may be running in another session - selecting one │
@@ -341,7 +341,7 @@ This creates a checkpoint you can return to if needed.
The next uncompleted phase is Phase Y: [Name]. The next uncompleted phase is Phase Y: [Name].
To continue, start a NEW conversation with: To continue, start a NEW conversation with:
> /smarsh2code-3--implement specs/<feature-name>/overview.md > /plan2code-3--implement specs/<feature-name>/overview.md
The command will auto-detect Phase Y as the next phase to implement. The command will auto-detect Phase Y as the next phase to implement.
``` ```
@@ -378,7 +378,7 @@ Example for continuing:
> ║ ║ > ║ ║
> ║ Then: ║ > ║ Then: ║
> ║ 1. Start a NEW conversation ║ > ║ 1. Start a NEW conversation ║
> ║ 2. Use command: /smarsh2code-3--implement ║ > ║ 2. Use command: /plan2code-3--implement ║
> ║ 3. Provide path: specs/<feature-name>/overview.md ║ > ║ 3. Provide path: specs/<feature-name>/overview.md ║
> ║ ║ > ║ ║
> ║ The command will auto-detect Phase 3 as next. ║ > ║ The command will auto-detect Phase 3 as next. ║
@@ -386,7 +386,7 @@ Example for continuing:
> ╚═══════════════════════════════════════════════════════════════════╝ > ╚═══════════════════════════════════════════════════════════════════╝
> ``` > ```
> >
> Need to change the plan? Use `/smarsh2code-1b--revise` before continuing." > Need to change the plan? Use `/plan2code-1b--revise` before continuing."
Example for final phase: Example for final phase:
@@ -410,13 +410,13 @@ Example for final phase:
> ║ ║ > ║ ║
> ║ Then: ║ > ║ Then: ║
> ║ 1. Start a NEW conversation ║ > ║ 1. Start a NEW conversation ║
> ║ 2. Use command: /smarsh2code-4--finalize ║ > ║ 2. Use command: /plan2code-4--finalize ║
> ║ 3. Provide path: specs/<feature-name>/overview.md ║ > ║ 3. Provide path: specs/<feature-name>/overview.md ║
> ║ ║ > ║ ║
> ╚═══════════════════════════════════════════════════════════════════╝ > ╚═══════════════════════════════════════════════════════════════════╝
> ``` > ```
> >
> Need to revise before finalizing? Use `/smarsh2code-1b--revise` first." > Need to revise before finalizing? Use `/plan2code-1b--revise` first."
## Abort Handling ## Abort Handling
@@ -426,7 +426,7 @@ If user says "abort", "cancel", or similar:
- List completed vs remaining tasks - List completed vs remaining tasks
- Note created/modified files - Note created/modified files
- Do NOT change phase checkbox (stays `[/]`) - Do NOT change phase checkbox (stays `[/]`)
- Explain: "Run `/smarsh2code-3--implement` again to resume." - Explain: "Run `/plan2code-3--implement` again to resume."
3. Stop implementation 3. Stop implementation
## Recovery ## Recovery
+2 -2
View File
@@ -304,7 +304,7 @@ specs--completed/
║ All tasks finished. Specs archived to: ║ ║ All tasks finished. Specs archived to: ║
║ specs--completed/<feature-name>/ ║ ║ specs--completed/<feature-name>/ ║
║ ║ ║ ║
║ Thank you for using the Smarsh2Code workflow! ║ ║ Thank you for using the Plan2Code workflow! ║
║ ║ ║ ║
╚═══════════════════════════════════════════════════════════════════╝ ╚═══════════════════════════════════════════════════════════════════╝
``` ```
@@ -352,7 +352,7 @@ Options:
║ Return to implementation before finalizing. ║ ║ Return to implementation before finalizing. ║
║ ║ ║ ║
║ 1. Start a NEW conversation ║ ║ 1. Start a NEW conversation ║
║ 2. Use command: /smarsh2code-3--implement ║ ║ 2. Use command: /plan2code-3--implement ║
║ 3. Provide path: specs/<feature-name>/overview.md ║ ║ 3. Provide path: specs/<feature-name>/overview.md ║
║ ║ ║ ║
║ The command will auto-detect the next Phase to implement. ║ ║ The command will auto-detect the next Phase to implement. ║