Merge pull request #231 from TimeWarpEngineering/Cramer/2025-06-24/Task_025

Task 025: File Naming Convention Analysis and Standardization

Author: StevenTCramer

CLAUDE.md

@@ -1,4 +1,4 @@
-# CLAUDE.md
+# Claude.md
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 

TimeWarp.Architecture/CLAUDE.md TimeWarp.Architecture/Claude.mdTimeWarp.Architecture/CLAUDE.md renamed to TimeWarp.Architecture/Claude.md

@@ -1,4 +1,4 @@
-# CLAUDE.md
+# Claude.md
 
 This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
 
@@ -122,6 +122,19 @@ This project uses a **hybrid approach** combining Kanban folders for internal de
 - `Kanban/InProgress/` - Currently being worked on
 - `Kanban/Done/` - Completed tasks
 
+### Task Organization Convention
+- **Simple tasks**: Single markdown file (e.g., `001_Fix-Bug.md`)
+- **Complex tasks with deliverables**: Use folder structure:
+  ```
+  025_Create-Analysis-Report/
+  ├── Task.md           # Task specification and notes
+  ├── Report.md         # Generated deliverable
+  └── Additional.md     # Other outputs as needed
+  ```
+- **Folder naming**: Same `###_Task-Name` pattern as single files
+- **Task file naming**: Use `Task.md` within folder (path provides context)
+- **Deliverable naming**: Descriptive names for outputs
+
 ### GitHub Issues (External Interface)
 - **Community contributions**: Bug reports, feature requests from users
 - **AI agent integration**: Create issues and mention AI agents (e.g., @claude) for automated work
@@ -134,6 +147,21 @@ This project uses a **hybrid approach** combining Kanban folders for internal de
 3. **AI automation**: Comment on GitHub Issues with "@claude please work on this" to trigger AI agents
 4. **Branch naming**: Task numbers integrate with branch naming convention: `Author/YYYY-MM-DD/Task_###`
 
+### Branch Naming Convention (ADR-0004)
+**Format**: `Author/YYYY-MM-DD/Task_###`
+
+**Examples**:
+- `Cramer/2025-06-18/Task_019`
+- `Cramer/2025-06-23/Task_023`
+- `Cramer/2025-06-24/Task_025`
+
+**Elements**:
+- **Author**: Developer's name/identifier (e.g., "Cramer")
+- **Date**: Branch creation date in YYYY-MM-DD format
+- **Task**: Task number from Kanban system (###)
+
+**Usage**: Always create feature branches using this convention when starting work on Kanban tasks. This provides clear ownership, temporal context, and traceability to the task management system.
+
 ### Definition of Done (API Endpoints)
 **Implementation:**
 - Server: *Endpoint (required), Server-side Validator, Mapper, *Handler (required)

TimeWarp.Architecture/Documentation/Developer/Conceptual/ArchitecturalDecisionRecords/Approved/0006-kanban-development-process.md

@@ -117,6 +117,19 @@ Kanban/
 * **Active tasks**: `001_`, `002_`, etc. (remove B prefix when ready)
 * **Sequential numbering**: Ensures unique identification and chronological order
 
+### Task Organization Convention
+* **Simple tasks**: Single markdown file (e.g., `001_Fix-Bug.md`)
+* **Complex tasks with deliverables**: Folder structure for organization
+  ```
+  025_Create-File-Naming-Convention-Analysis-Report/
+  ├── Task.md                           # Task specification and notes
+  ├── Analysis-Report.md                # Generated deliverable
+  └── Additional-Files.md               # Other outputs as needed
+  ```
+* **Folder naming**: Use same `###_Task-Name` pattern as single files
+* **Task file naming**: Use `Task.md` within folder (path provides context, eliminates redundancy)
+* **Deliverable naming**: Descriptive names for outputs (reports, documentation, etc.)
+
 ### Integration with Development Workflow
 * **Branch naming**: Task numbers align with branch naming (e.g., `Author/Date/Task_019`)
 * **Commit references**: Commits can reference task numbers for traceability

TimeWarp.Architecture/Documentation/Developer/Conceptual/DirectoryStructure.md

@@ -29,7 +29,7 @@
 * [Directory.Build.props](https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build?view=vs-2019#directorybuildprops-and-directorybuildtargets) Set the versions of the packages used across the solution here.
 * [global.json](https://docs.microsoft.com/en-us/dotnet/core/tools/global-json?tabs=netcore3x)- (optional) specify required SDK
 * [Nuget.config](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file) - specify NuGet sources
-* README.md
+* ReadMe.md
 * Run.ps1 - (optional) PowerShell script to Run the application
 * TestCafe.ps1 - Script to execute the TestCafe tests
 * UNLICENSE.md

TimeWarp.Architecture/Kanban/Done/023_Create-Architectural-Decision-Records.md

@@ -48,7 +48,7 @@ Create formal Architectural Decision Records (ADRs) to document key development
 - ✅ Used consistent terminology (master vs main branch)
 - ✅ Created proper branch and followed Kanban workflow
 - ✅ Committed changes following proper process
-- ✅ Updated CLAUDE.md to reference new ADRs
+- ✅ Updated Claude.md to reference new ADRs
 
 ## Related Tasks
 
@@ -65,5 +65,5 @@ Create formal Architectural Decision Records (ADRs) to document key development
 2. ✅ Moved task to InProgress 
 3. ✅ Committed ADR files on branch
 4. ✅ Enhanced ADRs based on feedback and comprehensive analysis
-5. ✅ Updated CLAUDE.md to reference new ADRs
+5. ✅ Updated Claude.md to reference new ADRs
 6. ✅ Ready for pull request creation and task completion

TimeWarp.Architecture/Kanban/Done/024_Migrate-To-Hybrid-Task-Management.md

@@ -53,7 +53,7 @@ Implement the hybrid Kanban + GitHub Issues approach documented in ADR-0006 by r
 ### Template Clean-up
 
 - Remove Process folder references from documentation
-- Update CLAUDE.md to reflect hybrid approach
+- Update Claude.md to reflect hybrid approach
 - Ensure new template instances only include Kanban
 
 ## Related Work