rafcode 3.0.0 → 3.8.0

package/dist/prompts/amend.js

@@ -5,8 +5,7 @@ import { encodeTaskId } from '../utils/paths.js';
  * - userMessage: Reference to input.md and new task description (via positional argument, triggers the LLM to start)
  */
 export function getAmendPrompt(params) {
-    const { projectPath, existingTasks, nextTaskNumber, newTaskDescription, worktreeMode, } = params;
-    const worktreeFlag = worktreeMode ? ' --worktree' : '';
+    const { projectPath, existingTasks, nextTaskNumber, newTaskDescription, } = params;
     const existingTasksSummary = existingTasks
         .map((task) => {
         const status = task.status === 'completed'
@@ -29,15 +28,14 @@ export function getAmendPrompt(params) {
     const modifiableTasksList = modifiableTasks.length > 0
         ? modifiableTasks.map((t) => `- Task ${t.id}: ${t.taskName}`).join('\n')
         : '(none)';
-    const systemPrompt = `You are a project planning assistant for RAF (Ralph's Automation Framework). Your task is to ADD NEW TASKS or MODIFY PENDING tasks in an existing project.
+    const systemPrompt = `You are a project planning assistant for RAF (Ralph's Automation Framework). Add new tasks or modify pending tasks in an existing project.
 
-## IMPORTANT: Amendment Mode
+## Amendment Mode
 
-You are in AMENDMENT MODE. This means:
-- You MAY modify [MODIFIABLE] tasks (pending/failed) if the user requests changes
-- NEVER modify [PROTECTED] tasks (completed) - their outcomes depend on the original plan
-- DO NOT renumber existing tasks
-- You can create NEW tasks starting from number ${encodeTaskId(nextTaskNumber)}
+- [PROTECTED] tasks (completed): NEVER modify — their outcomes depend on the original plan
+- [MODIFIABLE] tasks (pending/failed): MAY modify if the user requests changes
+- Do NOT renumber existing tasks
+- New tasks start from number ${encodeTaskId(nextTaskNumber)}
 
 ## Project Location
 
@@ -45,54 +43,30 @@ Project folder: ${projectPath}
 
 ## Existing Tasks
 
-The following tasks already exist in this project:
-
 ${existingTasksSummary}
 
-### Protected Tasks (COMPLETED - cannot be modified)
+### Protected (COMPLETED)
 ${protectedTasksList}
 
-### Modifiable Tasks (PENDING/FAILED - can be modified if requested)
+### Modifiable (PENDING/FAILED)
 ${modifiableTasksList}
 
 ## Instructions
 
 ### Step 1: Read Context
 
-First, read the original project description from:
-- ${projectPath}/input.md
-
-And review existing decisions from:
-- ${projectPath}/decisions.md (if it exists)
+Read the original project description (\`${projectPath}/input.md\`) and existing decisions (\`${projectPath}/decisions.md\`, if it exists).
 
 ### Step 2: Analyze New Requirements
 
-Read the user's description of new tasks and identify what needs to be added. Consider:
-- How the new tasks relate to existing ones
-- Dependencies on completed tasks (check the ## Dependencies section in existing plan files)
-- Whether new tasks should reference existing task outcomes
-
-**Identifying Follow-up Tasks**: When a new task is a follow-up, fix, or iteration of a previously completed task, you MUST reference the previous task's outcome in the new plan's Context section. This gives the executing agent full context about what was done before.
-
-Use this format in the Context section:
+Consider how new tasks relate to existing ones and their dependencies. For follow-up/fix tasks, reference the previous task's outcome in the Context section:
 \`This is a follow-up to task NN. See outcome: {projectPath}/outcomes/NN-task-name.md\`
 
-The outcome file paths for completed tasks are listed above in the Existing Tasks section.
-
 ### Step 3: Interview the User
 
-For EACH new task you identify, use the AskUserQuestion tool to gather:
-- Specific requirements and constraints
-- Technology preferences
-- Any existing code or patterns to follow
-- Edge cases to handle
-
-### Step 3.5: Record Decisions
+For EACH new task, use AskUserQuestion to gather specific requirements, technology preferences, existing patterns, and edge cases.
 
-After EACH interview question is answered, append the Q&A pair to the existing decisions file:
-- ${projectPath}/decisions.md
-
-Use this format:
+After EACH answer, append the Q&A to \`${projectPath}/decisions.md\`:
 \`\`\`markdown
 ## [Question asked]
 [User's answer]
@@ -100,12 +74,9 @@ Use this format:
 
 ### Step 4: Create New Plan Files
 
-After interviewing the user about all NEW tasks, create plan files starting from the next available number:
-- ${projectPath}/plans/${encodeTaskId(nextTaskNumber)}-task-name.md
-- ${projectPath}/plans/${encodeTaskId(nextTaskNumber + 1)}-task-name.md
-- etc.
+Create plan files starting from \`${projectPath}/plans/${encodeTaskId(nextTaskNumber)}-task-name.md\`. Use kebab-case names.
 
-Each plan file MUST have Obsidian-style frontmatter at the top, before the \`# Task:\` heading. The frontmatter uses standard YAML format with opening and closing \`---\` delimiters:
+Each plan file MUST have this structure:
 
 \`\`\`markdown
 ---
@@ -114,95 +85,51 @@ effort: medium
 # Task: [Task Name]
 
 ## Objective
-[Clear, one-sentence description of what this task accomplishes]
+[Clear, one-sentence description]
 
 ## Context
-[Why this task is needed, how it fits into the larger project]
-[Reference relevant existing tasks if applicable]
-[For follow-up/fix tasks: "This is a follow-up to task NN. See outcome: {projectPath}/outcomes/NN-task-name.md"]
+[Why this task is needed, relation to existing tasks]
+[For follow-ups: "This is a follow-up to task NN. See outcome: {projectPath}/outcomes/NN-task-name.md"]
 
 ## Dependencies
-[Optional section - omit if task has no dependencies]
-[Comma-separated list of task IDs this task depends on, e.g., "1, 2"]
-[If a dependency fails, this task will be automatically blocked]
+[Optional — omit if none. Comma-separated task IDs, e.g., "1, 2"]
 
 ## Requirements
-[Specific requirements gathered from the user interview]
 - Requirement 1
 - Requirement 2
-- ...
 
 ## Implementation Steps
 1. [Step 1]
 2. [Step 2]
-3. [Step 3]
-...
 
 ## Acceptance Criteria
 - [ ] Criterion 1
 - [ ] Criterion 2
-- [ ] All tests pass
 
 ## Notes
-[Any additional context, warnings, or considerations]
-[Reference to existing task outcomes if relevant]
-\`\`\`
-
-### Frontmatter Requirements
-
-The \`effort\` field is REQUIRED in every plan file. It indicates task complexity and determines which model will execute the task:
-- \`effort: low\` — Trivial/mechanical changes, simple one-file edits, config changes
-- \`effort: medium\` — Well-scoped feature work, bug fixes with clear plans, multi-file changes following existing patterns
-- \`effort: high\` — Architectural changes, complex logic, tasks requiring deep codebase understanding
-
-Optionally, you can add an explicit \`model\` field to override the effort-based model selection:
-\`\`\`markdown
----
-effort: medium
-model: opus
----
-# Task: ...
+[Additional context, warnings, references to existing task outcomes]
 \`\`\`
 
-This is rarely needed — prefer using the \`effort\` label so the user's config controls the actual model used.
+**Frontmatter fields:**
+- \`effort\` (REQUIRED): \`low\` (trivial/mechanical), \`medium\` (well-scoped feature work), \`high\` (architectural/complex)
+- \`model\` (optional): Override effort-based model selection. Rarely needed.
 
 ### Step 5: Confirm Completion
 
-After creating all new plan files:
-1. Provide a summary of:
-   - The new tasks you've created, including the effort level for each task. Example format:
-     - Task 2: add-caching (effort: medium)
-     - Task 3: update-docs (effort: low)
-   - How they relate to existing tasks
-   - Total task count in the project
-2. Display this exit message to the user:
+Summarize new tasks with effort levels, their relation to existing tasks, and total task count. Then display:
 
 \`\`\`
 Planning complete! To exit this session and run your tasks:
   1. Press Ctrl-C twice to exit
-  2. Then run: raf do <project>${worktreeFlag}
+  2. Then run: raf do <project>
 \`\`\`
 
-## Important Rules
-
-1. NEVER modify COMPLETED task plans - they are [PROTECTED] because their outcomes depend on the original plan
-2. You MAY modify non-completed task plans (pending/failed) if the user requests changes - they are [MODIFIABLE]
-3. ALWAYS interview the user before creating or modifying plans
-4. New tasks start from number ${encodeTaskId(nextTaskNumber)}
-5. Use descriptive, kebab-case names for plan files
-6. Each plan should be self-contained with all context needed
-7. Specify task dependencies using the ## Dependencies section with task IDs only (e.g., "1, 2")
-8. Tasks without dependencies should omit the Dependencies section entirely
-9. Be specific - vague plans lead to poor execution
-10. ALWAYS include the \`effort\` frontmatter field in every plan file — assess each task's complexity
-
-## Plan Output Style
-
-Plans can include whatever level of detail you deem helpful for the executing agent. Use your judgment:
-- Include implementation details when they clarify the approach
-- Code snippets are acceptable when they help illustrate a specific pattern
-- File paths are helpful when referencing existing project files, patterns, or directories
-- Focus on clarity — the goal is for the executing agent to understand what needs to be done`;
+## Rules
+
+- Always interview the user before creating or modifying plans
+- Each plan must be self-contained with all context needed
+- Be specific — vague plans lead to poor execution
+- Include implementation details, code snippets, and file paths when they clarify the approach`;
     const userMessage = `I want to add the following new tasks to this project:
 
 ${newTaskDescription}

package/dist/prompts/amend.js.map

@@ -1 +1 @@
-{"version":3,"file":"amend.js","sourceRoot":"","sources":["../../src/prompts/amend.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAejD;;;;GAIG;AACH,MAAM,UAAU,cAAc,CAAC,MAAyB;IACtD,MAAM,EACJ,WAAW,EACX,aAAa,EACb,cAAc,EACd,kBAAkB,EAClB,YAAY,GACb,GAAG,MAAM,CAAC;IACX,MAAM,YAAY,GAAG,YAAY,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,EAAE,CAAC;IAEvD,MAAM,oBAAoB,GAAG,aAAa;SACvC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;QACZ,MAAM,MAAM,GACV,IAAI,CAAC,MAAM,KAAK,WAAW;YACzB,CAAC,CAAC,aAAa;YACf,CAAC,CAAC,IAAI,CAAC,MAAM,KAAK,QAAQ;gBACxB,CAAC,CAAC,UAAU;gBACZ,CAAC,CAAC,WAAW,CAAC;QACpB,MAAM,aAAa,GACjB,IAAI,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,cAAc,CAAC;QAC/D,MAAM,UAAU,GACd,IAAI,CAAC,MAAM,KAAK,WAAW;YACzB,CAAC,CAAC,gBAAgB,WAAW,aAAa,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,KAAK;YACvG,CAAC,CAAC,EAAE,CAAC;QACT,OAAO,UAAU,IAAI,CAAC,EAAE,KAAK,IAAI,CAAC,QAAQ,IAAI,MAAM,IAAI,aAAa,GAAG,UAAU,EAAE,CAAC;IACvF,CAAC,CAAC;SACD,IAAI,CAAC,IAAI,CAAC,CAAC;IAEd,MAAM,cAAc,GAAG,aAAa,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC;IAC7E,MAAM,eAAe,GAAG,aAAa,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC;IAE9E,MAAM,kBAAkB,GACtB,cAAc,CAAC,MAAM,GAAG,CAAC;QACvB,CAAC,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QACvE,CAAC,CAAC,QAAQ,CAAC;IACf,MAAM,mBAAmB,GACvB,eAAe,CAAC,MAAM,GAAG,CAAC;QACxB,CAAC,CAAC,eAAe,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QACxE,CAAC,CAAC,QAAQ,CAAC;IAEf,MAAM,YAAY,GAAG;;;;;;;;kDAQ2B,YAAY,CAAC,cAAc,CAAC;;;;kBAI5D,WAAW;;;;;;EAM3B,oBAAoB;;;EAGpB,kBAAkB;;;EAGlB,mBAAmB;;;;;;;IAOjB,WAAW;;;IAGX,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;IA2BX,WAAW;;;;;;;;;;;IAWX,WAAW,UAAU,YAAY,CAAC,cAAc,CAAC;IACjD,WAAW,UAAU,YAAY,CAAC,cAAc,GAAG,CAAC,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iCA8ExB,YAAY;;;;;;;;iCAQZ,YAAY,CAAC,cAAc,CAAC;;;;;;;;;;;;;;6FAcgC,CAAC;IAE5F,MAAM,WAAW,GAAG;;EAEpB,kBAAkB;;wEAEoD,CAAC;IAEvE,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,CAAC;AACvC,CAAC"}
+{"version":3,"file":"amend.js","sourceRoot":"","sources":["../../src/prompts/amend.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAcjD;;;;GAIG;AACH,MAAM,UAAU,cAAc,CAAC,MAAyB;IACtD,MAAM,EACJ,WAAW,EACX,aAAa,EACb,cAAc,EACd,kBAAkB,GACnB,GAAG,MAAM,CAAC;IAEX,MAAM,oBAAoB,GAAG,aAAa;SACvC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;QACZ,MAAM,MAAM,GACV,IAAI,CAAC,MAAM,KAAK,WAAW;YACzB,CAAC,CAAC,aAAa;YACf,CAAC,CAAC,IAAI,CAAC,MAAM,KAAK,QAAQ;gBACxB,CAAC,CAAC,UAAU;gBACZ,CAAC,CAAC,WAAW,CAAC;QACpB,MAAM,aAAa,GACjB,IAAI,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,cAAc,CAAC;QAC/D,MAAM,UAAU,GACd,IAAI,CAAC,MAAM,KAAK,WAAW;YACzB,CAAC,CAAC,gBAAgB,WAAW,aAAa,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,KAAK;YACvG,CAAC,CAAC,EAAE,CAAC;QACT,OAAO,UAAU,IAAI,CAAC,EAAE,KAAK,IAAI,CAAC,QAAQ,IAAI,MAAM,IAAI,aAAa,GAAG,UAAU,EAAE,CAAC;IACvF,CAAC,CAAC;SACD,IAAI,CAAC,IAAI,CAAC,CAAC;IAEd,MAAM,cAAc,GAAG,aAAa,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC;IAC7E,MAAM,eAAe,GAAG,aAAa,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,KAAK,WAAW,CAAC,CAAC;IAE9E,MAAM,kBAAkB,GACtB,cAAc,CAAC,MAAM,GAAG,CAAC;QACvB,CAAC,CAAC,cAAc,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QACvE,CAAC,CAAC,QAAQ,CAAC;IACf,MAAM,mBAAmB,GACvB,eAAe,CAAC,MAAM,GAAG,CAAC;QACxB,CAAC,CAAC,eAAe,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,UAAU,CAAC,CAAC,EAAE,KAAK,CAAC,CAAC,QAAQ,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC;QACxE,CAAC,CAAC,QAAQ,CAAC;IAEf,MAAM,YAAY,GAAG;;;;;;;gCAOS,YAAY,CAAC,cAAc,CAAC;;;;kBAI1C,WAAW;;;;EAI3B,oBAAoB;;;EAGpB,kBAAkB;;;EAGlB,mBAAmB;;;;;;2CAMsB,WAAW,0CAA0C,WAAW;;;;;;;;;;;yCAWlE,WAAW;;;;;;;;oCAQhB,WAAW,UAAU,YAAY,CAAC,cAAc,CAAC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;+FAuDU,CAAC;IAE9F,MAAM,WAAW,GAAG;;EAEpB,kBAAkB;;wEAEoD,CAAC;IAEvE,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,CAAC;AACvC,CAAC"}

package/dist/prompts/execution.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"execution.d.ts","sourceRoot":"","sources":["../../src/prompts/execution.ts"],"names":[],"mappings":"AAQA;;;GAGG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CA2BxD;AAED,MAAM,WAAW,qBAAqB;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,MAAM,CAAC;IACnB,gBAAgB,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7D,UAAU,EAAE,OAAO,CAAC;IACpB,aAAa,EAAE,MAAM,CAAC;IACtB,eAAe,EAAE,MAAM,CAAC;IACxB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,yCAAyC;IACzC,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB,qDAAqD;IACrD,kBAAkB,CAAC,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CACjE;AAED,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,qBAAqB,GAAG,MAAM,CAkLxE"}
+{"version":3,"file":"execution.d.ts","sourceRoot":"","sources":["../../src/prompts/execution.ts"],"names":[],"mappings":"AASA;;;GAGG;AACH,wBAAgB,gBAAgB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CA2BxD;AAED,MAAM,WAAW,qBAAqB;IACpC,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,MAAM,CAAC;IACnB,gBAAgB,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7D,UAAU,EAAE,OAAO,CAAC;IACpB,aAAa,EAAE,MAAM,CAAC;IACtB,eAAe,EAAE,MAAM,CAAC;IACxB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,mBAAmB,CAAC,EAAE,MAAM,CAAC;IAC7B,yCAAyC;IACzC,aAAa,CAAC,EAAE,MAAM,EAAE,CAAC;IACzB,qDAAqD;IACrD,kBAAkB,CAAC,EAAE,KAAK,CAAC;QAAE,MAAM,EAAE,MAAM,CAAC;QAAC,OAAO,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CACjE;AAED,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,qBAAqB,GAAG,MAAM,CAgKxE"}

package/dist/prompts/execution.js

@@ -1,4 +1,5 @@
 import { getCommitFormat, getCommitPrefix, renderCommitMessage } from '../utils/config.js';
+import { extractProjectName } from '../utils/paths.js';
 /**
  * Maximum characters for a dependency outcome summary.
  * Outcomes larger than this will be truncated to avoid context bloat.
@@ -49,9 +50,11 @@ ${previousOutcomes.map((o) => `### Task ${o.taskId}\n${o.content}`).join('\n\n')
     // Build example commit message from config template
     const commitTemplate = getCommitFormat('task');
     const commitPrefix = getCommitPrefix();
+    const projectName = extractProjectName(projectPath) ?? projectNumber;
     const exampleCommit = renderCommitMessage(commitTemplate, {
         prefix: commitPrefix,
-        projectId: projectNumber,
+        projectId: projectName, // backwards compat: {projectId} resolves to projectName
+        projectName,
         taskId: paddedTaskNumber,
         description: '<description>',
     });
@@ -121,20 +124,19 @@ ${depOutcomesFormatted}
 2. Execute the task according to the plan
 3. Verify all acceptance criteria are met
 4. Signal completion with the appropriate marker
-
-## Instructions
 ${retryContextSection}
+## Instructions
+
 ### Step 1: Read the Plan
 
-First, read the plan file to understand exactly what needs to be done.
+Read the plan file to understand exactly what needs to be done.
 
 ### Step 2: Execute the Task
 
-Follow the implementation steps in the plan. Key guidelines:
-- Write clean, maintainable code
-- Follow existing code patterns in the project
-- Add appropriate error handling
+Follow the implementation steps in the plan:
+- Write clean, maintainable code following existing patterns
 - Follow any CLAUDE.md instructions
+- If you encounter blockers, try to resolve them before giving up
 ${dependencyContextSection}${outcomesSection}
 ### Step 3: Verify Completion
 
@@ -145,48 +147,29 @@ Before marking the task complete:
 ${commitInstructions}
 ### Step 4: Write Outcome File
 
-**CRITICAL**: You MUST write an outcome file to document what was accomplished.
-
 **Outcome file path**: \`${outcomeFilePath}\`
 
-The outcome file should contain:
+The outcome file must contain:
 1. A summary of what was done
 2. Key changes made (files modified, features added, etc.)
 3. Any important notes or follow-up items
-4. The completion marker as the LAST line
+4. The completion marker as the LAST line (exactly one marker per file)
 
-**For code tasks**: Summarize what was changed and why
-**For documentation/report tasks**: The outcome IS the deliverable - include the full content
+**For documentation/report tasks**: The outcome IS the deliverable — include the full content.
 
-**CRITICAL**: The outcome file MUST end with one of these markers:
+The outcome file MUST end with one of these markers:
 
-If the task was completed successfully, end the file with:
+On success:
 \`\`\`
 <promise>COMPLETE</promise>
 \`\`\`
 
-If the task failed and cannot be completed, end the file with:
+On failure (do NOT commit — just write the outcome and stop):
 \`\`\`
 <promise>FAILED</promise>
 Reason: [explain why the task failed]
 \`\`\`
 
-## Important Rules
-
-1. ALWAYS read the plan file first
-2. Follow the plan precisely
-3. Do not skip any acceptance criteria
-4. If you encounter blockers, try to resolve them
-5. The outcome file MUST contain EXACTLY ONE completion marker
-6. The completion marker MUST be the LAST line in the outcome file
-7. On SUCCESS: Commit code changes AND outcome file together BEFORE you finish
-8. On FAILURE: Do NOT commit - just write the outcome file with FAILED marker
-
-## Error Handling
-
-If you encounter errors:
-- Try to fix them yourself first
-- If an error prevents completion, write the outcome file with FAILED status and a clear reason
-- Do not mark COMPLETE if there are failing tests or unmet criteria`;
+Do not mark COMPLETE if there are failing tests or unmet criteria.`;
 }
 //# sourceMappingURL=execution.js.map

package/dist/prompts/execution.js.map

@@ -1 +1 @@
-{"version":3,"file":"execution.js","sourceRoot":"","sources":["../../src/prompts/execution.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,mBAAmB,EAAE,MAAM,oBAAoB,CAAC;AAE3F;;;GAGG;AACH,MAAM,4BAA4B,GAAG,IAAI,CAAC;AAE1C;;;GAGG;AACH,MAAM,UAAU,gBAAgB,CAAC,OAAe;IAC9C,2CAA2C;IAC3C,IAAI,OAAO,CAAC,MAAM,IAAI,4BAA4B,EAAE,CAAC;QACnD,OAAO,OAAO,CAAC;IACjB,CAAC;IAED,0CAA0C;IAC1C,MAAM,YAAY,GAAG,OAAO,CAAC,KAAK,CAAC,wCAAwC,CAAC,CAAC;IAC7E,IAAI,YAAY,IAAI,YAAY,CAAC,CAAC,CAAC,EAAE,CAAC;QACpC,MAAM,OAAO,GAAG,YAAY,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QACvC,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC,IAAI,OAAO,CAAC,MAAM,IAAI,4BAA4B,EAAE,CAAC;YACzE,OAAO,iBAAiB,OAAO,4CAA4C,CAAC;QAC9E,CAAC;IACH,CAAC;IAED,sCAAsC;IACtC,MAAM,SAAS,GAAG,OAAO,CAAC,SAAS,CAAC,CAAC,EAAE,4BAA4B,CAAC,CAAC;IACrE,8CAA8C;IAC9C,MAAM,WAAW,GAAG,SAAS,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAChD,MAAM,UAAU,GAAG,SAAS,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAC/C,MAAM,UAAU,GAAG,IAAI,CAAC,GAAG,CAAC,WAAW,EAAE,UAAU,CAAC,CAAC;IAErD,IAAI,UAAU,GAAG,4BAA4B,GAAG,CAAC,EAAE,CAAC;QAClD,OAAO,SAAS,CAAC,SAAS,CAAC,CAAC,EAAE,UAAU,GAAG,CAAC,CAAC,GAAG,4CAA4C,CAAC;IAC/F,CAAC;IAED,OAAO,SAAS,GAAG,4CAA4C,CAAC;AAClE,CAAC;AAoBD,MAAM,UAAU,kBAAkB,CAAC,MAA6B;IAC9D,MAAM,EACJ,WAAW,EACX,QAAQ,EACR,MAAM,EACN,UAAU,EACV,UAAU,EACV,gBAAgB,EAChB,UAAU,EACV,aAAa,EACb,eAAe,EACf,aAAa,GAAG,CAAC,EACjB,mBAAmB,EACnB,aAAa,GAAG,EAAE,EAClB,kBAAkB,GAAG,EAAE,GACxB,GAAG,MAAM,CAAC;IAEX,IAAI,eAAe,GAAG,EAAE,CAAC;IACzB,IAAI,gBAAgB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAChC,eAAe,GAAG;;;;;EAKpB,gBAAgB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,YAAY,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC;CAC/E,CAAC;IACA,CAAC;IAED,6CAA6C;IAC7C,MAAM,gBAAgB,GAAG,UAAU,CAAC,QAAQ,EAAE,CAAC;IAE/C,oDAAoD;IACpD,MAAM,cAAc,GAAG,eAAe,CAAC,MAAM,CAAC,CAAC;IAC/C,MAAM,YAAY,GAAG,eAAe,EAAE,CAAC;IACvC,MAAM,aAAa,GAAG,mBAAmB,CAAC,cAAc,EAAE;QACxD,MAAM,EAAE,YAAY;QACpB,SAAS,EAAE,aAAa;QACxB,MAAM,EAAE,gBAAgB;QACxB,WAAW,EAAE,eAAe;KAC7B,CAAC,CAAC;IAEH,MAAM,kBAAkB,GAAG,UAAU;QACnC,CAAC,CAAC;;;;;;uCAMiC,eAAe;4CACV,QAAQ;2BACzB,aAAa;;;;;;;CAOvC;QACG,CAAC,CAAC,EAAE,CAAC;IAEP,gDAAgD;IAChD,IAAI,mBAAmB,GAAG,EAAE,CAAC;IAC7B,IAAI,aAAa,GAAG,CAAC,IAAI,mBAAmB,EAAE,CAAC;QAC7C,mBAAmB,GAAG;;;kBAGR,aAAa;;6BAEF,mBAAmB;;;;;;;CAO/C,CAAC;IACA,CAAC;IAED,+DAA+D;IAC/D,IAAI,wBAAwB,GAAG,EAAE,CAAC;IAClC,IAAI,aAAa,CAAC,MAAM,GAAG,CAAC,IAAI,kBAAkB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC9D,MAAM,oBAAoB,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YACxD,MAAM,UAAU,GAAG,gBAAgB,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC;YAC/C,OAAO,YAAY,CAAC,CAAC,MAAM,KAAK,UAAU,EAAE,CAAC;QAC/C,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QAEhB,wBAAwB,GAAG;;;;;oBAKX,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC;;EAE1C,oBAAoB;CACrB,CAAC;IACA,CAAC;IAED,OAAO;;;;UAIC,UAAU,OAAO,UAAU;aACxB,MAAM;oBACC,WAAW;;;;4BAIH,QAAQ;;;;;;EAMlC,mBAAmB;;;;;;;;;;;;EAYnB,wBAAwB,GAAG,eAAe;;;;;;;EAO1C,kBAAkB;;;;;2BAKO,eAAe;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oEAwC0B,CAAC;AACrE,CAAC"}
+{"version":3,"file":"execution.js","sourceRoot":"","sources":["../../src/prompts/execution.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,eAAe,EAAE,mBAAmB,EAAE,MAAM,oBAAoB,CAAC;AAC3F,OAAO,EAAE,kBAAkB,EAAE,MAAM,mBAAmB,CAAC;AAEvD;;;GAGG;AACH,MAAM,4BAA4B,GAAG,IAAI,CAAC;AAE1C;;;GAGG;AACH,MAAM,UAAU,gBAAgB,CAAC,OAAe;IAC9C,2CAA2C;IAC3C,IAAI,OAAO,CAAC,MAAM,IAAI,4BAA4B,EAAE,CAAC;QACnD,OAAO,OAAO,CAAC;IACjB,CAAC;IAED,0CAA0C;IAC1C,MAAM,YAAY,GAAG,OAAO,CAAC,KAAK,CAAC,wCAAwC,CAAC,CAAC;IAC7E,IAAI,YAAY,IAAI,YAAY,CAAC,CAAC,CAAC,EAAE,CAAC;QACpC,MAAM,OAAO,GAAG,YAAY,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QACvC,IAAI,OAAO,CAAC,MAAM,GAAG,CAAC,IAAI,OAAO,CAAC,MAAM,IAAI,4BAA4B,EAAE,CAAC;YACzE,OAAO,iBAAiB,OAAO,4CAA4C,CAAC;QAC9E,CAAC;IACH,CAAC;IAED,sCAAsC;IACtC,MAAM,SAAS,GAAG,OAAO,CAAC,SAAS,CAAC,CAAC,EAAE,4BAA4B,CAAC,CAAC;IACrE,8CAA8C;IAC9C,MAAM,WAAW,GAAG,SAAS,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAChD,MAAM,UAAU,GAAG,SAAS,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAC/C,MAAM,UAAU,GAAG,IAAI,CAAC,GAAG,CAAC,WAAW,EAAE,UAAU,CAAC,CAAC;IAErD,IAAI,UAAU,GAAG,4BAA4B,GAAG,CAAC,EAAE,CAAC;QAClD,OAAO,SAAS,CAAC,SAAS,CAAC,CAAC,EAAE,UAAU,GAAG,CAAC,CAAC,GAAG,4CAA4C,CAAC;IAC/F,CAAC;IAED,OAAO,SAAS,GAAG,4CAA4C,CAAC;AAClE,CAAC;AAoBD,MAAM,UAAU,kBAAkB,CAAC,MAA6B;IAC9D,MAAM,EACJ,WAAW,EACX,QAAQ,EACR,MAAM,EACN,UAAU,EACV,UAAU,EACV,gBAAgB,EAChB,UAAU,EACV,aAAa,EACb,eAAe,EACf,aAAa,GAAG,CAAC,EACjB,mBAAmB,EACnB,aAAa,GAAG,EAAE,EAClB,kBAAkB,GAAG,EAAE,GACxB,GAAG,MAAM,CAAC;IAEX,IAAI,eAAe,GAAG,EAAE,CAAC;IACzB,IAAI,gBAAgB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAChC,eAAe,GAAG;;;;;EAKpB,gBAAgB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,YAAY,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC;CAC/E,CAAC;IACA,CAAC;IAED,6CAA6C;IAC7C,MAAM,gBAAgB,GAAG,UAAU,CAAC,QAAQ,EAAE,CAAC;IAE/C,oDAAoD;IACpD,MAAM,cAAc,GAAG,eAAe,CAAC,MAAM,CAAC,CAAC;IAC/C,MAAM,YAAY,GAAG,eAAe,EAAE,CAAC;IACvC,MAAM,WAAW,GAAG,kBAAkB,CAAC,WAAW,CAAC,IAAI,aAAa,CAAC;IACrE,MAAM,aAAa,GAAG,mBAAmB,CAAC,cAAc,EAAE;QACxD,MAAM,EAAE,YAAY;QACpB,SAAS,EAAE,WAAW,EAAG,wDAAwD;QACjF,WAAW;QACX,MAAM,EAAE,gBAAgB;QACxB,WAAW,EAAE,eAAe;KAC7B,CAAC,CAAC;IAEH,MAAM,kBAAkB,GAAG,UAAU;QACnC,CAAC,CAAC;;;;;;uCAMiC,eAAe;4CACV,QAAQ;2BACzB,aAAa;;;;;;;CAOvC;QACG,CAAC,CAAC,EAAE,CAAC;IAEP,gDAAgD;IAChD,IAAI,mBAAmB,GAAG,EAAE,CAAC;IAC7B,IAAI,aAAa,GAAG,CAAC,IAAI,mBAAmB,EAAE,CAAC;QAC7C,mBAAmB,GAAG;;;kBAGR,aAAa;;6BAEF,mBAAmB;;;;;;;CAO/C,CAAC;IACA,CAAC;IAED,+DAA+D;IAC/D,IAAI,wBAAwB,GAAG,EAAE,CAAC;IAClC,IAAI,aAAa,CAAC,MAAM,GAAG,CAAC,IAAI,kBAAkB,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC9D,MAAM,oBAAoB,GAAG,kBAAkB,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YACxD,MAAM,UAAU,GAAG,gBAAgB,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC;YAC/C,OAAO,YAAY,CAAC,CAAC,MAAM,KAAK,UAAU,EAAE,CAAC;QAC/C,CAAC,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QAEhB,wBAAwB,GAAG;;;;;oBAKX,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC;;EAE1C,oBAAoB;CACrB,CAAC;IACA,CAAC;IAED,OAAO;;;;UAIC,UAAU,OAAO,UAAU;aACxB,MAAM;oBACC,WAAW;;;;4BAIH,QAAQ;;;;EAIlC,mBAAmB;;;;;;;;;;;;;EAanB,wBAAwB,GAAG,eAAe;;;;;;;EAO1C,kBAAkB;;;2BAGO,eAAe;;;;;;;;;;;;;;;;;;;;;;;mEAuByB,CAAC;AACpE,CAAC"}

package/dist/prompts/planning.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"planning.d.ts","sourceRoot":"","sources":["../../src/prompts/planning.ts"],"names":[],"mappings":"AAAA,MAAM,WAAW,oBAAoB;IACnC,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,YAAY,CAAC,EAAE,OAAO,CAAC;CACxB;AAED,MAAM,WAAW,oBAAoB;IACnC,YAAY,EAAE,MAAM,CAAC;IACrB,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,oBAAoB,GAAG,oBAAoB,CAiMpF"}
+{"version":3,"file":"planning.d.ts","sourceRoot":"","sources":["../../src/prompts/planning.ts"],"names":[],"mappings":"AAAA,MAAM,WAAW,oBAAoB;IACnC,WAAW,EAAE,MAAM,CAAC;IACpB,YAAY,EAAE,MAAM,CAAC;IACrB,YAAY,CAAC,EAAE,OAAO,CAAC;CACxB;AAED,MAAM,WAAW,oBAAoB;IACnC,YAAY,EAAE,MAAM,CAAC;IACrB,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAC,MAAM,EAAE,oBAAoB,GAAG,oBAAoB,CA4FpF"}

package/dist/prompts/planning.js

@@ -4,15 +4,8 @@
  * - userMessage: Reference to input.md file (via positional argument, triggers the LLM to start)
  */
 export function getPlanningPrompt(params) {
-    const { projectPath, worktreeMode } = params;
-    const worktreeFlag = worktreeMode ? ' --worktree' : '';
-    const systemPrompt = `You are a project planning assistant for RAF (Ralph's Automation Framework). Your task is to analyze the user's project description and create detailed task plans.
-
-## Your Goals
-
-1. **Analyze the input** and identify distinct, actionable tasks
-2. **Interview the user** about EACH task to gather specific requirements
-3. **Create plan files** for each task with clear instructions
+    const { projectPath } = params;
+    const systemPrompt = `You are a project planning assistant for RAF (Ralph's Automation Framework). Analyze the user's project description, interview them, and create detailed task plans.
 
 ## Project Location
 
@@ -22,53 +15,25 @@ Project folder: ${projectPath}
 
 ### Step 1: Identify and Order Tasks
 
-Based on the project description, identify distinct tasks. Each task should:
-- Be independently completable
-- Have a clear outcome
-- Take roughly 10-30 minutes of work
+Identify distinct tasks from the project description. Each task should be independently completable, have a clear outcome, and take roughly 10-30 minutes.
 
-**CRITICAL: Order tasks by logical execution order.** Lower-numbered tasks should be completed before higher-numbered ones. Consider:
-- Setup/foundation tasks come first (e.g., defining schemas, creating interfaces)
-- Core implementation tasks come next
-- Integration and extension tasks come later
-- Testing and validation tasks typically come last
+**Order tasks by logical execution order:** setup/foundation → core implementation → integration/extension → testing/validation.
 
 ### Step 2: Interview the User
 
-For EACH task you identify, you MUST use the AskUserQuestion tool to gather:
-- Specific requirements and constraints
-- Technology preferences
-- Any existing code or patterns to follow
-- Edge cases to handle
-
-DO NOT skip the interview step. The quality of your plans depends on understanding the user's exact needs.
-
-### Step 2.5: Record Decisions
+For EACH task, use the AskUserQuestion tool to gather specific requirements, technology preferences, existing patterns to follow, and edge cases. Do not skip this step.
 
-After EACH interview question is answered, record the Q&A pair in the decisions file:
-- ${projectPath}/decisions.md
-
-Use this format:
+After EACH answer, append the Q&A pair to \`${projectPath}/decisions.md\`:
 \`\`\`markdown
-# Project Decisions
-
-## [Question asked]
-[User's answer]
-
 ## [Question asked]
 [User's answer]
 \`\`\`
 
-This file serves as documentation of design choices made during planning. Append each new Q&A pair as you conduct the interview.
-
 ### Step 3: Create Plan Files
 
-After interviewing the user about all tasks, create plan files in the plans folder:
-- ${projectPath}/plans/1-task-name.md
-- ${projectPath}/plans/2-task-name.md
-- etc.
+Create plan files in \`${projectPath}/plans/\` numbered in execution order (e.g., \`1-task-name.md\`, \`2-task-name.md\`). Use kebab-case names.
 
-Each plan file MUST have Obsidian-style frontmatter at the top, before the \`# Task:\` heading. The frontmatter uses standard YAML format with opening and closing \`---\` delimiters:
+Each plan file MUST have this structure:
 
 \`\`\`markdown
 ---
@@ -77,116 +42,51 @@ effort: medium
 # Task: [Task Name]
 
 ## Objective
-[Clear, one-sentence description of what this task accomplishes]
+[Clear, one-sentence description]
 
 ## Context
 [Why this task is needed, how it fits into the larger project]
 
 ## Dependencies
-[Optional section - omit if task has no dependencies]
-[Comma-separated list of task IDs this task depends on, e.g., "1, 2"]
-[If a dependency fails, this task will be automatically blocked]
+[Optional — omit if none. Comma-separated task IDs, e.g., "1, 2"]
 
 ## Requirements
-[Specific requirements gathered from the user interview]
 - Requirement 1
 - Requirement 2
-- ...
 
 ## Implementation Steps
 1. [Step 1]
 2. [Step 2]
-3. [Step 3]
-...
 
 ## Acceptance Criteria
 - [ ] Criterion 1
 - [ ] Criterion 2
-- [ ] All tests pass
 
 ## Notes
-[Any additional context, warnings, or considerations]
+[Additional context, warnings, or considerations]
 \`\`\`
 
-### Frontmatter Requirements
+**Frontmatter fields:**
+- \`effort\` (REQUIRED): \`low\` (trivial/mechanical), \`medium\` (well-scoped feature work), \`high\` (architectural/complex)
+- \`model\` (optional): Override effort-based model selection. Rarely needed — prefer \`effort\` so the user's config controls the model.
 
-The \`effort\` field is REQUIRED in every plan file. It indicates task complexity and determines which model will execute the task:
-- \`effort: low\` — Trivial/mechanical changes, simple one-file edits, config changes
-- \`effort: medium\` — Well-scoped feature work, bug fixes with clear plans, multi-file changes following existing patterns
-- \`effort: high\` — Architectural changes, complex logic, tasks requiring deep codebase understanding
+**Dependencies:** Infer automatically from task relationships (don't ask the user). Only reference lower-numbered tasks. Only direct dependencies, not transitive ones. Omit section if no prerequisites.
 
-Optionally, you can add an explicit \`model\` field to override the effort-based model selection:
-\`\`\`markdown
----
-effort: medium
-model: opus
----
-# Task: ...
-\`\`\`
+### Step 4: Confirm Completion
 
-This is rarely needed — prefer using the \`effort\` label so the user's config controls the actual model used.
-
-### Step 4: Infer Task Dependencies
-
-For each task, analyze which other tasks must complete successfully before it can begin. Add a \`## Dependencies\` section to plan files that have prerequisites.
-
-**How to identify dependencies:**
-- If task B uses output/artifacts from task A → B depends on A
-- If task B modifies code created by task A → B depends on A
-- If task B tests functionality from task A → B depends on A
-- If task B extends or builds upon task A → B depends on A
-
-**Dependency format examples:**
-\`\`\`markdown
-## Dependencies
-1
-\`\`\`
-or for multiple dependencies:
-\`\`\`markdown
-## Dependencies
-1, 2
-\`\`\`
-
-**Rules for dependencies:**
-- Only reference lower-numbered tasks (tasks are ordered by execution order)
-- Omit the Dependencies section entirely if a task has no prerequisites
-- Keep dependency lists minimal - only direct dependencies, not transitive ones
-- Never create circular dependencies (impossible if you only reference lower-numbered tasks)
-
-### Step 5: Confirm Completion
-
-After creating all plan files:
-1. Provide a summary of the tasks you've created, including the effort level for each task. Example:
-   - Task 1: setup-database (effort: low)
-   - Task 2: implement-auth (effort: medium)
-   - Task 3: refactor-api (effort: high)
-2. Display this exit message to the user:
+Provide a summary with effort levels (e.g., "Task 1: setup-database (effort: low)"), then display:
 
 \`\`\`
 Planning complete! To exit this session and run your tasks:
   1. Press Ctrl-C twice to exit
-  2. Then run: raf do <project>${worktreeFlag}
+  2. Then run: raf do <project>
 \`\`\`
 
-## Important Rules
-
-1. ALWAYS interview the user before creating plans
-2. Create plans in numbered order (1, 2, 3, etc.) reflecting logical execution order
-3. Use descriptive, kebab-case names for plan files
-4. Each plan should be self-contained with all context needed
-5. Infer dependencies automatically - analyze task relationships, don't ask the user about dependencies
-6. Only add Dependencies section when a task genuinely requires another to complete first
-7. Dependencies must only reference lower-numbered tasks to prevent circular dependencies
-8. Be specific - vague plans lead to poor execution
-9. ALWAYS include the \`effort\` frontmatter field in every plan file — assess each task's complexity
-
-## Plan Output Style
-
-Plans can include whatever level of detail you deem helpful for the executing agent. Use your judgment:
-- Include implementation details when they clarify the approach
-- Code snippets are acceptable when they help illustrate a specific pattern
-- File paths are helpful when referencing existing project files, patterns, or directories
-- Focus on clarity — the goal is for the executing agent to understand what needs to be done`;
+## Rules
+
+- Each plan must be self-contained with all context needed for execution
+- Be specific — vague plans lead to poor execution
+- Include implementation details, code snippets, and file paths when they clarify the approach`;
     const userMessage = `Here is my project description:
 
 ${params.inputContent}

package/dist/prompts/planning.js.map

@@ -1 +1 @@
-{"version":3,"file":"planning.js","sourceRoot":"","sources":["../../src/prompts/planning.ts"],"names":[],"mappings":"AAWA;;;;GAIG;AACH,MAAM,UAAU,iBAAiB,CAAC,MAA4B;IAC5D,MAAM,EAAE,WAAW,EAAE,YAAY,EAAE,GAAG,MAAM,CAAC;IAC7C,MAAM,YAAY,GAAG,YAAY,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,EAAE,CAAC;IAEvD,MAAM,YAAY,GAAG;;;;;;;;;;kBAUL,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;IA8BzB,WAAW;;;;;;;;;;;;;;;;;;IAkBX,WAAW;IACX,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;iCAoGkB,YAAY;;;;;;;;;;;;;;;;;;;;;6FAqBgD,CAAC;IAE5F,MAAM,WAAW,GAAG;;EAEpB,MAAM,CAAC,YAAY;;sDAEiC,CAAC;IAErD,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,CAAC;AACvC,CAAC"}
+{"version":3,"file":"planning.js","sourceRoot":"","sources":["../../src/prompts/planning.ts"],"names":[],"mappings":"AAWA;;;;GAIG;AACH,MAAM,UAAU,iBAAiB,CAAC,MAA4B;IAC5D,MAAM,EAAE,WAAW,EAAE,GAAG,MAAM,CAAC;IAC/B,MAAM,YAAY,GAAG;;;;kBAIL,WAAW;;;;;;;;;;;;;;8CAciB,WAAW;;;;;;;;yBAQhC,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;+FAuD2D,CAAC;IAE9F,MAAM,WAAW,GAAG;;EAEpB,MAAM,CAAC,YAAY;;sDAEiC,CAAC;IAErD,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,CAAC;AACvC,CAAC"}