@devobsessed/code-captain 0.0.8 → 0.0.9

package/copilot/prompts/research.prompt.md

@@ -30,6 +30,7 @@ Conduct systematic research on a topic using structured phases that build upon e
 4. Plan research phases and approach
 
 **Research Structure:**
+
 - Phase 1: Define scope and questions [in_progress]
 - Phase 2: Initial discovery [pending]
 - Phase 3: Deep dive analysis [pending]
@@ -87,7 +88,7 @@ Conduct systematic research on a topic using structured phases that build upon e
 2. Create recommendations based on research
 3. Identify next steps or areas requiring further investigation
 4. Document sources and evidence for claims
-5. Determine current date using robust file system method (see Date Determination Process below)
+5. Get current date using: `npx @devobsessed/code-captain date`
 6. Create research document in `.code-captain/research/` folder using the standardized format below
 7. Present findings in appropriate format (summary document, recommendations)
 
@@ -121,37 +122,18 @@ Conduct systematic research on a topic using structured phases that build upon e
 - **Further Research:** [What questions remain]
 - **Decision Points:** [Key choices that need to be made]
 
-## Date Determination Process
-
-### Primary Method: System Clock
-
-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 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)"
-3. **WAIT** for user response
-4. **VALIDATE** format matches `^\d{4}-\d{2}-\d{2}$`
-   - year: 2024-2030
-   - month: 01-12
-   - day: 01-31
-5. **STORE** date for folder naming
+## Date Determination
 
-### Error Handling
+Get current date by running: `npx @devobsessed/code-captain date`
 
-- **IF** date_invalid: USE fallback_method
-- **IF** both_methods_fail: ERROR "Unable to determine current date"
+This returns the current date in `YYYY-MM-DD` format for folder naming:
+`.code-captain/research/[DATE]-[topic-name]-research.md`
 
 ## Research Document Template
 
-**First, determine the current date using the process above.**
+**First, get the current date using: `npx @devobsessed/code-captain date`**
 
-Create a markdown file in `.code-captain/research/[DATE]-[topic-name]-research.md` where `[DATE]` is determined using the robust date process.
+Create a markdown file in `.code-captain/research/[DATE]-[topic-name]-research.md`.
 
 **Example:** `.code-captain/research/2024-01-15-blockchain-supply-chain-research.md`
 
@@ -250,6 +232,7 @@ Use the following structure:
 ## Tool Integration
 
 **Primary tools:**
+
 - `fetch` - Web research and external information gathering
 - `search` - Finding existing research and related documentation
 - `editFiles` - Creating research documents and reports
@@ -257,6 +240,7 @@ Use the following structure:
 - `codebase` - Understanding project context and existing knowledge
 
 **Documentation organization:**
+
 - Research documents stored in `.code-captain/research/`
 - Date-prefixed filenames for chronological organization
 - Cross-references to related project documentation
@@ -297,6 +281,7 @@ Use the following structure:
 ## Example Research Progression
 
 **Initial Phase:**
+
 ```
 - Research blockchain solutions for supply chain [in_progress]
 - Analyze implementation approaches [pending]
@@ -306,6 +291,7 @@ Use the following structure:
 ```
 
 **After Phase 2:**
+
 ```
 - Research blockchain solutions for supply chain [completed]
 - Analyze implementation approaches [in_progress]
@@ -316,6 +302,7 @@ Use the following structure:
 ```
 
 **Final:**
+
 ```
 - Research blockchain solutions for supply chain [completed]
 - Analyze implementation approaches [completed]
@@ -323,4 +310,4 @@ Use the following structure:
 - Determine date using file system method [completed]
 - Create research document in .code-captain/research/ [completed]
 - Create recommendation report [completed]
-```
+```

package/cursor/README.md

@@ -13,76 +13,82 @@ npx @devobsessed/code-captain
 ```
 
 The installer will auto-detect Cursor and install to:
+
 - `.cursor/rules/cc.mdc` - Command recognition and auto-completion
 - `.code-captain/` - Complete workflow system
 
 ### Manual Installation
 
 ```bash
-# Clone or download the cursor/ directory contents
+# Install Cursor rules and commands
 cp cursor/cc.mdc .cursor/rules/
-cp -r cursor/ .code-captain/
+cp cursor/commands/*.md .cursor/commands/
 ```
 
 ## 🎯 Command Syntax
 
-Code Captain commands in Cursor use the `cc:` prefix:
+Code Captain commands in Cursor use the `/` slash prefix:
 
 ```bash
-cc: initialize
-cc: create-spec "user authentication system"
-cc: execute-task
-cc: status
+/initialize
+/create-spec "user authentication system"
+/execute-task
+/status
 ```
 
 ## 🛠️ Available Commands
 
 ### 📋 Project Setup & Analysis
-- **`cc: initialize`** - Analyze project and generate foundational documentation
-- **`cc: plan-product "product idea"`** - Comprehensive product planning with vision and roadmap
-- **`cc: research "topic"`** - Systematic 4-phase technical research
-- **`cc: new-command "name" "description"`** - Create custom Code Captain commands
+
+- **`/initialize`** - Analyze project and generate foundational documentation
+- **`/plan-product "product idea"`** - Comprehensive product planning with vision and roadmap
+- **`/research "topic"`** - Systematic 4-phase technical research
+- **`/new-command "name" "description"`** - Create custom Code Captain commands
 
 ### 📝 Requirements & Planning
-- **`cc: create-spec "feature description"`** - Generate comprehensive feature specifications
-- **`cc: edit-spec [spec-identifier] "changes"`** - Modify existing specifications with impact analysis
-- **`cc: create-adr "architectural decision"`** - Create Architecture Decision Records (auto-research)
-- **`cc: explain-code [target]`** - Generate code explanations with visual diagrams
+
+- **`/create-spec "feature description"`** - Generate comprehensive feature specifications
+- **`/edit-spec [spec-identifier] "changes"`** - Modify existing specifications with impact analysis
+- **`/create-adr "architectural decision"`** - Create Architecture Decision Records (auto-research)
+- **`/explain-code [target]`** - Generate code explanations with visual diagrams
 
 ### ⚙️ Implementation
-- **`cc: execute-task`** - Test-driven development workflow with progress tracking
-- **`cc: status`** - Comprehensive project status and next action recommendations
-- **`cc: swab`** - Apply one small improvement (Boy Scout Rule)
+
+- **`/execute-task`** - Test-driven development workflow with progress tracking
+- **`/status`** - Comprehensive project status and next action recommendations
+- **`/swab`** - Apply one small improvement (Boy Scout Rule)
 
 ## 🔄 Workflow Examples
 
 ### Complete Feature Development
+
 ```bash
 # 1. Project setup and analysis
-cc: initialize
+/initialize
 
 # 2. Research and planning
-cc: research "WebSocket vs Server-Sent Events for real-time features"
-cc: create-adr "real-time communication architecture"
+/research "WebSocket vs Server-Sent Events for real-time features"
+/create-adr "real-time communication architecture"
 
 # 3. Feature specification
-cc: create-spec "real-time chat with message history"
+/create-spec "real-time chat with message history"
 
 # 4. Implementation
-cc: execute-task
+/execute-task
 ```
 
 ### Code Understanding and Cleanup
+
 ```bash
 # Understand existing code
-cc: explain-code AuthenticationService
-cc: explain-code "src/components/UserDashboard.tsx:45-120"
+/explain-code AuthenticationService
+/explain-code "src/components/UserDashboard.tsx:45-120"
 
 # Make incremental improvements
-cc: swab
+/swab
 
 # Check project health
-cc: status
+/status
 ```
 
 ## 📁 File Organization
@@ -91,103 +97,101 @@ Cursor integration creates this structure:
 
 ```
 .cursor/
+├── commands/              # Native Cursor command files
+│   ├── initialize.md
+│   ├── create-spec.md
+│   ├── execute-task.md
+│   └── ...
 └── rules/
-    └── cc.mdc              # Command recognition file
+    └── cc.mdc              # Code Captain identity & behavior rules
 
 .code-captain/
-├── commands/               # All available commands
 ├── docs/                   # Generated documentation
 ├── research/               # Technical research reports
 ├── decision-records/       # Architecture Decision Records
-├── specs/                  # Feature specifications
-│   └── YYYY-MM-DD-feature/
-│       ├── spec.md
-│       ├── user-stories/
-│       └── tasks.md
-└── cc.md                  # Complete reference guide
+└── specs/                  # Feature specifications
+    └── YYYY-MM-DD-feature/
+        ├── spec.md
+        ├── user-stories/
+        └── tasks.md
 ```
 
 ## 🎯 Cursor-Specific Features
 
 ### Native Command Recognition
+
 - Commands auto-complete in the chat interface
 - Syntax highlighting for Code Captain commands
 - Contextual command suggestions
 
 ### Seamless Tool Integration
+
 - Leverages Cursor's native `codebase_search`, `file_search`, `edit_file`
 - Automatic progress tracking with `todo_write`
 - Parallel tool execution for maximum efficiency
 
 ### Smart Context Awareness
-- Reads `.code-captain/state.json` for platform and shell detection
-- Adapts commands and file paths for your specific environment
+
+- Native Cursor integration with automatic environment detection
+- Adapts commands and file paths for your specific platform
 - Maintains context across command executions
 
 ## 🚀 Advanced Usage
 
 ### Custom Command Creation
+
 ```bash
 # Create domain-specific commands
-cc: new-command "audit" "Security and code quality auditing"
-cc: new-command "deploy" "Production deployment workflow"
+/new-command "audit" "Security and code quality auditing"
+/new-command "deploy" "Production deployment workflow"
 ```
 
 ### Specification Management
+
 ```bash
 # Create and modify specifications
-cc: create-spec "user profile management"
-cc: edit-spec "user-profile-management" "add avatar upload functionality"
+/create-spec "user profile management"
+/edit-spec "user-profile-management" "add avatar upload functionality"
 ```
 
 ```bash
 # Implementation workflow
-cc: execute-task
+/execute-task
 ```
 
 ### Research and Decision Making
+
 ```bash
 # Systematic research
-cc: research "React state management: Redux vs Zustand vs Context"
+/research "React state management: Redux vs Zustand vs Context"
 
 # Document architectural decisions
-cc: create-adr "state management library selection"
-```
-
-## 🔧 Configuration
-
-### Environment Setup
-Code Captain automatically reads your environment from `.code-captain/state.json`:
-
-```json
-{
-  "platform": "darwin",
-  "shell": "/bin/zsh",
-  "ide": "cursor"
-}
+/create-adr "state management library selection"
 ```
 
 ## 📊 Command Reference
 
-| Command | Purpose | Output Location |
-|---------|---------|-----------------|
-| `initialize` | Project analysis & setup | `.code-captain/docs/` |
-| `plan-product` | Product planning | `.code-captain/product/` |
-| `create-spec` | Feature specification | `.code-captain/specs/YYYY-MM-DD-feature/` |
-| `execute-task` | TDD implementation | Source code + tests |
-
+| Command        | Purpose                  | Output Location                           |
+| -------------- | ------------------------ | ----------------------------------------- |
+| `initialize`   | Project analysis & setup | `.code-captain/docs/`                     |
+| `plan-product` | Product planning         | `.code-captain/product/`                  |
+| `create-spec`  | Feature specification    | `.code-captain/specs/YYYY-MM-DD-feature/` |
+| `execute-task` | TDD implementation       | Source code + tests                       |
 
 ## 🛠️ Troubleshooting
 
 ### Command Not Recognized
-**Problem**: Cursor doesn't recognize `cc:` commands  
-**Solution**: Ensure `.cursor/rules/cc.mdc` exists and restart Cursor
+
+**Problem**: Cursor doesn't recognize `/` commands  
+**Solution**: Ensure `.cursor/commands/` and `.cursor/rules/cc.mdc` exist and restart Cursor
 
 ### Commands Execute But No Output
+
 **Problem**: Commands run but don't generate expected files  
 **Solution**: Check `.code-captain/` folder permissions and verify command completion
 
 ### Task Generation Issues
+
 **Problem**: Task generation produces incomplete results  
 **Solution**: Ensure specifications are detailed and requirements are clear
 
@@ -205,5 +209,5 @@ Cursor-specific contributions:
 **Ready to supercharge your Cursor development?**
 
 1. **Install:** `npx @devobsessed/code-captain`
-2. **Start:** `cc: initialize`
-3. **Explore:** `cc: status` for next steps 
+2. **Start:** `/initialize`
+3. **Explore:** `/status` for next steps

package/cursor/cc.mdc

@@ -1,17 +1,19 @@
+# Code Captain - System Instructions
 
-# Code Captain (cc:) - System Instructions
+## Identity & Approach
 
-**CRITICAL: Before responding to ANY cc: command, FIRST read `.code-captain/cc.md` for complete instructions and methodology.**
+You are **Code Captain** - a methodical AI development partner who executes comprehensive software workflows. You organize all work in `.code-captain/` folders and use `todo_write` for progress tracking.
 
-## Identity
+**Personality:**
 
-You are **Code Captain** - a methodical AI development partner who executes comprehensive software workflows. You organize all work in `.code-captain/` folders and use `todo_write` for progress tracking.
+- **Methodical but efficient** - Break complex tasks into clear, manageable steps while leveraging parallel execution
+- **Detail-oriented** - Provide context, rationale, and comprehensive documentation, not just code
+- **Critically minded** - Question assumptions, challenge potentially problematic requests, provide evidence-based pushback when needed
+- **Adaptable** - Adjust standards based on whether you need a quick prototype or production-ready code
 
 ## Command Execution Protocol
 
-1. **ALWAYS read `.code-captain/cc.md` FIRST** - Contains your complete methodology, personality, and detailed command instructions
-2. **ALWAYS read `.code-captain/state.json` FIRST** - Contains user's platform and shell for environment-specific commands and instructions
-3. **Display welcome message**: Randomly select one of these greetings:
+1. **Display welcome message**: Randomly select one of these greetings:
    - "⚓ All aboard! Code Captain ready to steer your development ship."
    - "🧭 Ahoy! Your Code Captain is charting the course to quality code."
    - "⛵ Welcome aboard! Code Captain at your service, ready to navigate your codebase."
@@ -22,41 +24,17 @@ You are **Code Captain** - a methodical AI development partner who executes comp
    - "🚢 Steady as she goes! Code Captain prepared to steer your project to success."
    - "⚓ Anchors aweigh! Code Captain ready to lead your development expedition."
    - "🧭 All hands on deck! Code Captain here to guide your coding voyage."
-4. **For complex commands, read command-specific documentation** (paths in cc.md)
-5. **Use parallel tool execution** when possible for efficiency
-
-## Core Commands
-
-- `initialize` - Project technical foundation setup and analysis (recommends plan-product for product strategy)
-- `new-command "name" "description"` - Meta command to create new Code Captain commands
-- `plan-product "idea"` - Product strategy and vision through structured discovery
-- `create-spec "feature"` - Feature specifications with implementation roadmaps
-  
-- `create-adr "decision"` - Architecture Decision Records (auto-executes research)
-- `research "topic"` - 4-phase systematic research
-- `execute-task` - TDD implementation from specifications
-- `status` - Comprehensive status report with git state, active work, and suggested actions
-- `swab` - Code cleanup: one small improvement following Boy Scout Rule
-
-## Enhanced Core Workflow
-
-  
-- `next-task` / `start-work` / `claim-task` - Intelligent task management
-- `my-tasks` / `available-tasks` / `team-status` - Work coordination
-- `complete-task` / `resolve-conflicts` - Task completion and conflict resolution
+2. **Use parallel tool execution** when possible for efficiency
+3. **Follow critical thinking guidelines** in `.code-captain/docs/best-practices.md` - disagree constructively rather than automatically agreeing
 
 ## File Organization
 
 ```
 .code-captain/
-├── cc.md           # Complete reference (READ THIS FIRST)
-├── state.json      # User platform and shell environment (READ THIS FIRST)
-├── commands/       # All command documentation (core + platform-specific)
 ├── specs/          # Requirements, specifications, and tasks
 ├── research/       # Technical research and analysis
 ├── decision-records/ # Architecture Decision Records
-├── docs/           # Generated documentation
-└── work-context/   # Generated LLM context for active tasks (created when needed)
+└── docs/           # Generated documentation, best practices
 ```
 
-**Remember: All details, examples, workflows, and personality are in `.code-captain/cc.md` - read it before executing any commands.**
+**Core Principle:** Always organize work into the `.code-captain/` folder structure to keep everything clean and discoverable. Focus on what's right for the project over being agreeable.

package/cursor/commands/create-adr.md

@@ -1,15 +1,9 @@
-# Create ADR Command (cc: create-adr)
+# Create ADR Command (create-adr)
 
 ## Overview
 
 Create comprehensive Architecture Decision Records (ADRs) that systematically document architectural decisions with clear rationale, alternatives considered, and consequences through a structured analysis and review process.
 
-## Usage
-
-```bash
-cc: create-adr "architectural decision description"
-```
-
 ## When to Use
 
 - Making significant architectural decisions that affect system structure or design
@@ -233,10 +227,10 @@ For each alternative, evaluate against established criteria:
 
 **Preparation Actions:**
 
-1. **Get current date:**
+1. **Get current date for document content:**
 
    ```bash
-   date +%Y-%m-%d
+   npx @devobsessed/code-captain date
    ```
 
 2. **Determine ADR number:**
@@ -245,8 +239,8 @@ For each alternative, evaluate against established criteria:
    - Use sequential numbering (0001, 0002, etc.)
 
 3. **Create ADR directory structure:**
-   
-   Create the decision records directory (Code Captain will use platform-appropriate commands based on your shell from `state.json`):
+
+   Create the decision records directory:
 
 **ADR Creation:**
 
@@ -257,7 +251,7 @@ Create markdown file: `.code-captain/decision-records/NNNN-decision-title.md`
 ```markdown
 # NNNN. [Decision Title]
 
-**Date:** [Use output from date +%Y-%m-%d command]
+**Date:** [Use output from npx @devobsessed/code-captain date]
 
 **Status:** [Proposed/Accepted/Deprecated/Superseded]