@devobsessed/code-captain 0.0.6 → 0.0.9

package/copilot/prompts/status.prompt.md

@@ -51,7 +51,7 @@ Provide developers with a comprehensive status report when starting work or swit
 **Based on Current State:**
 - If mid-task: Suggest `/execute-task`
 - If no active work: Suggest `/create-spec`
-- If specifications exist: Suggest `/create-github-issues`
+- If specifications exist: Suggest implementation with `/execute-task`
 - Always suggest `/swab` for code cleanup
 
 ## Output Format
@@ -421,4 +421,15 @@ $ /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 `/create-spec` or `/plan-product`
+- **Specs ready for implementation**: Suggest `/execute-task`
+- **Tasks ready**: Suggest `/execute-task`
+- **Code quality issues**: Suggest `/swab`
+- **Missing architecture**: Suggest `/create-adr`
+- **Research needed**: Suggest `/research`

package/copilot/prompts/swab.prompt.md

@@ -203,6 +203,7 @@ This command integrates with the existing Code Captain ecosystem by:
 2. **Leveraging existing tools** - Uses GitHub Copilot's native capabilities
 3. **Maintaining simplicity** - No complex configuration or state management
 4. **Respecting user control** - Always asks permission before making changes
+5. **Quality foundation** - Complements specification and implementation commands by maintaining code quality, supporting the overall project foundation alongside `.code-captain` documentation
 
 ## Future Enhancements
 

package/cursor/README.md

@@ -13,87 +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)
 
-### 🔗 Platform Integration
-- **`cc: create-github-issues [spec-path]`** - Create GitHub issues from specifications
-- **`cc: sync [--full|--my-work-only|--spec]`** - Advanced bidirectional GitHub sync
-- **`cc: sync-github-issues`** - Basic GitHub issue synchronization
-- **`cc: create-azure-work-items [spec-path]`** - Create Azure DevOps work items
-- **`cc: sync-azure-work-items [options]`** - Azure DevOps synchronization
+- **`/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
-
-# 5. Project management integration
-cc: create-github-issues
-cc: sync --spec realtime-chat
+/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
@@ -102,109 +97,103 @@ 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"
+```
 
-# Generate project management artifacts
-cc: create-github-issues .code-captain/specs/2024-12-28-user-profile/
+```bash
+# Implementation workflow
+/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"
+/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"
-}
-```
-
-### Project Management Platform
-Choose during installation or configure manually:
-- **GitHub Issues & Projects**
-- **Azure DevOps Work Items**
-
 ## 📊 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 |
-| `create-github-issues` | GitHub integration | Updates spec with issue numbers |
-| `sync` | Advanced GitHub sync | `.code-captain/state/github/` |
+| 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
 
-### GitHub Integration Issues
-**Problem**: GitHub commands fail  
-**Solution**: Verify repository has GitHub remote and check network connectivity
+### Task Generation Issues
+
+**Problem**: Task generation produces incomplete results  
+**Solution**: Ensure specifications are detailed and requirements are clear
 
 ## 🤝 Contributing
 
@@ -220,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,22 +1,19 @@
----
-description:
-globs:
-alwaysApply: true
----
+# 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."
@@ -27,43 +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
-- `generate-tasks` - LLM-powered task generation from specs  
-- `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 GitHub Workflow
-
-- `generate-tasks` / `create-github-issues` - Spec to GitHub issues workflow
-- `sync` - Advanced bidirectional GitHub sync with partitioned cache
-- `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
-├── state/          # GitHub sync cache (created when needed)
-└── 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
@@ -204,7 +198,7 @@ Use `todo_write` to track the ADR creation process:
 3. **Use `codebase_search` to understand current implementation approaches**
 
 4. **Identify and document alternative options:**
-   - Current state/status quo option
+   - Current state or status quo option
    - Industry standard approaches
    - Innovative or emerging alternatives
    - Hybrid approaches combining multiple patterns
@@ -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]