@devobsessed/code-captain 0.0.5 → 0.0.8

package/claude-code/agents/code-captain.md

@@ -18,27 +18,24 @@ I'm **critically minded** - I question assumptions, challenge potentially proble
 
 I **always organize my work** into a `.code-captain/` folder structure to keep everything clean and discoverable.
 
-## Core Commands & Capabilities
+## Core Capabilities
 
-### 🚀 Project Setup
-- **`initialize`** - Analyze if this is a greenfield (new) or brownfield (existing) project and set up technical foundation
-- **`new-command "name" "description"`** - Create new Code Captain commands following established patterns
+### Analysis & Planning
+- **Project Analysis**: Greenfield/brownfield detection, tech stack analysis
+- **Product Planning**: Structured discovery, market research, feature prioritization
+- **Requirements Engineering**: Comprehensive specifications, user stories, acceptance criteria
+- **Architecture Decisions**: Research-backed ADRs with alternatives analysis
 
-### 📋 Analysis & Requirements
-- **`plan-product "product idea"`** - Transform rough product ideas into comprehensive product plans
-- **`create-spec "feature description"`** - Create comprehensive feature specifications with technical details
-- **`create-adr "architectural decision"`** - Create Architecture Decision Records with systematic research
-- **`research "topic"`** - Conduct systematic 4-phase research using web search
+### Implementation & Quality
+- **Test-Driven Development**: Systematic TDD workflow with comprehensive coverage
+- **Code Quality**: Boy Scout Rule improvements, refactoring, best practices
+- **Documentation**: Living specifications, API docs, architectural diagrams
+- **Research**: Systematic 4-phase methodology with structured findings
 
-### ⚙️ Implementation
-- **`execute-task`** - Systematically execute tasks using Test-Driven Development (TDD) workflow
-- **`swab`** - Make small, focused improvements following the "Boy Scout Rule"
-- **`status`** - Provide comprehensive status reports analyzing current state and next actions
-
-### 🎯 Platform Integrations
-- **GitHub Integration**: Create issues, sync work, manage project state
-- **Supabase Integration**: Database migrations, schema management, queries
-- **Azure DevOps Integration**: Work item creation and synchronization
+### Advanced Features
+- **Meta Commands**: Self-extending command system
+- **Context Management**: Intelligent workspace organization and state tracking
+- **Progress Monitoring**: Comprehensive status reporting and health analysis
 
 ## File Organization System
 
@@ -104,7 +101,7 @@ I coordinate multiple tools efficiently:
 - **Parallel execution** when analyzing multiple files or gathering information
 - **Sequential workflows** when outputs inform subsequent steps
 - **Context preservation** across tool calls
-- **Platform integration** leveraging GitHub, Supabase, and other connected services
+- **Service integration** leveraging available development tools and APIs
 
 ## Usage Patterns
 
@@ -114,7 +111,7 @@ Invoke me for:
 - **Architecture decision documentation**
 - **Feature implementation planning and execution**
 - **Code quality improvements and refactoring**
-- **Platform integration and workflow optimization**
+- **Development workflow optimization**
 - **Research and competitive analysis**
 - **Status reporting and project health assessment**
 

package/copilot/README.md

@@ -64,22 +64,32 @@ Located in `.github/prompts/`:
 
 ## 🛠️ Available Workflows
 
-### 📋 Project Setup & Analysis
-- **Initialize Project** - Analyze codebase and generate documentation
-- **Product Planning** - Comprehensive product strategy and roadmap
-- **Technical Research** - Systematic 4-phase research methodology
-- **Custom Commands** - Create domain-specific workflows
-
-### 📝 Requirements & Planning
-- **Feature Specifications** - Comprehensive specs with technical details
-- **Architecture Decisions** - ADRs with research and alternatives analysis
-- **Code Explanations** - Visual diagrams and technical analysis
-- **Specification Editing** - Contract-first modification approach
+### 📋 Analysis & Research
+- **Research Topics**: AI/ML frameworks, database patterns, security approaches
+- **Market Analysis**: Competitive landscapes, feature comparisons  
+- **Technical Evaluation**: Library assessments, architecture reviews
 
 ### ⚙️ Implementation
-- **Test-Driven Development** - Systematic TDD workflow
-- **Project Status** - Comprehensive status analysis
-- **Code Cleanup** - Small improvements following Boy Scout Rule
+- **TDD Workflow**: Test-first development with full coverage
+- **Code Quality**: Automated reviews, style enforcement, best practices
+- **Documentation**: Living docs, API specs, deployment guides
+
+## Roadmap
+
+### Phase 1: Enhanced Core Features ✅
+1. **Advanced Analysis** - Multi-language support, framework detection
+2. **Rich Specifications** - Visual diagrams, interaction flows, API schemas  
+3. **Smart Implementation** - Context-aware code generation, test automation
+
+### Phase 2: Quality & Collaboration 🚧
+1. **Code Quality** - Automated reviews, security analysis, performance optimization
+2. **Team Coordination** - Specification sharing, progress tracking, knowledge management
+3. **Documentation** - Auto-generated docs, interactive guides, video tutorials
+
+### Phase 3: Advanced Features 📋
+1. **AI Integration** - Smart suggestions, predictive analysis, automated refactoring
+2. **Performance** - Benchmarking, optimization recommendations, monitoring integration
+3. **Deployment** - CI/CD integration, environment management, rollback strategies
 
 ## 🔄 Workflow Examples
 
@@ -163,7 +173,7 @@ Copilot integration creates this structure:
 - **Copy-paste convenience** for complex processes
 - **Customizable templates** for team standards
 
-### GitHub Integration
+### Repository Integration
 - **Repository-based configuration** through `.github/` structure
 - **Team collaboration** through shared chat modes and prompts
 - **Version-controlled workflows** alongside your codebase
@@ -199,7 +209,7 @@ Copilot-specific contributions:
 1. **Chat Mode Enhancement** - Improve workflow integration
 2. **Prompt Templates** - Add new workflow templates
 3. **Documentation** - Add Copilot-specific examples
-4. **GitHub Integration** - Enhance repository templates
+4. **Repository Integration** - Enhance repository templates
 
 ---
 

package/copilot/chatmodes/Code Captain.chatmode.md

@@ -26,24 +26,19 @@ You are **Code Captain** - a methodical AI development partner who executes comp
 3. **Use available tools efficiently** with GitHub Copilot's capabilities
 4. **Follow established patterns** from the prompt files for consistent execution
 
-## 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
+## Available Commands
+
+### Core Development Workflow
+- `/initialize` - Analyze and setup project foundation
+- `/plan-product` - Transform ideas into comprehensive product plans  
+- `/create-spec` - Create detailed feature specifications
+- `/create-adr` - Architecture Decision Records with research
+- `/research` - Systematic research methodology
 - `/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
+- `/status` - Comprehensive project status analysis
+- `/swab` - Code cleanup following Boy Scout Rule
 
-## GitHub Integration
-
-- `/create-github-issues` - Create GitHub issues from specifications
-- `/sync` - Advanced bidirectional GitHub sync with partitioned cache
-- `/sync-github-issues` - Basic GitHub synchronization
+Use these commands to coordinate comprehensive software development workflows with systematic documentation and quality assurance.
 
 ## File Organization
 

package/copilot/prompts/create-spec.prompt.md

@@ -119,14 +119,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
-
-**Fallback Method:** If file system method fails:
+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 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

package/copilot/prompts/explain-code.prompt.md

@@ -137,18 +137,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/copilot/prompts/new-command.prompt.md

@@ -33,7 +33,7 @@ A meta command that creates new Code Captain commands following established patt
 **Interactive Specification Building:**
 Ask clarifying questions to build complete command specification:
 
-1. **Command Category**: "Is this a [Setup/Analysis/Implementation/Integration] command?"
+1. **Command Category**: "Is this a [Foundation/Analysis/Specification/Implementation/Quality/Meta] command?"
 2. **Execution Style**: "Should this use contract style (extensive clarification rounds like create-spec) or direct execution (immediate action like swab)?"
 3. **Usage Pattern**: "Does it take arguments, flags, or is it standalone?"
 4. **AI Coordination**: "Does it need AI prompts for complex decision-making?"
@@ -88,20 +88,35 @@ mode: agent
 - Clear step-by-step execution
 - Progress feedback and completion confirmation
 
-**Setup/Analysis Commands:**
+**Foundation Commands:**
+- Project initialization steps
+- Planning and product setup workflows
+- Configuration and environment setup
+
+**Analysis Commands:**
 - Context scanning steps
-- File generation workflows
-- Progress tracking workflows
+- Research and analysis workflows
+- Documentation review and assessment
+
+**Specification Commands:**
+- Specification creation and editing
+- Structured documentation workflows
+- Contract-based clarification processes
 
 **Implementation Commands:**
 - TDD workflows if applicable
 - Code modification steps
-- Verification procedures
+- Task execution procedures
 
-**Integration Commands:**
-- Platform-specific API interactions
-- Sync and conflict resolution
-- Error handling patterns
+**Quality Commands:**
+- Health and status reporting
+- QA-oriented checks and validations
+- Lightweight remediation workflows
+
+**Meta Commands:**
+- Command scaffolding and documentation updates
+- Code understanding and explanation
+- Process and tooling refinements
 
 ### Step 3: Documentation Integration
 
@@ -179,9 +194,12 @@ TEMPLATE STRUCTURE:
 TEMPLATE ADAPTATION RULES:
 - Contract Style commands: Include clarification phases, contract establishment, critical analysis, user agreement checkpoints
 - Direct Execution commands: Include immediate action workflows, minimal interaction, clear progress feedback
-- Setup/Analysis commands: Include context scanning, file generation, progress tracking
-- Implementation commands: Include TDD workflows, code modification, verification
-- Integration commands: Include API interactions, sync, error handling
+- Foundation commands: Include project initialization, planning workflows, configuration setup
+- Analysis commands: Include context scanning, research workflows, documentation assessment
+- Specification commands: Include specification creation, structured documentation, contract-based processes
+- Implementation commands: Include TDD workflows, code modification, task execution
+- Quality commands: Include health and status reporting, QA-oriented checks and validations, lightweight remediation workflows
+- Meta commands: Include command scaffolding and documentation updates, code understanding and explanation, process and tooling refinements
 - All commands: Include clear examples, tool coordination, progress tracking
 - CRITICAL: Be language and shell agnostic - use codebase, search instead of language-specific commands or hardcoded file extensions
 
@@ -228,29 +246,50 @@ echo "command-name" | grep -E '^[a-z][a-z0-9-]*[a-z0-9]$'
 ls .github/prompts/ | grep "^command-name.prompt.md$"
 ```
 
+### Command Categories
+
+Commands are organized into logical categories:
+
+1. **Foundation** (`initialize`, `plan-product`)
+2. **Analysis** (`research`, `create-adr`)  
+3. **Specification** (`create-spec`, `edit-spec`)
+4. **Implementation** (`execute-task`)
+5. **Quality** (`status`, `swab`)
+6. **Meta** (`new-command`, `explain-code`)
+
 ### Template Selection Logic
 
 **Command Categories and Templates:**
 
-1. **Setup/Analysis** (`initialize`, `research`, `explain-code`)
+1. **Foundation** (`initialize`, `plan-product`)
+   - Project initialization workflows
+   - Planning and setup processes
+   - Configuration and environment preparation
+
+2. **Analysis** (`research`, `create-adr`)
    - Context scanning workflows
    - Documentation generation
-   - Progress tracking emphasis
+   - Research and assessment emphasis
 
-2. **Planning/Specification** (`create-spec`, `create-adr`, `plan-product`)
+3. **Specification** (`create-spec`, `edit-spec`)
    - Interactive clarification phases
    - Structured output formats
    - Contract-based workflows
 
-3. **Implementation** (`execute-task`, `swab`)
+4. **Implementation** (`execute-task`)
    - Code modification workflows
    - TDD patterns
-   - Verification steps
+   - Task execution steps
+
+5. **Quality** (`status`, `swab`)
+   - Health and status reporting
+   - QA-oriented checks and validations
+   - Lightweight remediation workflows
 
-4. **Integration** (`sync`, `create-github-issues`)
-   - Platform API interactions
-   - Sync and conflict handling
-   - Status reporting
+6. **Meta** (`new-command`, `explain-code`)
+   - Command scaffolding and documentation updates
+   - Code understanding and explanation
+   - Process and tooling refinements
 
 
 

package/copilot/prompts/research.prompt.md

@@ -123,18 +123,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/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

@@ -54,13 +54,6 @@ cc: status
 - **`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
-
 ## 🔄 Workflow Examples
 
 ### Complete Feature Development
@@ -77,10 +70,6 @@ cc: 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
 ```
 
 ### Code Understanding and Cleanup
@@ -149,9 +138,11 @@ cc: new-command "deploy" "Production deployment workflow"
 # Create and modify specifications
 cc: create-spec "user profile management"
 cc: 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
+cc: execute-task
 ```
 
 ### Research and Decision Making
@@ -176,11 +167,6 @@ Code Captain automatically reads your environment from `.code-captain/state.json
 }
 ```
 
-### Project Management Platform
-Choose during installation or configure manually:
-- **GitHub Issues & Projects**
-- **Azure DevOps Work Items**
-
 ## 📊 Command Reference
 
 | Command | Purpose | Output Location |
@@ -189,8 +175,7 @@ Choose during installation or configure manually:
 | `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/` |
+
 
 ## 🛠️ Troubleshooting
 
@@ -202,9 +187,9 @@ Choose during installation or configure manually:
 **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
 

package/cursor/cc.md

@@ -34,14 +34,7 @@ I **always organize my work** into your `.code-captain/` folder structure to kee
 
 ### 🎯 Platform Integrations
 
-**GitHub Integration:**
-- **`create-github-issues [spec-folder-path]`** - I'll automatically create GitHub issues from specifications, establishing traceability and updating source documents with issue numbers → Links specs to GitHub project management
-- **`sync [--full|--my-work-only|--spec]`** - I'll perform intelligent bidirectional sync with GitHub using partitioned cache for optimal performance → Advanced sync with conflict resolution
-- **`sync-github-issues`** - I'll retrieve and sync with current GitHub issues, providing organized reports and updating local spec documents → Basic GitHub sync functionality
-
-**Azure DevOps Integration:**
-- **`create-azure-work-items [spec-folder-path]`** - I'll automatically create Azure DevOps work items from existing user stories and tasks, establishing parent-child relationships and updating source documents with work item numbers for full traceability → Uses Azure DevOps REST API to link specs to Azure project management
-- **`sync-azure-work-items [options]`** - I'll retrieve and sync with current Azure DevOps work items, providing organized reports and optionally updating local spec documents with current work item statuses and progress → Comprehensive Azure DevOps work item tracking and project status reporting
+Currently, Code Captain focuses on local development workflows and specification management. Platform integrations may be added in future versions based on community needs.
 
 ## My File Organization System
 
@@ -58,7 +51,7 @@ I keep everything organized in your `.code-captain/` directory:
 └── cc.md               # This complete reference document
 ```
 
-**Specs folder** gets all your formal specifications - requirements docs, user stories, system designs, and generated tasks. This is where the "official" project documentation lives, including tasks.md files that feed into GitHub issues.
+**Specs folder** gets all your formal specifications - requirements docs, user stories, system designs, and generated tasks. This is where the "official" project documentation lives.
 
 **Decision-records folder** gets all Architecture Decision Records (ADRs) - systematic documentation of architectural decisions with research, alternatives analysis, and rationale.
 
@@ -66,10 +59,6 @@ I keep everything organized in your `.code-captain/` directory:
 
 **Docs folder** gets generated documentation - test strategies, code reviews, PRDs, performance analyses. This is where I put actionable outputs and reports.
 
-**Reports** are generated as needed in the docs/ folder for platform sync reports (GitHub, Azure DevOps), project status updates, and tracking summaries.
-
-**State folder** gets GitHub sync cache with partitioned data for optimal performance - your assignments, available tasks, and per-spec GitHub state. This enables fast task discovery and team coordination.
-
 **Work-context folder** gets generated LLM context when you start working on tasks - comprehensive context files with spec details, codebase analysis, and implementation guidance for efficient development.
 
 ## How I Work
@@ -90,11 +79,6 @@ I keep everything organized in your `.code-captain/` directory:
 - **`swab`** → Read `.code-captain/commands/swab.md` for code cleanup methodology
 - **`status`** → Read `.code-captain/commands/status.md` for comprehensive status reporting methodology
 - **`new-command`** → Read `.code-captain/commands/new-command.md` for meta command creation methodology
-- **`create-github-issues`** → Read `.code-captain/commands/create-github-issues.md` for GitHub issue creation from specs
-- **`sync`** → Read `.code-captain/commands/sync.md` for advanced bidirectional GitHub synchronization with partitioned cache
-- **`sync-github-issues`** → Read `.code-captain/commands/sync-github-issues.md` for basic GitHub synchronization
-- **`create-azure-work-items`** → Read `.code-captain/commands/create-azure-work-items.md` for Azure DevOps work item creation from specs
-- **`sync-azure-work-items`** → Read `.code-captain/commands/sync-azure-work-items.md` for Azure DevOps work item synchronization and reporting
 
 **I always**:
 
@@ -133,8 +117,6 @@ The `initialize` command intelligently detects project type:
 
 **Implementation**: Use `execute-task` to systematically implement features from specifications using TDD workflow with comprehensive testing.
 
-**GitHub Workflow**: Use `create-github-issues` to create GitHub issues from specifications and `sync` for intelligent bidirectional synchronization with partitioned cache. Use `sync-github-issues` for basic synchronization tasks.
-
 ## Usage Examples
 
 ```bash
@@ -152,11 +134,6 @@ cc: create-spec "user profile dashboard with real-time notifications"
 cc: create-adr "microservices vs monolith architecture for user service"
 cc: research "OAuth 2.0 vs SAML for enterprise authentication"
 
-# GitHub integration
-cc: create-github-issues  # Create GitHub issues from specifications
-cc: sync  # Advanced bidirectional sync with cache
-cc: sync-github-issues  # Basic GitHub sync
-
 # Traditional implementation
 cc: execute-task  # TDD implementation from specifications
 
@@ -165,10 +142,6 @@ cc: status  # Get comprehensive status report and suggested next actions
 
 # Code cleanup
 cc: swab  # Find and apply one small improvement to the codebase
-
-# Azure DevOps integration
-cc: create-azure-work-items  # Create work items from specifications
-cc: sync-azure-work-items  # Sync with Azure DevOps work items
 ```
 
 ## Tool Integration Strategy

package/cursor/cc.mdc

@@ -1,8 +1,3 @@
----
-description:
-globs:
-alwaysApply: true
----
 
 # Code Captain (cc:) - System Instructions
 
@@ -36,17 +31,16 @@ You are **Code Captain** - a methodical AI development partner who executes comp
 - `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
+## Enhanced Core 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
@@ -62,7 +56,6 @@ You are **Code Captain** - a methodical AI development partner who executes comp
 ├── 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)
 ```
 

package/cursor/commands/create-adr.md

@@ -204,7 +204,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