rafcode 1.1.2 → 1.3.2

package/src/prompts/amend.ts

@@ -35,7 +35,11 @@ export function getAmendPrompt(params: AmendPromptParams): AmendPromptResult {
             : '[PENDING]';
       const modifiability =
         task.status === 'completed' ? '[PROTECTED]' : '[MODIFIABLE]';
-      return `- Task ${task.id}: ${task.taskName} ${status} ${modifiability}`;
+      const outcomeRef =
+        task.status === 'completed'
+          ? `\n  Outcome: ${projectPath}/outcomes/${task.planFile.replace('plans/', '').replace(/\.md$/, '')}.md`
+          : '';
+      return `- Task ${task.id}: ${task.taskName} ${status} ${modifiability}${outcomeRef}`;
     })
     .join('\n');
 
@@ -94,6 +98,13 @@ Read the user's description of new tasks and identify what needs to be added. Co
 - 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:
+\`This is a follow-up to task NNN. See outcome: {projectPath}/outcomes/NNN-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:
@@ -109,7 +120,7 @@ After EACH interview question is answered, append the Q&A pair to the existing d
 
 Use this format:
 \`\`\`markdown
-## [Amendment] [Question asked]
+## [Question asked]
 [User's answer]
 \`\`\`
 
@@ -131,6 +142,7 @@ Each plan file should follow this structure:
 ## 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 NNN. See outcome: {projectPath}/outcomes/NNN-task-name.md"]
 
 ## Dependencies
 [Optional section - omit if task has no dependencies]
@@ -182,7 +194,20 @@ Planning complete! Press Ctrl-C twice to exit to exit this session
 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., "001, 002")
 8. Tasks without dependencies should omit the Dependencies section entirely
-9. Be specific - vague plans lead to poor execution`;
+9. Be specific - vague plans lead to poor execution
+
+## Plan Output Style
+
+**CRITICAL**: Plans should be HIGH-LEVEL and CONCEPTUAL:
+- Describe WHAT needs to be done, not HOW to code it
+- Focus on architecture, data flow, and component interactions
+- NO code snippets or implementation details in plans
+- File paths ARE acceptable when referencing:
+  - Existing project files to modify
+  - Previous plan/outcome files for context
+  - Project structure and directories
+- Let the executing agent decide implementation specifics
+- Plans guide the work; they don't prescribe exact code`;
 
   const userMessage = `I want to add the following new tasks to this project:
 

package/src/prompts/execution.ts

@@ -167,8 +167,7 @@ Follow the implementation steps in the plan. Key guidelines:
 - Write clean, maintainable code
 - Follow existing code patterns in the project
 - Add appropriate error handling
-- Write tests if specified in the plan
-- Follow any CLAUDE.md instructions if present
+- Follow any CLAUDE.md instructions
 ${dependencyContextSection}${outcomesSection}
 ### Step 3: Verify Completion
 

package/src/prompts/planning.ts

@@ -20,7 +20,7 @@ export function getPlanningPrompt(params: PlanningPromptParams): PlanningPromptR
 
 ## Your Goals
 
-1. **Analyze the input** and identify 3-8 distinct, actionable tasks
+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
 
@@ -32,7 +32,7 @@ Project folder: ${projectPath}
 
 ### Step 1: Identify and Order Tasks
 
-Based on the project description, identify 3-8 distinct tasks. Each task should:
+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 for Claude
@@ -163,7 +163,20 @@ Planning complete! To exit this session and run your tasks:
 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`;
+8. Be specific - vague plans lead to poor execution
+
+## Plan Output Style
+
+**CRITICAL**: Plans should be HIGH-LEVEL and CONCEPTUAL:
+- Describe WHAT needs to be done, not HOW to code it
+- Focus on architecture, data flow, and component interactions
+- NO code snippets or implementation details in plans
+- File paths ARE acceptable when referencing:
+  - Existing project files to modify
+  - Previous plan/outcome files for context
+  - Project structure and directories
+- Let the executing agent decide implementation specifics
+- Plans guide the work; they don't prescribe exact code`;
 
   const userMessage = `Here is my project description:
 

package/src/utils/terminal-symbols.ts

@@ -36,25 +36,28 @@ function truncate(str: string, maxLength: number): string {
  * @param status - Task status
  * @param name - Task name
  * @param elapsedMs - Optional elapsed time in milliseconds
- * @returns Formatted string like "● auth-login 1:23" or "✓ auth-login 1/5"
+ * @param taskId - Optional task ID for [NNN] prefix display
+ * @returns Formatted string like "● [001] auth-login 1:23" or "✓ [001] auth-login 1/5"
  */
 export function formatTaskProgress(
   current: number,
   total: number,
   status: TaskStatus,
   name: string,
-  elapsedMs?: number
+  elapsedMs?: number,
+  taskId?: string
 ): string {
   const symbol = SYMBOLS[status];
   const displayName = truncate(name || 'task', 40);
+  const idPrefix = taskId ? `[${taskId}] ` : '';
 
   // Show elapsed time for running tasks, completed tasks, and failed tasks
   if (elapsedMs !== undefined) {
     const timeStr = formatElapsedTime(elapsedMs);
-    return `${symbol} ${displayName} ${timeStr}`;
+    return `${symbol} ${idPrefix}${displayName} ${timeStr}`;
   }
 
-  return `${symbol} ${displayName} ${current}/${total}`;
+  return `${symbol} ${idPrefix}${displayName} ${current}/${total}`;
 }
 
 /**