docs(dev): normalize report and task filename examples

.claude-plugin/skills/agent-cli-dev/SKILL.md

@@ -147,9 +147,9 @@ Key rules for same-worktree launches:
 - Use `dev agent -a <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
 - Use `-m tmux` for headless or scripted launching; it works even when not already inside tmux
 - Each launch joins the same deterministic repo-scoped tmux session, so related agents stay grouped together
-- Ask each agent to write to a unique report path such as `.claude/REPORT-security-<run-id>.md` or `.claude/REPORT-tests-<run-id>.md`
+- Ask each agent to write to a unique report path such as `.claude/REPORT-security-20260319-153045-123.md` or `.claude/REPORT-tests-20260319-153045-123.md`
 - If you rerun the same prompt repeatedly, include a timestamp or other run id in the report filename so later runs do not overwrite earlier ones
-- Each agent launch gets its own unique task file in `.claude/` (e.g., `TASK-{timestamp}-{hex}.md`), so parallel launches do not overwrite each other
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not overwrite each other
 
 ### Prompt guidance for shared worktrees
 

.claude-plugin/skills/agent-cli-dev/examples.md

@@ -547,7 +547,7 @@ Do not fix code. Review only.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-security-$run_id.md:
+Write findings to .claude/REPORT-security-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -560,7 +560,7 @@ Review only. Focus on query patterns, repeated work, and unnecessary allocations
 </scope>
 
 <report>
-Write findings to .claude/REPORT-performance-$run_id.md:
+Write findings to .claude/REPORT-performance-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -573,7 +573,7 @@ Review only. Identify missing or weak tests.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-tests-$run_id.md:
+Write findings to .claude/REPORT-tests-20260319-153045-123.md:
 - Summary
 - Missing test cases
 - Suggested follow-up tests
@@ -585,7 +585,7 @@ Write findings to .claude/REPORT-tests-$run_id.md:
 - If you rerun the same prompt often, include a timestamp or run id in the filename so reports do not get replaced
 - `-m tmux` works even when the caller is not already inside tmux
 - All three agents land in the same deterministic tmux session for that repo
-- Each agent launch gets its own unique task file in `.claude/`, so parallel launches do not conflict
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not conflict
 
 ## Scenario 7: Parallel test validation
 

.claude/skills/agent-cli-dev/SKILL.md

@@ -147,9 +147,9 @@ Key rules for same-worktree launches:
 - Use `dev agent -a <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
 - Use `-m tmux` for headless or scripted launching; it works even when not already inside tmux
 - Each launch joins the same deterministic repo-scoped tmux session, so related agents stay grouped together
-- Ask each agent to write to a unique report path such as `.claude/REPORT-security-<run-id>.md` or `.claude/REPORT-tests-<run-id>.md`
+- Ask each agent to write to a unique report path such as `.claude/REPORT-security-20260319-153045-123.md` or `.claude/REPORT-tests-20260319-153045-123.md`
 - If you rerun the same prompt repeatedly, include a timestamp or other run id in the report filename so later runs do not overwrite earlier ones
-- Each agent launch gets its own unique task file in `.claude/` (e.g., `TASK-{timestamp}-{hex}.md`), so parallel launches do not overwrite each other
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not overwrite each other
 
 ### Prompt guidance for shared worktrees
 

.claude/skills/agent-cli-dev/examples.md

@@ -547,7 +547,7 @@ Do not fix code. Review only.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-security-$run_id.md:
+Write findings to .claude/REPORT-security-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -560,7 +560,7 @@ Review only. Focus on query patterns, repeated work, and unnecessary allocations
 </scope>
 
 <report>
-Write findings to .claude/REPORT-performance-$run_id.md:
+Write findings to .claude/REPORT-performance-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -573,7 +573,7 @@ Review only. Identify missing or weak tests.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-tests-$run_id.md:
+Write findings to .claude/REPORT-tests-20260319-153045-123.md:
 - Summary
 - Missing test cases
 - Suggested follow-up tests
@@ -585,7 +585,7 @@ Write findings to .claude/REPORT-tests-$run_id.md:
 - If you rerun the same prompt often, include a timestamp or run id in the filename so reports do not get replaced
 - `-m tmux` works even when the caller is not already inside tmux
 - All three agents land in the same deterministic tmux session for that repo
-- Each agent launch gets its own unique task file in `.claude/`, so parallel launches do not conflict
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not conflict
 
 ## Scenario 7: Parallel test validation
 

agent_cli/dev/skill/SKILL.md

@@ -147,9 +147,9 @@ Key rules for same-worktree launches:
 - Use `dev agent -a <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
 - Use `-m tmux` for headless or scripted launching; it works even when not already inside tmux
 - Each launch joins the same deterministic repo-scoped tmux session, so related agents stay grouped together
-- Ask each agent to write to a unique report path such as `.claude/REPORT-security-<run-id>.md` or `.claude/REPORT-tests-<run-id>.md`
+- Ask each agent to write to a unique report path such as `.claude/REPORT-security-20260319-153045-123.md` or `.claude/REPORT-tests-20260319-153045-123.md`
 - If you rerun the same prompt repeatedly, include a timestamp or other run id in the report filename so later runs do not overwrite earlier ones
-- Each agent launch gets its own unique task file in `.claude/` (e.g., `TASK-{timestamp}-{hex}.md`), so parallel launches do not overwrite each other
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not overwrite each other
 
 ### Prompt guidance for shared worktrees
 

agent_cli/dev/skill/examples.md

@@ -547,7 +547,7 @@ Do not fix code. Review only.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-security-$run_id.md:
+Write findings to .claude/REPORT-security-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -560,7 +560,7 @@ Review only. Focus on query patterns, repeated work, and unnecessary allocations
 </scope>
 
 <report>
-Write findings to .claude/REPORT-performance-$run_id.md:
+Write findings to .claude/REPORT-performance-20260319-153045-123.md:
 - Summary
 - Issues with file:line references
 - Suggested fixes
@@ -573,7 +573,7 @@ Review only. Identify missing or weak tests.
 </scope>
 
 <report>
-Write findings to .claude/REPORT-tests-$run_id.md:
+Write findings to .claude/REPORT-tests-20260319-153045-123.md:
 - Summary
 - Missing test cases
 - Suggested follow-up tests
@@ -585,7 +585,7 @@ Write findings to .claude/REPORT-tests-$run_id.md:
 - If you rerun the same prompt often, include a timestamp or run id in the filename so reports do not get replaced
 - `-m tmux` works even when the caller is not already inside tmux
 - All three agents land in the same deterministic tmux session for that repo
-- Each agent launch gets its own unique task file in `.claude/`, so parallel launches do not conflict
+- Each agent launch gets its own unique task file in `.claude/` (for example `.claude/TASK-1773934245-abcd.md`), so parallel launches do not conflict
 
 ## Scenario 7: Parallel test validation
 

docs/commands/dev.md

@@ -776,7 +776,7 @@ for section in 1 2 3 4; do
 done
 ```
 
-If multiple agents share one worktree, do not have them all write to `.claude/REPORT.md` because they will overwrite each other. Instead, assign unique report paths such as `.claude/REPORT-security-<run-id>.md` and `.claude/REPORT-tests-<run-id>.md`. If you rerun the same prompt repeatedly, use a timestamp or other run id so later runs do not replace earlier results. Each agent launch also gets its own `.claude/TASK-{timestamp}-{hex}.md` file, so prompt files no longer overwrite each other.
+If multiple agents share one worktree, do not have them all write to `.claude/REPORT.md` because they will overwrite each other. Instead, assign unique report paths such as `.claude/REPORT-security-20260319-153045-123.md` and `.claude/REPORT-tests-20260319-153045-123.md`. If you rerun the same prompt repeatedly, use a timestamp or other run id so later runs do not replace earlier results. Each agent launch also gets its own `.claude/TASK-1773934245-abcd.md` file, so prompt files no longer overwrite each other.
 
 ## Shell Integration