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

v1.14.0 — add Step 3b review workflow, unify file naming, resilient code references

Browse Source 
- Add /plan2code-3b-review: 5-step post-implementation review with adaptive
  scope, 11 dimensions, reference-file architecture, and Plan/Apply/Verify fixes
- Unify workflow/skill file naming to single-dash (drop -- and --- conventions)
- Add Devin platform support and CLAUDE.md MANDATORY FIRST STEP template
- Guide agents to use semantic anchors over line numbers in workflow prompts
- Bump version to 1.14.0
This commit is contained in:
Justin Parker
2026-05-23 06:58:20 -07:00
parent 8e0b1a2ab2
commit 5e48e98293
42 changed files with 3431 additions and 2542 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plan2code-bot/src/bin/plan2code-bot.ts
+6 -6
View File
@@ -3,10 +3,10 @@ import { runCLI } from '../cli.js';
function showHelp(): void {
console.log(`
+----------------------------------------------------------------+
� PLAN2CODEDE-BOT �
�----------------------------------------------------------------�
� Autonomous workflow test runner foplan2codede �
� Features LLM-as-judge for honest quality evaluation �
— PLAN2CODEDE-BOT —
—----------------------------------------------------------------—
— Autonomous workflow test runner foplan2codede —
— Features LLM-as-judge for honest quality evaluation —
+----------------------------------------------------------------+
Usage:
@@ -20,11 +20,11 @@ Options:
--resume Resume a previous incomplete run
Modes:
� New Project Mode - Run from empty directory
— New Project Mode - Run from empty directory
The bot generates an app idea, creates a subdirectory, writes
IDEA.md, runs init, then all 4 workflow steps.
� Enhancement Mode - Run from directory with AGENTS.md
— Enhancement Mode - Run from directory with AGENTS.md
The bot scans the existing codebase, proposes an enhancement,
writes IDEA.md, then runs plan through finalize.
plan2code-bot/src/idea-generator.ts
+3 -3
View File
@@ -39,12 +39,12 @@ export async function generateNewAppIdea(seed?: string): Promise<IdeaResult> {
const category = categories[Math.floor(Math.random() * categories.length)];
const seedClause = seed
? `\n\nThe user provided this seed for inspiration. Stay closely aligned with the theme and intent of the seed — build on it, don't ignore it:\n"${seed}"`
? `\n\nThe user provided this seed for inspiration. Stay closely aligned with the theme and intent of the seed — build on it, don't ignore it:\n"${seed}"`
: '';
const prompt = `Generate a random, creative idea for a ${category}. The project should be achievable in a single coding session (1-2 hours) and should be interesting but not overly complex.
IMPORTANT: Be creative and diverse with your ideas. Avoid defaulting to developer-centric tools (git analyzers, code formatters, repo scanners, etc.) unless the category specifically calls for it. Think about ideas that would appeal to a broad audience — productivity, entertainment, education, health, finance, art, music, social, cooking, travel, fitness, etc.${seedClause}
IMPORTANT: Be creative and diverse with your ideas. Avoid defaulting to developer-centric tools (git analyzers, code formatters, repo scanners, etc.) unless the category specifically calls for it. Think about ideas that would appeal to a broad audience — productivity, entertainment, education, health, finance, art, music, social, cooking, travel, fitness, etc.${seedClause}
Respond in EXACTLY this format (no other text):
NAME: <kebab-case-project-name>
@@ -54,7 +54,7 @@ DESCRIPTION: <2-3 sentence description of what the app does, its key features, a
prompt,
options: {
maxTurns: 1,
systemPrompt: 'You are a wildly creative project idea generator. You come up with surprising, fun, and diverse software project ideas spanning many domains — not just developer tools. Respond only in the exact format requested.',
systemPrompt: 'You are a wildly creative project idea generator. You come up with surprising, fun, and diverse software project ideas spanning many domains — not just developer tools. Respond only in the exact format requested.',
},
});
plan2code-bot/src/prompts/step-instructions.test.ts
+2 -2
View File
@@ -34,9 +34,9 @@ describe('buildStepPrompt', () => {
expect(prompt).toContain('/plan2code-2-document');
});
it('implement prompt includes /plan2code-3-implement skill invocation', () => {
it('implement prompt instructs direct tool usage without skill invocation', () => {
const prompt = buildStepPrompt('implement', config);
expect(prompt).toContain('/plan2code-3-implement');
expect(prompt).toContain('Do NOT use the Skill tool');
});
it('finalize prompt includes /plan2code-4-finalize skill invocation', () => {
plan2code-bot/src/prompts/step-instructions.ts
+8 -8
View File
@@ -20,7 +20,7 @@ export function buildStepPrompt(step: StepName, config: BotConfig): string {
function buildInitPrompt(config: BotConfig): string {
return `${AUTONOMOUS_PREAMBLE}
This is a brand new project with no existing code. Create a minimal stub AGENTS.md file and an IDEA.md file. Do NOT run the /plan2code-init skill � there is no codebase to analyze yet.
This is a brand new project with no existing code. Create a minimal stub AGENTS.md file and an IDEA.md file. Do NOT run the /plan2code-init skill — there is no codebase to analyze yet.
The project idea is: ${config.ideaDescription}
The project name is: ${config.ideaName}
@@ -28,7 +28,7 @@ The project name is: ${config.ideaName}
## What to create
### AGENTS.md
Create a minimal stub with ONLY the following � do NOT invent architecture, tech stack details, commands, or file structures:
Create a minimal stub with ONLY the following — do NOT invent architecture, tech stack details, commands, or file structures:
\`\`\`markdown
# AGENTS.md
@@ -47,7 +47,7 @@ This project is in the planning phase. Architecture, commands, and detailed docu
If IDEA.md does not already exist, create it with the project name and description.
## Rules
- Do NOT create .agents-docs/ or any detail files � there is nothing to document yet
- Do NOT create .agents-docs/ or any detail files — there is nothing to document yet
- Do NOT hallucinate architecture, dependencies, file structures, or tech stack choices
- Do NOT install dependencies or scaffold project files
- ONLY create the two files above`;
@@ -85,7 +85,7 @@ When making decisions:
function buildImplementPrompt(config: BotConfig): string {
return `${AUTONOMOUS_PREAMBLE}
You are a senior software engineer implementing a project phase. Do NOT use the Skill tool � implement directly using Read, Write, Edit, Glob, and Grep tools.
You are a senior software engineer implementing a project phase. Do NOT use the Skill tool — implement directly using Read, Write, Edit, Glob, and Grep tools.
## Process
@@ -95,7 +95,7 @@ You are a senior software engineer implementing a project phase. Do NOT use the
4. **Mark phase in-progress**: Update \`[ ]\` to \`[/]\` in overview.md
5. **Implement each task sequentially**:
- Read the task specification completely
- Write the code using Write or Edit tools � create real files, not code blocks
- Write the code using Write or Edit tools — create real files, not code blocks
- Mark the task \`[x]\` in the phase file immediately after completing it
6. **Complete the phase**: After all tasks, fill in the "Phase Completion Summary" in the phase file
7. **Mark phase complete**: Update \`[/]\` to \`[x]\` in overview.md
@@ -103,11 +103,11 @@ You are a senior software engineer implementing a project phase. Do NOT use the
## Rules
- Follow AGENTS.md if it exists
- Implement specs EXACTLY � no creative additions or unsolicited improvements
- Write task completion status (\`[x]\`) to disk immediately after each task � never batch
- Implement specs EXACTLY — no creative additions or unsolicited improvements
- Write task completion status (\`[x]\`) to disk immediately after each task — never batch
- Only create files mentioned in the spec tasks
- Use the specified file paths, function names, and structures from the spec
- No placeholder code � fully implement every function
- No placeholder code — fully implement every function
- Match existing codebase conventions
- Do NOT run git commands
- Skip running tests unless explicitly listed as a phase task