rafcode 1.0.0

package/RAF/015-name-lottery/plans/002-mention-plan-files-in-commit.md

@@ -0,0 +1,32 @@
+# Task: Mention plan files in git commit instructions
+
+## Objective
+Update the task execution prompt to explicitly mention that plan files should be included in commits when they exist.
+
+## Context
+When tasks are executed after `raf plan --amend`, new plan files may exist in the working directory. The current git commit instruction says to use `git add -A` which would include them, but it's not explicit. Making this explicit helps ensure Claude understands that plan files are part of the commit.
+
+## Requirements
+- Add a note to the Git Instructions section in the execution prompt
+- Mention that plan files in the `plans/` folder should be committed if they exist
+- Keep the instruction concise and integrated with existing commit flow
+- Do not change the commit message format
+
+## Implementation Steps
+1. Read `src/prompts/execution.ts` to understand the current git instructions (lines 89-101)
+2. Add a line to the commit instructions mentioning plan files, e.g.:
+   - "This includes any plan files in the `plans/` folder"
+   - Or: "Note: `git add -A` will include plan files if any were added"
+3. Ensure the instruction fits naturally with the existing text
+4. Test that the prompt generates correctly
+
+## Acceptance Criteria
+- [ ] Git Instructions section mentions plan files
+- [ ] Instruction is clear and concise
+- [ ] Does not break existing prompt structure
+- [ ] Execution prompt unit tests pass (if any exist)
+
+## Notes
+- The change is purely informational - `git add -A` already includes all files
+- This is a simple text addition to `src/prompts/execution.ts`
+- The commit message format remains `RAF[<project>:<task>] <description>`

package/RAF/015-name-lottery/plans/003-fix-input-md-in-amend-flow.md

@@ -0,0 +1,44 @@
+# Task: Fix input.md handling in amend flow
+
+## Objective
+Change the amend flow to append new task descriptions to input.md (instead of overwriting) and pass only the new input to Claude.
+
+## Context
+Currently during `raf plan --amend`, the input.md file handling may overwrite existing content. The correct behavior should be:
+1. Append new task descriptions to input.md with a horizontal rule separator
+2. Pass only the NEW task description to Claude (not the full input.md history)
+
+This preserves the complete project history in input.md while giving Claude only the relevant new information.
+
+## Requirements
+- Append new task descriptions to input.md with `---` separator
+- Pass only `newTaskDescription` to Claude in the amend prompt (not original input)
+- Preserve the original input.md content
+- Format: original content, then `---`, then new content
+
+## Implementation Steps
+1. Read `src/commands/plan.ts`, specifically `runAmendCommand()` (lines 210-378)
+2. After getting the new task description (around line 303-310):
+   - Read the existing input.md content
+   - Append a horizontal rule (`---`) and the new task description
+   - Write the combined content back to input.md
+3. Review `src/prompts/amend.ts` `getAmendPrompt()`:
+   - Ensure only `newTaskDescription` is passed in the user message (currently correct at line 188-192)
+   - The `inputContent` param may not be needed in the user message if Claude reads input.md directly
+4. Add/update tests for the amend flow
+
+## Acceptance Criteria
+- [ ] New task descriptions are appended to input.md (not overwriting)
+- [ ] Horizontal rule (`---`) separates original from new content
+- [ ] Claude receives only the new task description in the user message
+- [ ] Original input.md content is preserved
+- [ ] Multiple amend operations append correctly (each with separator)
+- [ ] Tests cover the append behavior
+
+## Notes
+- File locations:
+  - `src/commands/plan.ts` - amend command logic
+  - `src/prompts/amend.ts` - amend prompt generation
+  - `src/core/project-manager.ts` - may have utility for saving input
+- The amend prompt system message already instructs Claude to read input.md for context
+- Consider using `fs.appendFileSync` or reading/writing the full file

package/README.md

@@ -0,0 +1,116 @@
+# RAF - Automated Task Planning & Execution with Claude Code
+
+[![npm version](https://img.shields.io/npm/v/raf.svg)](https://www.npmjs.com/package/raf)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Node.js](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen.svg)](https://nodejs.org/)
+
+RAF is a CLI tool that orchestrates task planning and execution using Claude Code CLI.
+
+**GitHub:** [https://github.com/john-veresk/raf](https://github.com/john-veresk/raf)
+
+## Features
+
+- **Interactive Planning**: Claude interviews you to break down complex tasks
+- **Smart Project Naming**: Auto-generates descriptive project names using Claude Haiku
+- **Automated Execution**: Execute plans with retry logic and progress tracking
+- **Resume Support**: Continue from where you left off after interruption
+- **Git Integration**: Automatic commits after each completed task
+- **Multi-Project Execution**: Run multiple projects in sequence
+
+## Installation
+
+```bash
+npm install -g raf
+```
+
+## Requirements
+
+- Node.js 20+
+- Claude Code CLI installed and configured
+
+## Usage
+
+### Plan a Project
+
+```bash
+raf plan [projectName]
+```
+
+Opens your `$EDITOR` to write a project description, then Claude will:
+1. Identify 3-8 distinct tasks
+2. Interview you about each task
+3. Create detailed plan files
+
+To add tasks to an existing project:
+
+```bash
+raf plan --amend <identifier>
+```
+
+### Execute Plans
+
+```bash
+raf do <projects...>
+```
+
+Execute one or more projects. Accepts project identifiers in multiple formats:
+
+```bash
+raf do my-project           # By name
+raf do 3                    # By number
+raf do 001-my-project       # By folder name
+raf do 3 4 5                # Multiple projects
+```
+
+Options:
+- `-t, --timeout <minutes>` - Timeout per task (default: 60)
+- `-v, --verbose` - Show full Claude output
+- `-d, --debug` - Save all logs and show debug output
+- `-f, --force` - Re-run all tasks regardless of status
+
+### Check Status
+
+```bash
+raf status [identifier]
+```
+
+Without an identifier, lists all projects with their status. With an identifier, shows detailed task list:
+
+```bash
+raf status              # List all projects
+raf status my-project   # Show details for a project
+raf status 3            # By project number
+raf status --json       # Output as JSON
+```
+
+Status badges:
+- `[ ]` pending
+- `[x]` completed
+- `[!]` failed
+
+Project status badges:
+- `[P]` planning
+- `[R]` ready
+- `[~]` executing
+- `[x]` completed
+- `[!]` failed
+
+## Project Structure
+
+RAF creates a `./RAF/` folder with numbered project directories:
+
+```
+./RAF/
+├── 001-auth-system/
+│   ├── input.md           # Your original description
+│   ├── decisions.md       # Design decisions from planning
+│   ├── plans/             # Generated task plans
+│   ├── outcomes/          # Execution results
+│   └── logs/              # Debug logs (on failure)
+└── 002-dashboard/
+    └── ...
+```
+
+## License
+
+MIT

package/dist/commands/do.d.ts

@@ -0,0 +1,12 @@
+import { Command } from 'commander';
+/**
+ * Format failure history for console output.
+ * Shows attempts that failed before eventual success or final failure.
+ * Returns empty string if no failures occurred.
+ */
+export declare function formatRetryHistoryForConsole(taskId: string, taskName: string, failureHistory: Array<{
+    attempt: number;
+    reason: string;
+}>, finalAttempt: number, success: boolean): string;
+export declare function createDoCommand(): Command;
+//# sourceMappingURL=do.d.ts.map

package/dist/commands/do.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"do.d.ts","sourceRoot":"","sources":["../../src/commands/do.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAiCpC;;;;GAIG;AACH,wBAAgB,4BAA4B,CAC1C,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,MAAM,EAChB,cAAc,EAAE,KAAK,CAAC;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,CAAC,EAC1D,YAAY,EAAE,MAAM,EACpB,OAAO,EAAE,OAAO,GACf,MAAM,CAkBR;AA0BD,wBAAgB,eAAe,IAAI,OAAO,CAgBzC"}