@devobsessed/code-captain 0.0.5 → 0.0.8

package/cursor/commands/create-spec.md

@@ -43,7 +43,7 @@ cc: create-spec "rough feature description"
 #### Step 1.3: Structured Clarification Loop
 **Rules:**
 - Ask ONE focused question at a time
-- After each answer, re-scan codebase for new context if relevant
+- After each answer, re-scan codebase for additional context if relevant
 - Continue until reaching 95% confidence on deliverable
 - Each question should target the highest-impact unknown
 - **Never declare "final question"** - let the conversation flow naturally
@@ -92,8 +92,8 @@ When confident, present a contract proposal with any concerns surfaced:
 **Success Criteria:** [How we'll know it's working correctly]
 
 **Scope Boundaries:** 
-- In Scope: [2-3 key features]
-- Out of Scope: [2-3 things we won't build]
+- Included: [2-3 key features]
+- Excluded: [2-3 things we won't build]
 
 **⚠️ Technical Concerns (if any):**
 - [Specific concern about feasibility, performance, or architecture]
@@ -133,14 +133,11 @@ Options:
 
 **Date Determination Process:**
 
-1. **CREATE** directory if not exists: `.code-captain/specs/`
-2. **CREATE** temporary file: `.code-captain/specs/.date-check`
-3. **READ** file creation timestamp from filesystem
-4. **EXTRACT** date in YYYY-MM-DD format
-5. **DELETE** temporary file
-6. **STORE** date in variable for folder naming
+1. Read the current UTC date from the system clock and format as `YYYY-MM-DD`.
+2. Store it for naming:  
+   `.code-captain/specs/[DATE]-[feature-name]/`
 
-**Fallback Method:** If file system method fails:
+**Fallback Method:** If system clock access isn't available:
 1. **STATE**: "I need to confirm today's date for the specification folder"
 2. **ASK**: "What is today's date? (YYYY-MM-DD format)"
 3. **WAIT** for user response
@@ -414,8 +411,8 @@ Agent: [Continues with more informed questions about the hybrid architecture...]
 **Success Criteria:** Messages appear instantly, spam is prevented via crypto payments, blockchain verification happens within 5 minutes
 
 **Scope Boundaries:**
-- In Scope: Real-time chat, wallet integration, background blockchain settlement
-- Out of Scope: Advanced chat features (file sharing, voice), custom token creation
+- Included: Real-time chat, wallet integration, background blockchain settlement
+- Excluded: Advanced chat features (file sharing, voice), custom token creation
 
 ---
 Options: [yes/edit/risks/blueprint]

package/cursor/commands/explain-code.md

@@ -143,18 +143,15 @@ All explanations are automatically saved to `.code-captain/explanations/` using
 
 ## Date Determination Process
 
-### Primary Method: File System Timestamp
+### Primary Method: System Clock
 
-1. **CREATE** directory if not exists: `.code-captain/explanations/`
-2. **CREATE** temporary file: `.code-captain/explanations/.date-check`
-3. **READ** file creation timestamp from filesystem
-4. **EXTRACT** date in YYYY-MM-DD format
-5. **DELETE** temporary file
-6. **STORE** date in variable for file naming
+1. Read the current UTC date from the system clock and format as `YYYY-MM-DD`.
+2. Store it for naming:  
+   `.code-captain/explanations/[DATE]-[target-name].md`
 
 ### Fallback Method: User Confirmation
 
-If file system method fails:
+If system clock access isn't available:
 
 1. **STATE**: "I need to confirm today's date for the explanation file"
 2. **ASK**: "What is today's date? (YYYY-MM-DD format)"

package/cursor/commands/initialize.md

@@ -1,6 +1,6 @@
 # Initialize Command Workflow
 
-## Command: `cc: initialize`
+## Overview
 
 ### Purpose
 

package/cursor/commands/new-command.md

@@ -248,10 +248,11 @@ ls .code-captain/commands/ | grep "^command-name.md$"
    - TDD patterns
    - Verification steps
 
-4. **Integration** (`sync`, `create-github-issues`)
-   - Platform API interactions
-   - Sync and conflict handling
-   - Status reporting
+4. **Quality** (`status`, `swab`)
+5. **Meta** (`new-command`, `explain-code`)
+   - Command scaffolding and template generation
+   - Documentation updates across the ecosystem
+   - Validation and consistency checks
 
 ### Documentation Update Locations
 

package/cursor/commands/research.md

@@ -1,6 +1,6 @@
 # Research Command
 
-## Purpose
+## Overview
 
 Conduct systematic research on a topic using structured phases that build upon each other, creating actionable todos and leveraging web search capabilities.
 
@@ -122,18 +122,15 @@ Conduct systematic research on a topic using structured phases that build upon e
 
 ## Date Determination Process
 
-### Primary Method: File System Timestamp
+### Primary Method: System Clock
 
-1. **CREATE** directory if not exists: `.code-captain/research/`
-2. **CREATE** temporary file: `.code-captain/research/.date-check`
-3. **READ** file creation timestamp from filesystem
-4. **EXTRACT** date in YYYY-MM-DD format
-5. **DELETE** temporary file
-6. **STORE** date in variable for folder naming
+1. Read the current UTC date from the system clock and format as `YYYY-MM-DD`.
+2. Store it for naming:  
+   `.code-captain/research/[DATE]-[topic-name]-research.md`
 
 ### Fallback Method: User Confirmation
 
-If file system method fails:
+If system clock access isn't available:
 
 1. **STATE**: "I need to confirm today's date for the research folder"
 2. **ASK**: "What is today's date? (YYYY-MM-DD format)"

package/cursor/commands/status.md

@@ -54,7 +54,7 @@ Simple, no parameters needed. Works in any git repository with optional Code Cap
 **Based on Current State:**
 - If mid-task: Suggest `cc: execute-task`
 - If no active work: Suggest `cc: create-spec`
-- If specifications exist: Suggest `cc: create-github-issues`
+- If specifications exist: Suggest implementation with `cc: execute-task`
 - Always suggest `cc: swab` for code cleanup
 
 ## Output Format
@@ -410,4 +410,15 @@ $ cc: status
 
 ---
 
-*⚓ Keep your bearings, maintain your heading, and always know where you stand in the code.*
+*⚓ Keep your bearings, maintain your heading, and always know where you stand in the code.*
+
+## Suggested Next Actions
+
+Based on project state analysis, suggest relevant next steps:
+
+- **No specs**: Suggest `cc: create-spec` or `cc: plan-product`
+- **Specs ready for implementation**: Suggest `cc: execute-task`
+- **Tasks ready**: Suggest `cc: execute-task`
+- **Code quality issues**: Suggest `cc: swab`
+- **Missing architecture**: Suggest `cc: create-adr`
+- **Research needed**: Suggest `cc: research`

package/cursor/commands/swab.md

@@ -14,6 +14,17 @@ cc: swab
 
 ## Command Process
 
+### Step 0: Initialize Progress Tracking
+
+**Create todos for the swab process using `todo_write`:**
+
+```
+- Scan codebase for improvement opportunities [in_progress]
+- Prioritize and select best cleanup option [pending]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
+
 ### Step 1: Codebase Scanning
 
 **Scan for improvement opportunities:**
@@ -34,6 +45,8 @@ cc: swab
 
 ### Step 2: Opportunity Prioritization
 
+**Update progress:** Mark "Scan codebase for improvement opportunities" as `[completed]` and "Prioritize and select best cleanup option" as `[in_progress]`
+
 **Selection Criteria:**
 1. **Clarity Impact** - How much clearer will the code be?
 2. **Risk Level** - How certain are we this won't break anything?
@@ -49,6 +62,8 @@ cc: swab
 
 ### Step 3: Present Single Best Option
 
+**Update progress:** Mark "Prioritize and select best cleanup option" as `[completed]` and "Present cleanup suggestion to user" as `[in_progress]`
+
 **Display Format:**
 ```
 🧽 Swabbing the deck... found some mess in {filename}
@@ -66,12 +81,16 @@ Clean this up? [y/N]
 
 ### Step 4: Apply Change
 
+**Update progress:** Mark "Present cleanup suggestion to user" as `[completed]` and "Apply approved change" as `[in_progress]`
+
 **If approved:**
-- Make the exact replacement using search/replace
+- Make the exact replacement using search and replace
 - Verify the change was applied correctly
+- Mark "Apply approved change" as `[completed]`
 - Show success message: "✅ Deck swabbed! One less mess aboard."
 
 **If declined:**
+- Mark "Apply approved change" as `[completed]` (no change needed)
 - Exit gracefully with: "🧽 Deck inspection complete. No changes made."
 
 ## Core Rules
@@ -95,7 +114,7 @@ RULES:
 - Prioritize clarity and safety over cleverness
 - Preserve all existing functionality exactly
 - Be extremely conservative - if ANY uncertainty, do nothing
-- Provide exact search/replace strings
+- Provide exact search and replace strings
 - Focus on high-impact, zero-risk improvements
 
 SCAN PRIORITIES:
@@ -187,6 +206,44 @@ This might happen if the file was modified since scanning.
 Try running the command again.
 ```
 
+## Example Todo Progression
+
+**Initial:**
+
+```
+- Scan codebase for improvement opportunities [in_progress]
+- Prioritize and select best cleanup option [pending]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
+
+**After scanning:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [in_progress]
+- Present cleanup suggestion to user [pending]
+- Apply approved change [pending]
+```
+
+**After prioritization:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [completed]
+- Present cleanup suggestion to user [in_progress]
+- Apply approved change [pending]
+```
+
+**Final:**
+
+```
+- Scan codebase for improvement opportunities [completed]
+- Prioritize and select best cleanup option [completed]
+- Present cleanup suggestion to user [completed]
+- Apply approved change [completed]
+```
+
 ## Integration Notes
 
 This command integrates with the existing Code Captain ecosystem by:
@@ -195,6 +252,8 @@ This command integrates with the existing Code Captain ecosystem by:
 2. **Leveraging existing tools** - Uses `codebase_search`, `read_file`, `search_replace`
 3. **Maintaining simplicity** - No complex configuration or state management
 4. **Respecting user control** - Always asks permission before making changes
+5. **Progress tracking** - Uses `todo_write` for visibility into command progress
+6. **Quality foundation** - Complements specification and implementation commands by maintaining code quality, supporting the overall project foundation alongside `.code-captain` documentation
 
 ## Future Enhancements