rafcode 1.0.0

package/RAF/011-do-task-in-commit/outcomes/001-update-execution-prompt.md

@@ -0,0 +1,54 @@
+# Task 001: Update Execution Prompt
+
+## Summary
+
+Updated the execution prompt to instruct Claude to write meaningful commit messages describing what was accomplished, instead of using a fixed project-name + task-name format.
+
+## Changes Made
+
+### Files Modified
+
+1. **src/prompts/execution.ts**
+   - Removed `projectName` and `taskName` from `ExecutionPromptParams` interface
+   - Removed `projectName` and `taskName` from destructuring in `getExecutionPrompt()`
+   - Updated commit instructions to use `<description>` placeholder with guidance to write meaningful descriptions
+
+2. **src/commands/do.ts**
+   - Removed `projectName` and `taskName` parameters from the `getExecutionPrompt()` call
+
+3. **tests/unit/execution-prompt.test.ts**
+   - Updated `baseParams` to remove `projectName` and `taskName`
+   - Updated test expectations to check for new `<description>` format
+   - Removed tests that checked for project/task name in commit message
+   - Added new test to verify instructions for meaningful descriptions
+
+### New Commit Message Format
+
+Old format:
+```
+RAF[005:001] project-name task-name
+```
+
+New format:
+```
+RAF[005:001] <description>
+   - Write a concise description of what was accomplished
+   - Focus on the actual change, not the task name
+```
+
+## Acceptance Criteria Verification
+
+- [x] Commit instructions tell Claude to write meaningful descriptions
+- [x] RAF prefix `RAF[project:task]` is preserved in the format
+- [x] `projectName` and `taskName` parameters removed from interface
+- [x] TypeScript compiles without errors (`npm run build` passes)
+- [x] No changes to other prompt sections (outcome file, retry context, etc.)
+- [x] All 543 tests pass
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 2
+- Elapsed time: 3m 50s
+- Completed at: 2026-01-31T12:35:09.297Z

package/RAF/011-do-task-in-commit/outcomes/002-update-tests.md

@@ -0,0 +1,61 @@
+# Task 002: Update Tests
+
+## Summary
+
+Verified that the execution prompt unit tests have been updated to reflect the new commit message format. The test changes were already completed as part of Task 001, so this task involved verification rather than implementation.
+
+## Verification Results
+
+### Acceptance Criteria Status
+
+- [x] All tests pass with `npm test` - 543 tests pass
+- [x] Tests verify RAF prefix format is preserved - Tests check for `RAF[005:001]`, `RAF[a05:001]`, etc.
+- [x] Tests verify task number padding still works - Tests for single (001), double (012), and triple (123) digit padding
+- [x] Tests verify instruction for meaningful description is present - Test checks for "Write a concise description of what was accomplished"
+- [x] No tests checking for exact `projectName taskName` format - All tests now use `<description>` format
+- [x] Test coverage maintained for commit-related functionality - 27 tests in execution-prompt.test.ts
+
+### Test Changes (from Task 001)
+
+The following changes were made to `tests/unit/execution-prompt.test.ts`:
+
+1. **baseParams fixture updated** - Removed `projectName` and `taskName` properties
+2. **Commit Message Format tests updated**:
+   - Changed from checking exact `projectName taskName` format to `<description>` placeholder
+   - Added test `should instruct to write meaningful description`
+   - Kept all padding tests (001, 012, 123)
+   - Kept base36 project number test
+   - Kept autoCommit=false test
+3. **Complete Commit Message tests updated**:
+   - All tests now check for `<description>` instead of literal project/task names
+
+### Tests Verified
+
+```
+Commit Message Format
+  ✓ should include RAF commit schema format with description placeholder in prompt
+  ✓ should instruct to write meaningful description
+  ✓ should zero-pad single digit task numbers
+  ✓ should zero-pad double digit task numbers
+  ✓ should not pad triple digit task numbers
+  ✓ should include project number from base36 prefix
+  ✓ should not include commit instructions when autoCommit is false
+
+Complete Commit Message
+  ✓ should generate correct commit message format for task 006
+  ✓ should generate correct commit message format for first task
+  ✓ should generate correct commit message format for base36 project
+```
+
+## Notes
+
+- No code changes were needed for this task as the test updates were included in Task 001
+- This task served as a verification checkpoint to ensure test coverage is maintained
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 2
+- Elapsed time: 3m 6s
+- Completed at: 2026-01-31T12:38:15.976Z

package/RAF/011-do-task-in-commit/outcomes/003-update-documentation.md

@@ -0,0 +1,51 @@
+# Task 003: Update Documentation
+
+## Summary
+
+Updated CLAUDE.md to document the new commit message format where Claude writes meaningful descriptions instead of the fixed project-name + task-name format.
+
+## Changes Made
+
+### File Modified
+
+**CLAUDE.md** - Git Commit Schema section (lines 113-136)
+
+### Documentation Updates
+
+1. **Separated commit types** - Split the schema into two clearly labeled sections:
+   - "RAF-generated commits" (fixed format) - for plan and outcome commits
+   - "Claude-generated commits" (during task execution) - for task commits
+
+2. **Updated task commit format** - Changed from:
+   ```
+   RAF[<project-number>:<task>]    - Claude commits during task execution
+   ```
+   To:
+   ```
+   RAF[<project-number>:<task>] <description>
+   ```
+
+3. **Added explanation** - Added clarification that "Claude writes a concise description of what was accomplished, focusing on the actual change rather than the task name."
+
+4. **Added examples** - Included three realistic commit message examples:
+   ```
+   RAF[005:001] Add validation for user input fields
+   RAF[005:002] Fix null pointer in auth handler
+   RAF[a01:003] Refactor database connection pooling
+   ```
+
+## Acceptance Criteria Verification
+
+- [x] Git Commit Schema section updated with new format
+- [x] Clear explanation that Claude writes the description
+- [x] Example provided showing realistic commit message
+- [x] Distinction between RAF commits and Claude commits maintained
+- [x] No changes to other sections of CLAUDE.md
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 2
+- Elapsed time: 1m 42s
+- Completed at: 2026-01-31T12:39:58.591Z

package/RAF/011-do-task-in-commit/plans/001-update-execution-prompt.md

@@ -0,0 +1,46 @@
+# Task: Update Execution Prompt
+
+## Objective
+Modify the execution prompt to instruct Claude to write meaningful commit messages describing what the task accomplished, instead of using a fixed project-name + task-name format.
+
+## Context
+Currently, the execution prompt in `src/prompts/execution.ts` tells Claude to commit with a fixed message format:
+```
+RAF[005:001] project-name task-name
+```
+
+This format is not descriptive of what was actually done. We want Claude to write commit messages with a concise task description, without the project name.
+
+## Requirements
+- Keep the `RAF[project:task]` prefix format (e.g., `RAF[005:001]`)
+- Remove both `projectName` and `taskName` from the commit message
+- Instruct Claude to write a concise description of what was accomplished
+- Do NOT include project name in commit message
+- Provide minimal guidance (not strict rules like conventional commits)
+- Only change commit instructions when `autoCommit` is true
+
+Example new format:
+```
+RAF[005:001] Add validation for user input fields
+RAF[005:002] Fix null pointer in auth handler
+```
+
+## Implementation Steps
+1. Read `src/prompts/execution.ts` to understand the current implementation
+2. Modify the `commitInstructions` section (lines 48-56) to:
+   - Keep the RAF prefix format: `RAF[${projectNumber}:${paddedTaskNumber}]`
+   - Replace fixed message with instruction to write a meaningful description
+3. Remove `projectName` and `taskName` parameters from the interface and function since they're no longer needed for commit messages
+4. Update the `ExecutionPromptParams` interface to remove unused parameters
+5. Build and verify TypeScript compiles without errors
+
+## Acceptance Criteria
+- [ ] Commit instructions tell Claude to write meaningful descriptions
+- [ ] RAF prefix `RAF[project:task]` is preserved in the format
+- [ ] `projectName` and `taskName` parameters removed from interface (if unused elsewhere)
+- [ ] TypeScript compiles without errors
+- [ ] No changes to other prompt sections (outcome file, retry context, etc.)
+
+## Notes
+- The `projectName` and `taskName` might still be used elsewhere in the prompt or codebase - check before removing from interface
+- The commit message format change only affects the instructions given to Claude, not any RAF code that generates commits

package/RAF/011-do-task-in-commit/plans/002-update-tests.md

@@ -0,0 +1,51 @@
+# Task: Update Tests
+
+## Objective
+Update the execution prompt unit tests to reflect the new commit message format that instructs Claude to write meaningful descriptions.
+
+## Context
+The test file `tests/unit/execution-prompt.test.ts` has tests that verify the old commit message format:
+- `should include RAF commit schema format in prompt` - checks for exact format like `RAF[005:001] task-naming-improvements enhance-identifier-resolution`
+- `should include task name in commit message` - checks for task name
+- `should include project name in commit message` - checks for project name
+- `Complete Commit Message` describe block - multiple tests checking exact commit message format
+
+These tests need to be updated to reflect the new behavior.
+
+## Requirements
+- Update tests to verify the new commit message format
+- Tests should verify:
+  - RAF prefix is still present (e.g., `RAF[005:001]`)
+  - Task number zero-padding still works
+  - Instruction to write concise description is present
+  - Git Instructions section is present when autoCommit is true
+  - Git Instructions section is absent when autoCommit is false
+  - Project name is NOT in the commit message instruction
+- Remove tests that check for exact `projectName taskName` format
+- Update `baseParams` if `projectName`/`taskName` are removed from interface
+
+## Implementation Steps
+1. Read `tests/unit/execution-prompt.test.ts` to understand current test structure
+2. Update the `Commit Message Format` describe block:
+   - Modify test for exact format to check for new instruction style
+   - Keep tests for zero-padding (001, 012, 123)
+   - Keep test for base36 project numbers
+   - Update or remove tests checking for taskName and projectName in commit message
+3. Update the `Complete Commit Message` describe block:
+   - Remove tests that check for exact `projectName taskName` format
+   - Add tests that verify meaningful description instruction is present
+4. Update `baseParams` fixture if interface changed
+5. Run tests to verify they pass
+
+## Acceptance Criteria
+- [ ] All tests pass with `npm test`
+- [ ] Tests verify RAF prefix format is preserved
+- [ ] Tests verify task number padding still works
+- [ ] Tests verify instruction for meaningful description is present
+- [ ] No tests checking for exact `projectName taskName` format
+- [ ] Test coverage maintained for commit-related functionality
+
+## Notes
+- Depends on Task 001 being completed first
+- Some tests may need to be removed entirely if they tested specific format that no longer exists
+- Consider adding a test that verifies the wording of the new instruction

package/RAF/011-do-task-in-commit/plans/003-update-documentation.md

@@ -0,0 +1,45 @@
+# Task: Update Documentation
+
+## Objective
+Update CLAUDE.md to reflect the new commit message format where Claude writes meaningful descriptions instead of fixed project-name + task-name.
+
+## Context
+CLAUDE.md documents the Git Commit Schema in the "Architectural Decisions" section (around line 113-121). The current documentation shows:
+```
+RAF[<project-number>:plan]      - After planning phase completes
+RAF[<project-number>:outcome]   - After all tasks complete
+RAF[<project-number>:<task>]    - Claude commits during task execution
+```
+
+This needs to be updated to reflect that task commits now include meaningful descriptions written by Claude.
+
+## Requirements
+- Update the Git Commit Schema section to show the new format
+- Explain that Claude writes a concise description of what was accomplished
+- Note that project name is NOT included in task commits (only in RAF-generated plan/outcome commits)
+- Keep documentation of `plan` and `outcome` commits unchanged (those are made by RAF, not Claude)
+- Add examples showing realistic commit messages:
+  ```
+  RAF[005:001] Add validation for user input fields
+  RAF[005:002] Fix null pointer in auth handler
+  ```
+
+## Implementation Steps
+1. Read CLAUDE.md and locate the Git Commit Schema section
+2. Update the task-level commit format to show it includes a description
+3. Add an example showing what a real commit message might look like
+4. Ensure the documentation distinguishes between:
+   - RAF-generated commits (plan, outcome) - fixed format
+   - Claude-generated commits (task) - meaningful description
+
+## Acceptance Criteria
+- [ ] Git Commit Schema section updated with new format
+- [ ] Clear explanation that Claude writes the description
+- [ ] Example provided showing realistic commit message
+- [ ] Distinction between RAF commits and Claude commits maintained
+- [ ] No changes to other sections of CLAUDE.md
+
+## Notes
+- This is documentation only, no code changes
+- The plan and outcome commit formats remain unchanged
+- Only the task-level commits (made by Claude during execution) are affected

package/RAF/012-name-picker-buffet/decisions.md

@@ -0,0 +1,40 @@
+# Project Decisions
+
+## For the name picker feature: When generating project names, should the name-generating model also have access to the project description (input.md content) to make relevant suggestions?
+Yes, use full context - Claude sees the project description to suggest relevant names.
+
+## How should the name selection UI work?
+Arrow key navigation - Interactive menu with arrow keys to select.
+
+## For the `raf do` project picker: How should pending projects be displayed when no project name is given?
+List all pending with arrow selection - Show all pending projects, user navigates with arrows.
+
+## For `raf status` truncation: When showing only the last 10 projects, how should older projects be indicated?
+"... and N more" at top - Shows count of hidden older projects.
+
+## For failure reason details: Should the bullet points show ALL previous failure attempts, or just the most recent one?
+All attempts - Show bullet point for each failed attempt with reason.
+
+## For the name generation model: Which model should generate project name suggestions?
+Claude Sonnet - More capable model for creative naming.
+
+## For arrow key selection UI (both name picker and project picker): Which library should be used?
+Use a library that supports navigation with arrow keys + custom input option. Options considered:
+- `inquirer-list-input` plugin - allows list selection with arbitrary user input
+- Standard `@inquirer/prompts` with chained prompts (list + conditional input for "Other")
+Recommendation: Use `@inquirer/prompts` (modern inquirer) with "Other (enter custom name)" as a choice that triggers an input prompt.
+
+## Should RAF commit at any point, or should Claude handle all commits?
+Claude handles ALL commits. One task = one commit (code changes + outcome file together). RAF should NOT make any commits - neither after planning nor after project completion. The execution prompt needs to include file location instructions so Claude knows where to write the outcome file.
+
+## Should Claude commit the outcome file in the same commit as code changes, or separately?
+Same commit as code - one commit contains both the code changes and the outcome file.
+
+## How should name generation handle projects with many unrelated tasks?
+When the project description has many unrelated/disconnected tasks, prefer more abstract, metaphorical, or fun names instead of trying to be descriptive. A name like "spring-cleaning" or "grab-bag" is better than trying to describe all the unrelated tasks.
+
+## [Amendment] For the plan mode fix: Should the user's project description from input.md be passed as the user message (with instructions in system prompt)?
+Project description as user message - Pass the input.md content as user message, keep planning instructions in system prompt.
+
+## [Amendment] For the dangerously-skip-permissions flag in plan mode: What should the CLI flag be named?
+CLI flag --auto or -y - A shorter flag name that implies auto-approve, matching common CLI conventions.

package/RAF/012-name-picker-buffet/input.md

@@ -0,0 +1,6 @@
+- [ ] generate several name for project name (3-5) and let user pick or provide own name if user didn't specified name in "raf plan", instruct the name generating model to have variety in style for names (fun, metaphor, descriptive, somewhat related and fun etc)
+- [ ] raf do without project name allows you to pick form pending projects
+- [ ] raf status shows list of 10 last projects (with note on top what list was cut - ...)
+- [ ] in outcome details section add short description for failure reasons (with bullet point for each failed attempt)
+- [ ] don't do output commit since claude does it within the task
+- [ ] instruct claude to do output file commit alongside the code and only after that produce <promise>COMPLETE</promise>

package/RAF/012-name-picker-buffet/outcomes/001-name-picker-for-raf-plan.md

@@ -0,0 +1,49 @@
+# Outcome: Name Picker for `raf plan`
+
+## Summary
+
+Implemented an interactive name picker that generates 3-5 creative project name suggestions using Claude Sonnet and allows users to select from them using arrow-key navigation or provide a custom name.
+
+## Key Changes
+
+### New Files
+- **src/ui/name-picker.ts**: Interactive UI component using `@inquirer/prompts` for arrow-key selection
+- **tests/unit/name-picker.test.ts**: Comprehensive tests for the name picker (13 tests)
+
+### Modified Files
+- **package.json**: Added `@inquirer/prompts` as a dependency
+- **src/utils/name-generator.ts**: Added `generateProjectNames()` function that returns 3-5 names with varied styles (metaphorical, fun/playful, action-oriented, abstract, cultural reference)
+- **src/commands/plan.ts**: Updated to use the new multi-name generation and picker flow
+- **tests/unit/name-generator.test.ts**: Added tests for multi-name generation (21 new tests)
+
+## Features Implemented
+
+1. **Multi-name generation**: Claude Sonnet generates 5 names with different styles:
+   - Metaphorical (e.g., 'phoenix', 'lighthouse')
+   - Fun/Playful (e.g., 'turbo-boost', 'magic-beans')
+   - Action-oriented (e.g., 'bug-squasher', 'speed-demon')
+   - Abstract (e.g., 'horizon', 'cascade')
+   - Cultural reference (e.g., 'atlas', 'merlin')
+
+2. **Interactive selection**: Users can navigate with arrow keys and press Enter to select
+
+3. **Custom name option**: "Other (enter custom name)" option triggers text input with validation
+
+4. **Robust fallback**: Falls back to single word-extraction name if API fails
+
+## Acceptance Criteria Met
+
+- ✅ Running `raf plan` without a name shows 3-5 generated names
+- ✅ Names have variety in style (not all the same pattern)
+- ✅ User can select with arrow keys and Enter
+- ✅ User can choose "Other" and type custom name
+- ✅ Selected name is used for project folder creation
+- ✅ All tests pass (577 total)
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 1
+- Elapsed time: 3m 45s
+- Completed at: 2026-01-31T14:01:55.680Z

package/RAF/012-name-picker-buffet/outcomes/002-interactive-project-picker-for-raf-do.md

@@ -0,0 +1,49 @@
+# Outcome: Interactive Project Picker for `raf do`
+
+## Summary
+
+Implemented an interactive project picker that allows users to run `raf do` without specifying a project name. When no arguments are provided, the command displays a list of pending projects with arrow-key navigation for selection.
+
+## Key Changes
+
+### New Files
+- **src/ui/project-picker.ts**: Interactive UI component for selecting pending projects
+  - `getPendingProjects()`: Filters projects to only show those with pending/failed tasks
+  - `formatProjectChoice()`: Formats project display as "001 fix-auth-bug (2/5 tasks)"
+  - `pickPendingProject()`: Shows interactive selection using `@inquirer/prompts`
+- **tests/unit/project-picker.test.ts**: Comprehensive tests for the project picker (14 tests)
+
+### Modified Files
+- **src/commands/do.ts**: Updated to support optional project argument
+  - Changed `<projects...>` to `[projects...]` making the argument optional
+  - Added interactive picker flow when no arguments provided
+  - Shows "No pending projects found" message when list is empty
+  - Handles Ctrl+C gracefully for cancellation
+
+## Features Implemented
+
+1. **Pending project detection**: Scans RAF directory for projects with pending or failed tasks
+2. **Task progress display**: Shows completion status like "(2/5 tasks)" for each project
+3. **Arrow-key navigation**: Uses `@inquirer/prompts` select for interactive selection
+4. **Sorted by project number**: Projects shown oldest first (by number)
+5. **Graceful handling**:
+   - Empty list shows friendly message
+   - Ctrl+C exits cleanly without error
+
+## Acceptance Criteria Met
+
+- [x] Running `raf do` without arguments shows pending projects list
+- [x] Projects show number, name, and progress (X/Y tasks)
+- [x] User can navigate with arrow keys and select with Enter
+- [x] Selected project is executed
+- [x] Empty list shows friendly message "No pending projects found"
+- [x] Ctrl+C exits gracefully
+- [x] All tests pass (591 total)
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 1
+- Elapsed time: 3m 25s
+- Completed at: 2026-01-31T14:05:20.699Z

package/RAF/012-name-picker-buffet/outcomes/003-raf-status-truncation.md

@@ -0,0 +1,55 @@
+# Outcome: Enhanced `raf status` with Last 10 Projects Truncation
+
+## Summary
+
+Implemented truncation of `raf status` output to show only the last 10 projects by default, with a dimmed indicator at the top showing how many more projects exist.
+
+## Key Changes
+
+### Modified Files
+- **src/commands/status.ts**:
+  - Added `MAX_DISPLAYED_PROJECTS = 10` constant
+  - Modified `listAllProjects()` to slice to last N projects when total exceeds max
+  - Added truncation indicator at top: "... and N more project(s)" in dim text
+  - JSON output remains unchanged (returns all projects)
+
+- **src/utils/logger.ts**:
+  - Added `dim()` method for visually distinct truncation indicator (uses ANSI dim escape code)
+
+- **tests/unit/status-command.test.ts**:
+  - Added new test suite "Status Command - Truncation Behavior" with 8 tests covering:
+    - Projects below max (no truncation)
+    - Projects at exactly max
+    - Projects above max (truncation)
+    - Correct slicing behavior (last N projects)
+    - Correct hidden count calculation
+    - Ascending order preserved after slicing
+    - Edge case: exactly max + 1 projects
+
+## Acceptance Criteria Met
+
+- [x] `raf status` shows max 10 projects
+- [x] When > 10 projects exist, shows "... and N more projects" at top
+- [x] Projects are sorted by number (ascending) with newest at bottom
+- [x] When <= 10 projects, no truncation indicator shown
+- [x] Individual project status (`raf status <id>`) unchanged
+- [x] All tests pass (599 total)
+
+## Example Output
+
+When there are 15 projects:
+```
+... and 5 more projects
+006 project-f ●○○ (0/3)
+007 project-g ✓✓● (2/3)
+...
+015 project-o ✓✓✓ (3/3)
+```
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 1
+- Elapsed time: 2m 7s
+- Completed at: 2026-01-31T14:07:27.762Z

package/RAF/012-name-picker-buffet/outcomes/004-failure-reason-details.md

@@ -0,0 +1,65 @@
+# Outcome: Failure Reason Details in Outcome Files
+
+## Summary
+
+Added a "Failure History" section to outcome files that lists all previous failure attempts with bullet points for each failure reason, showing the journey from failed attempts to eventual success (or final failure).
+
+## Key Changes
+
+### New Files
+- **tests/unit/failure-history.test.ts**: Comprehensive tests for the `formatFailureHistory` function (12 tests)
+
+### Modified Files
+- **src/commands/do.ts**:
+  - Added `formatFailureHistory()` function that formats failure history as a markdown section
+  - Added `failureHistory` array to track all failure reasons across retry attempts
+  - Updated all failure paths (timeout, context overflow, parsed failure, outcome file failure, no marker) to record failures
+  - Integrated failure history into both success and failure outcome generation
+  - For success: inserts failure history before `<promise>COMPLETE</promise>` marker
+  - For failure: inserts failure history before `<promise>FAILED</promise>` marker
+
+## Features Implemented
+
+1. **Failure tracking**: All failed attempts are recorded with their attempt number and reason
+2. **Success tracking**: Final successful attempt is shown when preceded by failures
+3. **Clean runs**: No failure history section is added when there are no failures
+4. **Proper placement**: Failure history appears before the `<promise>` marker as specified
+
+## Example Output
+
+When task fails twice then succeeds:
+```markdown
+## Failure History
+- **Attempt 1**: Context overflow detected after 45 minutes
+- **Attempt 2**: API rate limit exceeded
+- **Attempt 3**: Success
+
+<promise>COMPLETE</promise>
+```
+
+When task fails all retries:
+```markdown
+## Failure History
+- **Attempt 1**: Task timed out
+- **Attempt 2**: Task timed out
+- **Attempt 3**: Context overflow - task too large
+
+<promise>FAILED</promise>
+```
+
+## Acceptance Criteria Met
+
+- [x] Outcome files include failure history when any attempts failed
+- [x] Each failed attempt shows attempt number and short reason
+- [x] Successful final attempt also shows in history (if preceded by failures)
+- [x] Clean runs (no failures) don't show failure history section
+- [x] Failure reasons are concise (1-2 sentences)
+- [x] All tests pass (611 total, 12 new for failure history)
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 1
+- Elapsed time: 3m 29s
+- Completed at: 2026-01-31T14:10:57.686Z

package/RAF/012-name-picker-buffet/outcomes/005-remove-raf-commits.md

@@ -0,0 +1,57 @@
+# Outcome: Remove All RAF-Side Git Commits
+
+## Summary
+
+Removed all git commit operations from RAF. Claude now handles all commits during task execution - one commit per task containing both code changes and the outcome file.
+
+## Key Changes
+
+### Files Modified
+
+- **src/commands/plan.ts**:
+  - Removed import of `commitProjectFolder`
+  - Removed import of `extractProjectNumber` (no longer needed)
+  - Removed commit logic after planning phase completes
+  - Removed commit logic after amendment phase completes
+
+- **src/commands/do.ts**:
+  - Removed import of `commitProjectFolder`
+  - Removed commit logic when project completes (`isProjectComplete`)
+  - Kept `stashChanges` and `hasUncommittedChanges` for failure handling
+
+- **src/core/git.ts**:
+  - Removed `CommitResult` interface
+  - Removed `CommitType` type
+  - Removed `commitProjectFolder` function
+  - Kept utility functions: `isGitRepo`, `getGitStatus`, `hasUncommittedChanges`, `parseGitStatus`, `getChangedFiles`, `stashChanges`
+
+- **CLAUDE.md**:
+  - Updated "Git Commit Schema" section
+  - Removed "RAF-generated commits" section (`RAF[NNN:plan]`, `RAF[NNN:outcome]`)
+  - Updated to reflect that all commits are now Claude-generated during task execution
+  - Added note that code changes and outcome file are committed together
+
+### Files Deleted
+
+- **tests/unit/git-commit-project.test.ts**: Removed tests for the deleted `commitProjectFolder` function (11 tests)
+
+## Acceptance Criteria Met
+
+- [x] `raf plan` does not create any git commits
+- [x] `raf do` does not create any git commits
+- [x] Git stashing on failure still works
+- [x] No errors when running in non-git directories
+- [x] CLAUDE.md updated to reflect new workflow
+- [x] All tests pass (600 total after removing 11 commit tests)
+
+## Notes
+
+This is a simplification of the codebase - less code, clearer responsibility. Claude handles all commits during task execution, making the workflow more straightforward and giving Claude full control over what gets committed and when.
+
+<promise>COMPLETE</promise>
+
+
+## Details
+- Attempts: 1
+- Elapsed time: 2m 55s
+- Completed at: 2026-01-31T14:13:53.207Z