rafcode 1.0.0

package/RAF/005-task-naming-improvements/outcomes/004-implement-amend-flag-for-plan.md

@@ -0,0 +1,55 @@
+## Status: SUCCESS
+
+# Task 004 - Completed
+
+## Summary
+The task has been completed successfully. Let me summarize the implementation:
+## Summary
+I have successfully completed Task 004: Implement `--amend` Flag for `raf plan`.
+### Changes Made
+**1. `src/commands/plan.ts`** - Updated plan command:
+- Added `-a, --amend <identifier>` option to Commander.js definition
+- Added check when creating new project: if project name matches existing project, show error with suggestion to use `--amend`
+- Implemented `runAmendCommand()` function that:
+  - Resolves project using all identifier formats (number, name, full folder name)
+  - Loads existing project state (tasks with completed/pending/failed status)
+  - Shows warning for fully completed projects
+  - Opens editor with template showing existing tasks as read-only context
+  - Launches Claude with amend-specific prompt
+  - Detects and reports only newly created plan files
+  - Commits the changes
+- Added `getAmendTemplate()` function for editor content
+**2. `src/prompts/amend.ts`** - New file with amend-specific prompt:
+- Includes AMENDMENT MODE instructions
+- Lists existing tasks with their status ([COMPLETED], [PENDING], [FAILED])
+- Instructs Claude to start numbering from next available task number
+- Explicitly forbids modification of existing plan files
+- Includes original input and new task description
+**3. `tests/unit/plan-command.test.ts`** - New test file with 27 tests:
+- Project resolution for amend (numeric ID, name, full folder name)
+- Base36 project resolution for amend
+- Existing project state loading (pending, completed, failed, mixed)
+- Fully completed project detection
+- Task name extraction
+- Next task number calculation
+- Amend prompt generation
+- Existing project detection without amend flag
+### Acceptance Criteria Verification
+- ✅ `raf plan --amend 003` opens editor then launches Claude with existing task context
+- ✅ `raf plan --amend 001-my-project` works with full folder name identifier
+- ✅ `raf plan existing-project` (without `--amend`) shows clear error message
+- ✅ Claude receives context about existing tasks and their status
+- ✅ New tasks are numbered correctly (continuing from last task number)
+- ✅ Warning is displayed when amending a fully completed project
+- ✅ Amending creates new plan files without touching existing ones
+- ✅ Tests cover the amend workflow (27 new tests)
+- ✅ Help text documents the `--amend` option
+### Test Results
+- All 368 tests pass
+- TypeScript build succeeds with no errors
+<promise>COMPLETE</promise>
+
+## Details
+- Attempts: 1
+- Elapsed time: 4m 2s
+- Completed at: 2026-01-30T21:32:58.833Z

package/RAF/005-task-naming-improvements/outcomes/005-commit-outcomes-on-complete.md

@@ -0,0 +1,47 @@
+## Status: SUCCESS
+
+# Task 005 - Completed
+
+## Summary
+## Summary
+I have successfully completed Task 005: Universal Commit Schema for RAF.
+### Changes Made
+**1. `src/core/git.ts`** - Updated `commitProjectFolder` function:
+- Added new `CommitType` type (`'plan' | 'outcome'`)
+- Changed function signature from `(projectPath, projectName)` to `(projectPath, projectNumber, commitType)`
+- Updated commit message format from `RAF(${projectName}): Plan complete` to `RAF[${projectNumber}:${commitType}]`
+- Added default value for `commitType` parameter (`'plan'`)
+**2. `src/commands/plan.ts`** - Updated plan and amend commands:
+- Added import for `extractProjectNumber`
+- Updated `runPlanCommand()` to use new signature: `commitProjectFolder(projectPath, projectNum, 'plan')`
+- Updated `runAmendCommand()` to use new signature: `commitProjectFolder(projectPath, projectNum, 'plan')`
+**3. `src/commands/do.ts`** - Added outcome commit on project completion:
+- Added import for `commitProjectFolder`
+- Added outcome commit logic in `if (isProjectComplete(state))` block
+- Commits with format `RAF[<project-number>:outcome]` when all tasks complete successfully
+**4. `tests/unit/git-commit-project.test.ts`** - Updated and expanded tests:
+- Updated existing tests for new function signature
+- Added dedicated `describe('plan commits')` block with 3 tests
+- Added dedicated `describe('outcome commits')` block with 2 tests
+- Tests cover: plan format, outcome format, default type, base36 project numbers
+### Acceptance Criteria Verification
+- ✅ Git utility function supports both plan and outcome commit types
+- ✅ Plan commits use format `RAF[<project-number>:plan]`
+- ✅ Outcome commits use format `RAF[<project-number>:outcome]`
+- ✅ `raf plan` auto-commits project folder after successful planning
+- ✅ `raf do` auto-commits project folder when final task completes successfully
+- ✅ Only project folder is staged/committed, other repo changes are untouched
+- ✅ No commit is made if planning or final task fails
+- ✅ Graceful handling when not in a git repo (warning, no crash)
+- ✅ Graceful handling when there are no changes to commit
+- ✅ Tests cover both plan and outcome commit workflows
+- ✅ Success messages are logged after commits
+### Test Results
+- All 372 tests pass
+- TypeScript build succeeds with no errors
+<promise>COMPLETE</promise>
+
+## Details
+- Attempts: 1
+- Elapsed time: 3m 10s
+- Completed at: 2026-01-30T22:26:38.415Z

package/RAF/005-task-naming-improvements/outcomes/006-update-execution-prompt-commit-schema.md

@@ -0,0 +1,40 @@
+## Status: SUCCESS
+
+# Task 006 - Completed
+
+## Summary
+## Summary
+I have successfully completed Task 006: Update Execution Prompt for Universal Task Commit Schema.
+### Changes Made
+**1. `src/prompts/execution.ts`** - Updated execution prompt:
+- Added `projectNumber: string` field to `ExecutionPromptParams` interface (required)
+- Added `taskName: string` field to `ExecutionPromptParams` interface (required)
+- Made `projectName` required (removed optional `?`)
+- Added zero-padding for task number (3 digits)
+- Updated commit message format to: `RAF[${projectNumber}:${paddedTaskNumber}] ${projectName} ${taskName}`
+**2. `src/commands/do.ts`** - Updated do command:
+- Added extraction of `projectNumber` using `extractProjectNumber(projectPath)`
+- Updated `getExecutionPrompt()` call to pass `projectNumber` and `taskName`
+- Task name is extracted from plan file using `extractTaskNameFromPlanFile(task.planFile)`
+**3. `tests/unit/execution-prompt.test.ts`** - New test file with 19 tests:
+- Tests for RAF commit schema format in prompt
+- Tests for zero-padding of single, double, and triple digit task numbers
+- Tests for base36 project numbers
+- Tests for task name and project name in commit message
+- Tests for autoCommit=false case
+- Tests for various commit message combinations
+- Tests for task information, outcome file notes, and previous outcomes
+### Acceptance Criteria Verification
+- ✅ `ExecutionPromptParams` includes `projectNumber` and `taskName` fields
+- ✅ Execution prompt instructs Claude to use format `RAF[005:001] project-name task-name`
+- ✅ `do.ts` extracts and passes project number from folder name
+- ✅ `do.ts` extracts and passes task name from plan file name
+- ✅ Task number is zero-padded in commit message (001, 002, etc.)
+- ✅ Tests verify correct commit message format in prompt
+- ✅ All existing tests pass (391 tests total)
+<promise>COMPLETE</promise>
+
+## Details
+- Attempts: 1
+- Elapsed time: 2m 55s
+- Completed at: 2026-01-30T22:29:34.246Z

package/RAF/005-task-naming-improvements/outcomes/007-allow-pending-task-amendments.md

@@ -0,0 +1,38 @@
+## Status: SUCCESS
+
+# Task 007 - Completed
+
+## Summary
+## Summary
+I have successfully completed Task 007: Allow Pending Task Amendments in Amend Mode.
+### Changes Made
+**1. `src/prompts/amend.ts`** - Updated amend prompt:
+- Modified task summary to include `[PROTECTED]` for completed tasks and `[MODIFIABLE]` for pending/failed tasks
+- Added separate lists for protected tasks and modifiable tasks with clear headers
+- Updated "IMPORTANT: Amendment Mode" section to allow modification of [MODIFIABLE] tasks
+- Updated "Important Rules" section to distinguish between protected and modifiable tasks
+- Shows `(none)` when either category has no tasks
+**2. `tests/unit/plan-command.test.ts`** - Added and updated tests:
+- Updated existing tests for new prompt format
+- Added 7 new tests covering:
+  - Protected task listing
+  - Modifiable task listing
+  - Mixed task status handling
+  - `(none)` display when no tasks in a category
+  - Task status indicator verification
+### Acceptance Criteria Verification
+- ✅ Amend prompt allows modification of non-completed tasks (pending/failed)
+- ✅ Amend prompt prohibits modification of COMPLETED tasks
+- ✅ Prompt clearly lists which tasks are modifiable vs protected
+- ✅ Status indicators are clear: [PROTECTED], [MODIFIABLE]
+- ✅ Tests cover different task status combinations (7 new tests)
+- ✅ All existing tests pass (396 tests total)
+### Test Results
+- All 396 tests pass
+- TypeScript build succeeds with no errors
+<promise>COMPLETE</promise>
+
+## Details
+- Attempts: 1
+- Elapsed time: 2m 15s
+- Completed at: 2026-01-30T22:31:49.414Z

package/RAF/005-task-naming-improvements/outcomes/008-fix-timeout-label.md

@@ -0,0 +1,24 @@
+## Status: SUCCESS
+
+# Task 008 - Completed
+
+## Summary
+## Summary
+I have successfully completed Task 008: Fix Timeout Label.
+### Change Made
+**`src/commands/do.ts:227`** - Changed startup message label:
+- Before: `Tasks: ${state.tasks.length}, Timeout: ${timeout} minutes`
+- After: `Tasks: ${state.tasks.length}, Task timeout: ${timeout} minutes`
+### Acceptance Criteria Verification
+- ✅ The message displays "Task timeout:" instead of "Timeout:"
+- ✅ The rest of the message format remains unchanged
+- ✅ All existing tests pass (396 tests total)
+### Test Results
+- All 396 tests pass
+- TypeScript build succeeds with no errors
+<promise>COMPLETE</promise>
+
+## Details
+- Attempts: 1
+- Elapsed time: 36s
+- Completed at: 2026-01-30T22:35:52.807Z

package/RAF/005-task-naming-improvements/plans/001-enhance-identifier-resolution.md

@@ -0,0 +1,46 @@
+# Task: Enhance Identifier Resolution for Full Folder Names
+
+## Objective
+Extend the `resolveProjectIdentifier` function to support full folder names like `001-fix-stuff` or `a01-important-project` in addition to the existing number, base36, and name formats.
+
+## Context
+Currently `resolveProjectIdentifier()` in `src/utils/paths.ts` supports:
+- Numeric IDs: `3`, `003`
+- Base36 IDs: `a00`, `a01`
+- Project names: `fix-stuff`
+
+Users want to copy-paste full folder names directly from file explorers or terminal output. This enhancement is the foundation for consistent identifier support across all RAF commands.
+
+## Requirements
+- Support full folder name format: `NNN-project-name` or `XXX-project-name` (base36)
+- Extract the prefix and use existing resolution logic
+- Design the function to be extensible for future task-level references like `001-project/002-task`
+- Maintain backward compatibility with all existing identifier formats
+- All commands (`raf do`, `raf status`, `raf plan`) will share this enhanced resolution
+
+## Implementation Steps
+1. Read and understand the current `resolveProjectIdentifier()` function in `src/utils/paths.ts`
+2. Add a new identifier type detection for full folder names:
+   - Pattern: `^(\d{2,3}|[a-z][0-9a-z]{2})-(.+)$` to match `NNN-name` or `XXX-name`
+   - Extract prefix and validate it matches existing project
+3. Update the resolution logic order:
+   - Check if identifier is a full folder name first
+   - Then fall through to existing checks (numeric, base36, name)
+4. Add unit tests for the new identifier format:
+   - Test `001-fix-stuff` resolves correctly
+   - Test `a01-important-project` resolves correctly
+   - Test partial matches don't accidentally match (e.g., `001-wrong-name` should fail if folder is `001-correct-name`)
+5. Document the supported identifier formats in code comments
+
+## Acceptance Criteria
+- [ ] `resolveProjectIdentifier('001-fix-stuff')` returns the correct project path
+- [ ] `resolveProjectIdentifier('a01-important-project')` returns the correct project path
+- [ ] Invalid full folder names (wrong prefix or name) return appropriate errors
+- [ ] All existing identifier formats continue to work
+- [ ] Unit tests cover the new functionality
+- [ ] Function design allows for future task-level reference extension
+
+## Notes
+- The full folder name should be an exact match, not a partial match
+- Consider edge cases where the name portion contains hyphens (e.g., `001-my-cool-project`)
+- This task must be completed before tasks 002 and 003 can proceed

package/RAF/005-task-naming-improvements/plans/002-add-identifier-support-to-status.md

@@ -0,0 +1,36 @@
+# Task: Add Identifier Support to `raf status`
+
+## Objective
+Update the `raf status` command to accept all identifier formats (number, base36, full folder name, project name) for consistency with other commands.
+
+## Context
+Currently `raf status [projectName]` may only accept project names. After task 001 enhances `resolveProjectIdentifier`, this command should use that function to support all identifier formats, giving users a consistent experience across all RAF commands.
+
+## Requirements
+- `raf status 3` - status by numeric ID
+- `raf status 003` - status by zero-padded numeric ID
+- `raf status a00` - status by base36 ID
+- `raf status my-project` - status by project name (existing)
+- `raf status 001-my-project` - status by full folder name (new)
+- `raf status a00-my-project` - status by full folder name with base36 prefix (new)
+
+## Implementation Steps
+1. Read the current `status.ts` command implementation in `src/commands/`
+2. Identify how the project name/identifier is currently resolved
+3. Replace or update the resolution logic to use `resolveProjectIdentifier()` from `src/utils/paths.ts`
+4. Ensure error messages are clear when the identifier doesn't match any project
+5. Add integration tests for the status command with various identifier formats
+6. Update any help text or documentation for the command
+
+## Acceptance Criteria
+- [ ] `raf status 3` shows status for project 003
+- [ ] `raf status 001-fix-stuff` shows status for that project
+- [ ] `raf status a00-important` shows status for that project
+- [ ] Invalid identifiers show helpful error messages
+- [ ] `raf status` (no argument) continues to list all projects
+- [ ] Tests cover the new identifier support
+- [ ] `--json` output works correctly with all identifier formats
+
+## Notes
+- Depends on task 001 being completed first
+- The behavior when no project matches should be consistent with `raf do`

package/RAF/005-task-naming-improvements/plans/003-update-do-for-full-folder-names.md

@@ -0,0 +1,38 @@
+# Task: Update `raf do` for Full Folder Name Support
+
+## Objective
+Ensure `raf do` supports the full folder name identifier format (`001-fix-stuff`) for consistency across all RAF commands.
+
+## Context
+The `raf do` command already uses `resolveProjectIdentifier()` for project resolution. After task 001 enhances that function to support full folder names, this task ensures `raf do` works correctly with the new format and has appropriate tests.
+
+## Requirements
+- `raf do 001-fix-stuff` - execute project by full folder name
+- `raf do a00-important-project` - execute project by full folder name with base36 prefix
+- `raf do 001-fix-stuff 002-another-project` - multi-project execution with full folder names
+- All existing identifier formats must continue to work
+
+## Implementation Steps
+1. Read the current `do.ts` command implementation in `src/commands/`
+2. Verify it uses `resolveProjectIdentifier()` (it should based on the codebase exploration)
+3. After task 001 is complete, the function should automatically support full folder names
+4. Add integration tests specifically for full folder name support in `raf do`:
+   - Single project with full folder name
+   - Multiple projects mixing identifier formats
+   - Invalid full folder names
+5. Test verbose and debug modes with the new identifier format
+6. Update help text if needed
+
+## Acceptance Criteria
+- [ ] `raf do 001-fix-stuff` executes the correct project
+- [ ] `raf do a00-project` executes the correct project
+- [ ] `raf do 001-a 002-b` executes multiple projects correctly
+- [ ] Mixed formats work: `raf do 3 001-fix-stuff my-project`
+- [ ] Error messages are helpful for non-matching full folder names
+- [ ] All existing tests continue to pass
+- [ ] New tests cover full folder name scenarios
+
+## Notes
+- This task may be minimal if `raf do` already delegates entirely to `resolveProjectIdentifier()`
+- Depends on task 001 being completed first
+- Focus on testing rather than code changes if the integration is already correct

package/RAF/005-task-naming-improvements/plans/004-implement-amend-flag-for-plan.md

@@ -0,0 +1,67 @@
+# Task: Implement `--amend` Flag for `raf plan`
+
+## Objective
+Add a `--amend` flag to the `raf plan` command that allows adding new tasks to existing projects without modifying completed tasks.
+
+## Context
+Users need the ability to extend existing plans with new tasks as requirements evolve. The `--amend` flag provides a controlled way to add tasks while preserving the integrity of completed work.
+
+## Requirements
+- Command signature: `raf plan --amend <project-identifier>`
+- When `raf plan <existing-project>` is used without `--amend`, show an error
+- In amend mode:
+  - Open editor for user to describe new tasks (same as regular planning)
+  - Launch interactive Claude session with context of existing tasks
+  - Claude should see all existing tasks with their status (completed/pending/failed)
+  - New tasks are numbered sequentially after existing tasks
+  - Only adding new tasks is supported (no modification/deletion of existing)
+- Show warning if project is fully completed but allow amendment
+- Support all identifier formats for the project argument
+
+## Implementation Steps
+1. Read the current `plan.ts` command implementation in `src/commands/`
+2. Add the `--amend` option to the Commander.js command definition:
+   ```typescript
+   .option('-a, --amend <identifier>', 'Add tasks to an existing project')
+   ```
+3. Modify the command logic to detect existing project:
+   - If project identifier matches existing project AND no `--amend` flag → error with helpful message
+   - If `--amend` flag provided → enter amend mode
+4. Create or modify the planning prompt for amend mode:
+   - Include summary of existing tasks and their status
+   - Instruct Claude to add new tasks starting from the next number
+   - Preserve the original `input.md` content as context
+5. Load existing project state:
+   - Read all plan files from `plans/` directory
+   - Read outcomes from `outcomes/` directory
+   - Build task status summary (completed/pending/failed)
+6. Update the editor flow:
+   - Pre-populate with context about existing tasks (as reference)
+   - User adds description of NEW tasks only
+7. Launch interactive Claude session with the amend-specific prompt
+8. Handle the warning for fully completed projects:
+   - Check if all tasks are completed
+   - Display warning: "Project is fully completed. New tasks will extend the existing plan."
+   - Continue with amendment
+9. Add tests for:
+   - `raf plan --amend 003` with pending tasks
+   - `raf plan --amend 003` with all tasks completed (warning shown)
+   - `raf plan existing-project` without flag (error)
+   - Various identifier formats with `--amend`
+
+## Acceptance Criteria
+- [ ] `raf plan --amend 003` opens editor then launches Claude with existing task context
+- [ ] `raf plan --amend 001-my-project` works with full folder name identifier
+- [ ] `raf plan existing-project` (without `--amend`) shows clear error message
+- [ ] Claude receives context about existing tasks and their status
+- [ ] New tasks are numbered correctly (continuing from last task number)
+- [ ] Warning is displayed when amending a fully completed project
+- [ ] Amending creates new plan files without touching existing ones
+- [ ] Tests cover the amend workflow
+- [ ] Help text documents the `--amend` option
+
+## Notes
+- This task depends on task 001 for identifier resolution
+- Consider creating a separate prompt file in `src/prompts/` for the amend context
+- The editor content should clearly distinguish between existing task summary (read-only context) and the area for new task descriptions
+- Be careful not to accidentally modify or renumber existing plan files

package/RAF/005-task-naming-improvements/plans/005-commit-outcomes-on-complete.md

@@ -0,0 +1,86 @@
+# Task: Universal Commit Schema for RAF
+
+## Objective
+Implement a universal commit schema for all RAF-triggered commits (plan and outcome) with consistent formatting.
+
+## Context
+RAF needs a consistent commit message format across all automated commits. This provides clear identification of RAF-generated commits in git history and makes it easy to understand what type of commit it is (plan, task, or outcome).
+
+This task builds on the existing `raf do` command implementation and extends to `raf plan`.
+
+## Requirements
+
+### Commit Schema Format
+- **Plan commits**: `RAF[<project-number>:plan]`
+  - Example: `RAF[005:plan]`
+  - Triggered by: RAF programmatically after `raf plan` creates plan files
+- **Outcome commits**: `RAF[<project-number>:outcome]`
+  - Example: `RAF[005:outcome]`
+  - Triggered by: RAF programmatically when all tasks in a project complete via `raf do`
+- **Task commits**: `RAF[<project-number>:<task-number>] <project-name> <task-name>`
+  - Example: `RAF[005:001] task-naming-improvements enhance-identifier-resolution`
+  - Triggered by: Claude during task execution (handled in separate task 006)
+
+### Plan Commit Requirements
+- Trigger: After `raf plan` successfully creates all plan files
+- Scope: Commit the entire project folder (plans, decisions.md, input.md)
+- Handle dirty repo: Stage and commit only the project folder
+- Only commit on success - if planning fails, do not commit
+
+### Outcome Commit Requirements
+- Trigger: When final task in a project completes successfully via `raf do`
+- Scope: Commit the entire project folder (plans, outcomes, decisions, input.md, state.json, etc.)
+- Handle dirty repo: Stage and commit only the project folder
+- Only commit on success - if the final task fails, do not commit
+
+## Implementation Steps
+
+### Part A: Git Utility
+1. Create a git commit utility function in `src/utils/git.ts`:
+   - Accept project folder path, project number, and commit type (plan/outcome)
+   - Stage only files within the project folder: `git add <project-folder>`
+   - Create commit with appropriate format based on type
+   - Handle git errors gracefully (not a git repo, nothing to commit, etc.)
+
+### Part B: Plan Commits
+2. Read the current `plan.ts` command implementation in `src/commands/`
+3. After Claude successfully creates plan files, call the git utility with type "plan"
+4. Log success message: "Plan committed to git."
+
+### Part C: Outcome Commits
+5. Read the current `do.ts` command implementation in `src/commands/`
+6. Identify where task completion is detected (success/failure handling)
+7. Add a helper function to check if project is complete:
+   - Load project state
+   - Check if all tasks have status "completed"
+8. After a task completes successfully, check if this was the final task
+9. If project is now complete, call the git utility with type "outcome"
+10. Log success message: "Project complete. Committed to git."
+
+### Part D: Tests
+11. Add tests for:
+    - Plan commits after successful planning
+    - Outcome commits when final task completes
+    - Not committing when task/planning fails
+    - Handling non-git repos gracefully
+    - Handling when project folder has no changes
+
+## Acceptance Criteria
+- [ ] Git utility function supports both plan and outcome commit types
+- [ ] Plan commits use format `RAF[<project-number>:plan]`
+- [ ] Outcome commits use format `RAF[<project-number>:outcome]`
+- [ ] `raf plan` auto-commits project folder after successful planning
+- [ ] `raf do` auto-commits project folder when final task completes successfully
+- [ ] Only project folder is staged/committed, other repo changes are untouched
+- [ ] No commit is made if planning or final task fails
+- [ ] Graceful handling when not in a git repo (warning, no crash)
+- [ ] Graceful handling when there are no changes to commit
+- [ ] Tests cover both plan and outcome commit workflows
+- [ ] Success messages are logged after commits
+
+## Notes
+- Use `child_process.execSync` or similar for git commands
+- Extract git utilities to `src/utils/git.ts` for reusability
+- The project folder path can be derived from the project identifier resolution (task 001)
+- Be careful with error handling - git failures should not crash RAF commands
+- Task commits are handled separately in task 006 (Claude-triggered via execution prompt)

package/RAF/005-task-naming-improvements/plans/006-update-execution-prompt-commit-schema.md

@@ -0,0 +1,60 @@
+# Task: Update Execution Prompt for Universal Task Commit Schema
+
+## Objective
+Update the execution prompt to instruct Claude to use the universal commit schema format for task commits.
+
+## Context
+RAF uses a universal commit schema for all commits. While plan and outcome commits are handled programmatically by RAF (task 005), task commits are made by Claude during execution. The execution prompt needs to be updated to use the new format:
+
+`RAF[<project-number>:<task-number>] <project-name> <task-name>`
+
+Example: `RAF[005:001] task-naming-improvements enhance-identifier-resolution`
+
+This task depends on the commit schema defined in task 005.
+
+## Requirements
+- Update `src/prompts/execution.ts` to use the new commit message format
+- The execution prompt params must include:
+  - Project number (e.g., "005")
+  - Task number (e.g., "001")
+  - Project name (e.g., "task-naming-improvements")
+  - Task name (e.g., "enhance-identifier-resolution")
+- The commit message should follow format: `RAF[<project-number>:<task-number>] <project-name> <task-name>`
+- Update the `do.ts` command to pass the required parameters to the execution prompt
+
+## Implementation Steps
+1. Read the current execution prompt in `src/prompts/execution.ts`
+2. Update `ExecutionPromptParams` interface to include:
+   - `projectNumber: string` (e.g., "005")
+   - `taskName: string` (e.g., "enhance-identifier-resolution")
+   - Ensure `projectName` is required (not optional)
+3. Update the `commitInstructions` section in `getExecutionPrompt` to use format:
+   ```
+   Commit with message: "RAF[${projectNumber}:${taskNumber}] ${projectName} ${taskName}"
+   ```
+   Note: `taskNumber` should be zero-padded (e.g., "001")
+4. Read the `do.ts` command implementation
+5. Update the call to `getExecutionPrompt` to pass:
+   - `projectNumber` extracted from the project folder name (e.g., "005" from "005-task-naming-improvements")
+   - `taskName` extracted from the task file name (e.g., "enhance-identifier-resolution" from "001-enhance-identifier-resolution.md")
+6. Add or update tests for:
+   - Execution prompt generates correct commit format
+   - Parameters are correctly passed from do command
+
+## Acceptance Criteria
+- [ ] `ExecutionPromptParams` includes `projectNumber` and `taskName` fields
+- [ ] Execution prompt instructs Claude to use format `RAF[005:001] project-name task-name`
+- [ ] `do.ts` extracts and passes project number from folder name
+- [ ] `do.ts` extracts and passes task name from plan file name
+- [ ] Task number is zero-padded in commit message (001, 002, etc.)
+- [ ] Tests verify correct commit message format in prompt
+- [ ] All existing tests pass
+
+## Notes
+- The project number can be extracted from the project folder name (first 3 digits or base36 prefix)
+- The task name is the kebab-case portion after the task number in the plan filename
+- Example extraction: `005-task-naming-improvements/plans/001-enhance-identifier-resolution.md`
+  - Project number: `005`
+  - Task number: `001` (from `taskNumber` param, zero-padded)
+  - Project name: `task-naming-improvements`
+  - Task name: `enhance-identifier-resolution`

package/RAF/005-task-naming-improvements/plans/007-allow-pending-task-amendments.md

@@ -0,0 +1,60 @@
+# Task: Allow Amending PENDING Tasks in Amend Mode
+
+## Objective
+Update the amend prompt to allow modifying PENDING (not yet executed) tasks, while still protecting COMPLETED tasks from changes.
+
+## Context
+Currently, the amend prompt instructs Claude to "NEVER modify existing plan files." However, this is overly restrictive for PENDING tasks that haven't been executed yet. Users should be able to:
+- Modify PENDING tasks (they haven't been executed, so changes are safe)
+- NOT modify COMPLETED tasks (their outcomes depend on the original plan)
+
+This provides flexibility while protecting work that has already been done.
+
+## Requirements
+- Update `src/prompts/amend.ts` to differentiate between completed and non-completed tasks
+- NOT COMPLETED tasks (pending or failed): Can be modified
+- COMPLETED tasks: Cannot be modified (protected)
+- The amend prompt should clearly communicate these rules to Claude
+- The prompt should list which specific tasks are modifiable vs protected
+
+## Implementation Steps
+1. Read the current amend prompt in `src/prompts/amend.ts`
+2. Update the `AmendPromptParams` interface if needed to include task status
+3. Modify the existing tasks summary section to clearly indicate:
+   - Which tasks are PROTECTED (completed)
+   - Which tasks are MODIFIABLE (pending, failed)
+4. Update the "Important Rules" section to replace:
+   ```
+   NEVER modify existing plan files (001-XXX)
+   ```
+   With something like:
+   ```
+   NEVER modify COMPLETED task plans - they are protected
+   You MAY modify non-completed task plans (pending/failed) if the user requests changes
+   ```
+5. Add a new section listing modifiable vs protected tasks explicitly
+6. Add tests for:
+   - Prompt correctly identifies modifiable tasks
+   - Prompt correctly identifies protected tasks
+   - Different combinations of task statuses
+
+## Acceptance Criteria
+- [ ] Amend prompt allows modification of non-completed tasks (pending/failed)
+- [ ] Amend prompt prohibits modification of COMPLETED tasks
+- [ ] Prompt clearly lists which tasks are modifiable vs protected
+- [ ] Status indicators are clear: [PROTECTED], [MODIFIABLE]
+- [ ] Tests cover different task status combinations
+- [ ] All existing tests pass
+
+## Notes
+- The task status is already available in `existingTasks` parameter
+- Consider using clear visual indicators like [PROTECTED] and [MODIFIABLE] instead of just status
+- This change makes the amend mode more practical while still safeguarding completed work
+- Example output in prompt:
+  ```
+  Existing Tasks:
+  - Task 001: setup-database [COMPLETED] [PROTECTED]
+  - Task 002: add-user-auth [COMPLETED] [PROTECTED]
+  - Task 003: implement-api [PENDING] [MODIFIABLE]
+  - Task 004: write-tests [PENDING] [MODIFIABLE]
+  ```

package/RAF/005-task-naming-improvements/plans/008-fix-timeout-label.md

@@ -0,0 +1,31 @@
+# Task: Fix Timeout Label
+
+## Objective
+Change the startup message label from "Timeout" to "Task timeout" for clarity.
+
+## Context
+When `raf do` starts executing a project, it displays a summary message showing the number of tasks and the timeout value. The current label "Timeout" is ambiguous - changing it to "Task timeout" makes it clearer that this timeout applies per-task, not for the entire project.
+
+## Requirements
+- Change the label from "Timeout" to "Task timeout" in the `raf do` startup message
+- Keep the rest of the message format unchanged: `Tasks: X, Task timeout: Y minutes`
+
+## Implementation Steps
+1. Open `src/commands/do.ts`
+2. Find line 227 with the logger.info call
+3. Change `Timeout:` to `Task timeout:`
+
+## Acceptance Criteria
+- [ ] The message displays "Task timeout:" instead of "Timeout:"
+- [ ] The rest of the message format remains unchanged
+- [ ] All existing tests pass
+
+## Notes
+This is a simple label change in `src/commands/do.ts:227`:
+```typescript
+// Before:
+logger.info(`Tasks: ${state.tasks.length}, Timeout: ${timeout} minutes`);
+
+// After:
+logger.info(`Tasks: ${state.tasks.length}, Task timeout: ${timeout} minutes`);
+```