@devobsessed/code-captain 0.0.3

package/copilot/README.md

@@ -0,0 +1,210 @@
+# Code Captain for GitHub Copilot + VS Code
+
+> **Classic VS Code with AI-powered chat modes and prompts**
+
+Transform GitHub Copilot Chat into a structured development workflow system with custom chat modes, prompts, and organized documentation.
+
+## 🚀 Installation
+
+### Automatic Installation (Recommended)
+
+```bash
+npx @devobsessed/code-captain
+```
+
+The installer will detect VS Code with Copilot and install to:
+- `.github/chatmodes/` - Code Captain chat mode
+- `.github/prompts/` - Workflow prompt templates
+- `.code-captain/` - Complete workflow system
+
+### Manual Installation
+
+```bash
+# Clone or download the copilot/ directory contents to .github/
+cp -r copilot/chatmodes/ .github/chatmodes/
+cp -r copilot/prompts/ .github/prompts/
+cp -r .code-captain/ .
+```
+
+## 🎯 Command Syntax
+
+Code Captain integrates with Copilot Chat through a custom chat mode. After installation:
+
+1. **Select Code Captain chat mode** from the chat mode dropdown
+2. **Use slash commands** directly:
+
+```bash
+/initialize
+/create-spec "user authentication system"
+/execute-task
+/status
+```
+
+## 📁 Chat Modes & Prompts
+
+### Chat Mode
+Located in `.github/chatmodes/`:
+
+- **Code Captain.chatmode.md** - Automatically available in chat mode selector
+
+### Available Prompts
+Located in `.github/prompts/`:
+
+- **`create-spec.prompt.md`** - Feature specification creation
+- **`create-adr.prompt.md`** - Architecture Decision Records
+- **`execute-task.prompt.md`** - Test-driven development workflow
+- **`initialize.prompt.md`** - Project setup and analysis
+- **`plan-product.prompt.md`** - Product planning and strategy
+- **`research.prompt.md`** - Systematic technical research
+- **`explain-code.prompt.md`** - Code explanation with diagrams
+- **`status.prompt.md`** - Project status analysis
+- **`swab.prompt.md`** - Code cleanup methodology
+- **`edit-spec.prompt.md`** - Specification modification
+- **`new-command.prompt.md`** - Custom command creation
+
+## 🛠️ 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
+
+### ⚙️ Implementation
+- **Test-Driven Development** - Systematic TDD workflow
+- **Project Status** - Comprehensive status analysis
+- **Code Cleanup** - Small improvements following Boy Scout Rule
+
+## 🔄 Workflow Examples
+
+### Using the Chat Mode
+
+1. **Open Copilot Chat** in VS Code
+2. **Select "Code Captain"** from the chat mode dropdown
+3. **Type:** `/initialize`
+4. **Follow the prompts** for project analysis
+5. **Review generated files** in `.code-captain/docs/`
+
+### Using Prompts Directly
+
+1. **Open a prompt file** (e.g., `.github/prompts/create-spec.prompt.md`)
+2. **Copy the prompt** content
+3. **Paste in Copilot Chat** (any mode)
+4. **Provide your feature description**
+
+### Complete Feature Development
+
+```bash
+# Select "Code Captain" chat mode, then:
+
+# 1. Project setup
+/initialize
+
+# 2. Research phase
+/research "React state management options"
+
+# 3. Document decision
+/create-adr "React state management library selection"
+
+# 4. Create specification
+/create-spec "user dashboard with real-time notifications"
+
+# 5. Implementation
+/execute-task
+
+# 6. Status check
+/status
+```
+
+## 📁 File Organization
+
+Copilot integration creates this structure:
+
+```
+.github/
+├── chatmodes/
+│   └── Code Captain.chatmode.md
+└── prompts/
+    ├── create-spec.prompt.md
+    ├── create-adr.prompt.md
+    ├── execute-task.prompt.md
+    ├── initialize.prompt.md
+    ├── plan-product.prompt.md
+    ├── research.prompt.md
+    ├── explain-code.prompt.md
+    ├── status.prompt.md
+    ├── swab.prompt.md
+    ├── edit-spec.prompt.md
+    └── new-command.prompt.md
+
+.code-captain/
+├── docs/                  # Generated documentation
+├── research/              # Technical research reports
+├── decision-records/      # Architecture Decision Records
+├── specs/                 # Feature specifications
+└── cc.md                 # Complete reference guide
+```
+
+## 🎯 Copilot-Specific Features
+
+### Custom Chat Modes
+- **Structured workflows** through chat mode activation
+- **Context-aware responses** based on project state
+- **Guided interactions** with step-by-step processes
+
+### Prompt Templates
+- **Reusable workflows** for consistent outputs
+- **Copy-paste convenience** for complex processes
+- **Customizable templates** for team standards
+
+### GitHub Integration
+- **Repository-based configuration** through `.github/` structure
+- **Team collaboration** through shared chat modes and prompts
+- **Version-controlled workflows** alongside your codebase
+
+
+## 📊 Command Reference
+
+| Slash Command | Purpose | Output Location |
+|---------------|---------|-----------------|
+| `/initialize` | Project analysis | `.code-captain/docs/` |
+| `/create-spec` | Feature specification | `.code-captain/specs/` |
+| `/status` | Project status | Terminal output |
+| `/research` | Technical research | `.code-captain/research/` |
+
+## 🛠️ Troubleshooting
+
+### Chat Mode Not Available
+**Problem**: Code Captain doesn't appear in chat mode selector  
+**Solution**: Ensure `.github/chatmodes/Code Captain.chatmode.md` exists and restart VS Code
+
+### Prompts Don't Work as Expected
+**Problem**: Prompts generate inconsistent results  
+**Solution**: Copy the exact prompt text and include all context sections
+
+### File Generation Issues
+**Problem**: Files aren't created in expected locations  
+**Solution**: Check `.code-captain/` folder exists and has write permissions
+
+## 🤝 Contributing
+
+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
+
+---
+
+**Ready to enhance your Copilot workflow?**
+
+1. **Install:** `npx @devobsessed/code-captain`
+2. **Open:** Copilot Chat in VS Code
+3. **Start:** Select "Code Captain" mode and type `/initialize` 

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

@@ -0,0 +1,60 @@
+---
+description: '⚓ Awaiting orders...'
+tools: ['changes', 'codebase', 'editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages']
+---
+
+# Code Captain - System Instructions
+
+## Identity
+
+You are **Code Captain** - a methodical AI development partner who executes comprehensive software workflows. You organize all work in `.code-captain/` folders and use file-based progress tracking.
+
+## Command Execution Protocol
+
+1. **Check user environment**: Read `.code-captain/state.json` for platform and shell configuration
+2. **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."
+   - "🚢 Greetings! Your Code Captain is here to guide you through smooth sailing."
+   - "⚓ Code Captain reporting for duty! Let's set sail toward exceptional software."
+   - "🧭 Ready to embark? Code Captain is here to navigate your development journey."
+   - "⛵ Permission to come aboard? Code Captain ready to chart your coding adventure."
+   - "🚢 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."
+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
+- `/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
+
+## GitHub Integration
+
+- `/create-github-issues` - Create GitHub issues from specifications
+- `/sync` - Advanced bidirectional GitHub sync with partitioned cache
+- `/sync-github-issues` - Basic GitHub synchronization
+
+## File Organization
+
+```
+.code-captain/
+├── state.json      # User platform and shell configuration
+├── docs/           # Generated documentation
+├── research/       # Technical research and analysis
+├── decision-records/ # Architecture Decision Records
+├── explanations/   # Code explanations with diagrams
+└── specs/          # Requirements, specifications, and tasks
+```
+
+**Note: Command details and workflows are defined in individual prompt files in `.github/prompts/`**

package/copilot/docs/best-practices.md

@@ -0,0 +1,74 @@
+# Development Best Practices
+
+## Context
+
+Global development guidelines for Agent OS projects.
+
+## Core Principles
+
+### Keep It Simple
+
+- Implement code in the fewest lines possible
+- Avoid over-engineering solutions
+- Choose straightforward approaches over clever ones
+
+### Optimize for Readability
+
+- Prioritize code clarity over micro-optimizations
+- Write self-documenting code with clear variable names
+- Add comments for "why" not "what"
+
+### DRY (Don't Repeat Yourself)
+
+- Extract repeated business logic to private methods
+- Extract repeated UI markup to reusable components
+- Create utility functions for common operations
+
+### File Structure
+
+- Keep files focused on a single responsibility
+- Group related functionality together
+- Use consistent naming conventions
+
+## Critical Thinking and Decision Making
+
+### Challenge Ideas and Assumptions
+
+- Question the "why" behind every technical decision
+- Identify unstated assumptions in requirements and designs
+- Ask "What could go wrong?" for proposed solutions
+- Consider edge cases and failure scenarios
+
+### Provide Constructive Pushback
+
+- Disagree when you have evidence-based concerns
+- Offer alternative approaches with clear reasoning
+- Challenge overly complex solutions in favor of simpler ones
+- Point out potential security, performance, or maintainability issues
+
+### Focus on Evidence Over Agreement
+
+- Base decisions on data, benchmarks, and measurable outcomes
+- Cite specific examples when discussing trade-offs
+- Reference industry standards and established patterns
+- Avoid "yes, and..." responses when "no, because..." is more appropriate
+
+### Question Popular Choices
+
+- Don't assume popularity equals correctness
+- Evaluate if trendy technologies actually solve the problem
+- Consider long-term maintenance costs of new frameworks
+- Assess if existing solutions already meet the need
+
+## Dependencies
+
+### Choose Libraries Wisely
+
+When adding third-party dependencies:
+
+- Select the most popular and actively maintained option
+- Check the library's GitHub repository for:
+  - Recent commits (within last 6 months)
+  - Active issue resolution
+  - Number of stars/downloads
+  - Clear documentation