@devobsessed/code-captain 0.0.6 → 0.0.9

package/windsurf/workflows/new-command.md

@@ -1,321 +0,0 @@
----
-description: Create new Code Captain workflows following established patterns and conventions for Windsurf
----
-
-# New Command Workflow
-
-## Overview
-A meta workflow that creates new Code Captain workflows following established patterns and conventions. This workflow generates properly structured workflow files, updates documentation, and ensures consistency across the Code Captain ecosystem for Windsurf environments.
-
-## Usage Examples
-
-```bash
-# Create a new workflow
-/new-command "optimize" "Performance optimization for slow code sections"
-
-# Create deployment workflow
-/new-command "deploy" "Deploy applications to various cloud platforms"
-
-# Create test generation workflow
-/new-command "test-gen" "Generate comprehensive test suites from existing code"
-```
-
-## Workflow Process
-
-### Step 1: Command Specification Gathering
-
-**Initial Input Processing:**
-- Parse workflow name (validate format: lowercase, hyphens allowed)
-- Extract brief description from user input
-- Use `find_by_name` to validate workflow name doesn't conflict with existing workflows
-
-**Interactive Specification Building:**
-
-Ask clarifying questions to build complete workflow specification:
-
-1. **Workflow Category**: "Is this a [Setup/Analysis/Implementation/Integration] workflow?"
-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?"
-5. **Output Location**: "Where should outputs be stored? (.code-captain/[folder])"
-6. **Tool Integration**: "Which Windsurf tools will it use? (codebase_search, view_file, etc.)"
-7. **Workflow Steps**: "What are the main phases/steps the workflow follows?"
-
-### Step 2: Workflow Structure Generation
-
-**Generate Standard Workflow File Structure:**
-
-Use `write_to_file` to create workflow in `.windsurf/workflows/[command-name].md`:
-
-```markdown
----
-description: [Generated from description and clarifying questions]
----
-
-# [Command Name] Workflow
-
-## Overview
-[Generated from description and clarifying questions]
-
-## Usage Examples
-
-```bash
-# Primary usage
-/[command-name] [arguments]
-
-# Example scenarios
-/[command-name] [example-args]
-```
-
-## Workflow Process
-
-### Step 1: [Phase Name]
-[Generated workflow steps]
-
-### Step 2: [Phase Name]
-[Generated workflow steps]
-
-## Core Rules
-[Generated based on workflow type]
-
-## Integration with Code Captain Ecosystem
-[Generated integration details]
-
-## Windsurf Tools Used
-[Generated tool list]
-
-## Windsurf Features Used
-[Generated features list]
-
----
-*[Generated tagline]*
-```
-
-**Template Sections Based on Workflow Type and Execution Style:**
-
-**Contract Style Workflows** (like `create-spec`, `create-adr`):
-- Phase 1: Contract Establishment (No File Creation)
-- Interactive clarification rounds with structured questions
-- Critical analysis and assumption challenging
-- Contract proposal phase
-- Explicit user agreement before proceeding
-
-**Direct Execution Workflows** (like `swab`, `execute-task`):
-- Immediate action workflows
-- Minimal clarification if needed
-- Clear step-by-step execution
-- Progress feedback and completion confirmation
-
-**Setup/Analysis Workflows:**
-- Context scanning steps
-- File generation workflows
-- Documentation creation
-
-**Implementation Workflows:**
-- TDD workflows if applicable
-- Code modification steps
-- Verification procedures
-
-**Integration Workflows:**
-- Platform-specific API interactions
-- Sync and conflict resolution
-- Error handling patterns
-
-### Step 3: Tool Integration Mapping
-
-**Map appropriate Windsurf tools based on workflow type:**
-
-**File Operations:**
-- `view_file`, `write_to_file`, `replace_file_content`, `find_by_name`, `list_dir`, `grep_search`
-
-**Code Analysis:**
-- `codebase_search`, `view_code_item`, `trajectory_search`
-
-**Web & Browser:**
-- `browser_preview`, `open_browser_url`, `search_web`, `read_url_content`
-
-**System & Deployment:**
-- `run_command`, `command_status`, `deploy_web_app`
-
-**Memory & Context:**
-- `view_content_chunk`, Memories feature for important decisions
-
-### Step 4: Validation and Character Limit Check
-
-**Verify Workflow Integration:**
-- Use `view_file` to check workflow file syntax and structure
-- Use `run_command` with `wc -c` to validate under 12k character limit
-- Use `find_by_name` to ensure no conflicts with existing workflows
-- Run basic structure validation
-
-**Character Limit Enforcement:**
-```bash
-# Check if workflow is under 12k limit
-wc -c .windsurf/workflows/[command-name].md
-
-# Validate limit
-[ $(wc -c < .windsurf/workflows/[command-name].md) -lt 12000 ] && echo "✅ Under 12k" || echo "⚠️ Over 12k"
-```
-
-**Present Summary:**
-```
-✅ New workflow created successfully!
-
-📁 Files Created:
-  - .windsurf/workflows/[command-name].md
-
-🚀 Workflow Ready:
-  Usage: /[command-name] [args]
-  Documentation: .windsurf/workflows/[command-name].md
-  Character count: [X]/12000 characters
-
-📏 Character Limit: ✅ Under 12k limit
-```
-
-## Core Rules
-
-1. **Consistent Structure** - All generated workflows follow established Windsurf patterns
-2. **Clear Documentation** - Each section has purpose and implementation details
-3. **Character Limit Compliance** - All workflows must be under 12k characters
-4. **Slash Command Syntax** - Use /command-name format for all examples
-5. **Windsurf Tool Integration** - Use appropriate Windsurf tools for functionality
-6. **Template Flexibility** - Adapt template based on workflow type and requirements
-7. **Language & Shell Agnostic** - Workflows work across different programming languages using Windsurf's tools
-
-## Workflow Generation Templates
-
-### Contract Style Template Structure
-```markdown
-## Workflow Process
-
-### Step 1: Requirement Clarification
-**Gather detailed requirements through structured questions**
-- [Specific clarification questions]
-- [Assumption challenging]
-- [Context gathering]
-
-### Step 2: Contract Proposal
-**Present structured contract for user agreement**
-- [Contract format specific to workflow type]
-- [Success criteria definition]
-- [Scope boundaries]
-
-### Step 3: User Agreement
-**Explicit confirmation before proceeding**
-- [Agreement validation]
-- [Scope confirmation]
-
-### Step 4: Implementation
-**Execute workflow based on agreed contract**
-- [Implementation steps]
-- [Progress tracking]
-- [Validation procedures]
-```
-
-### Direct Execution Template Structure
-```markdown
-## Workflow Process
-
-### Step 1: Context Analysis
-**Analyze current state and requirements**
-- [Context gathering steps]
-- [Requirement analysis]
-
-### Step 2: Action Execution
-**Perform workflow actions directly**
-- [Action steps]
-- [Tool usage]
-- [Progress feedback]
-
-### Step 3: Verification
-**Validate results and completion**
-- [Verification steps]
-- [Quality checks]
-- [Completion confirmation]
-```
-
-## Command Name Validation
-
-**Validation Rules:**
-- Lowercase letters, numbers, hyphens only
-- No spaces or special characters
-- Maximum 20 characters
-- Cannot start with number or hyphen
-- Must not conflict with existing workflows
-
-**Validation Process:**
-Use `grep_search` and `find_by_name` to check for conflicts:
-```bash
-# Check existing workflows
-find_by_name "[command-name].md" in .windsurf/workflows/
-
-# Validate format using pattern matching
-```
-
-## Error Handling
-
-**Common Issues:**
-- **Duplicate workflow name**: Check existing workflows, suggest alternatives
-- **Invalid workflow name format**: Provide format guidance and examples
-- **Character limit exceeded**: Provide optimization suggestions
-- **Template generation errors**: Validate inputs, provide clear error messages
-
-**Error Messages:**
-```
-❌ Workflow creation failed: [specific reason]
-
-Suggestions:
-- Check workflow name format (lowercase, hyphens only)
-- Ensure name doesn't conflict with existing workflows
-- Verify all required inputs are provided
-- Ensure generated content is under 12k characters
-
-Try: /new-command "valid-name" "clear description"
-```
-
-## Integration with Code Captain Ecosystem
-
-**Workflow relationship:**
-- Generates workflows compatible with other Code Captain workflows
-- Follows established patterns from existing workflows
-- Maintains consistency in structure and tool usage
-- Ensures proper slash command syntax throughout
-
-**Cross-workflow integration:**
-- New workflows can reference existing workflows with proper `/workflow-name` syntax
-- Generated workflows include appropriate tool mappings
-- Documentation follows established Windsurf patterns
-- Character limit compliance ensures deployability
-
-## Quality Standards
-
-**Structure requirements:**
-- Proper frontmatter with description
-- Clear overview and usage examples
-- Detailed workflow process with numbered steps
-- Appropriate tool integration
-- Proper slash command syntax
-
-**Content quality:**
-- Clear, actionable workflow steps
-- Appropriate tool usage for each step
-- Proper error handling guidance
-- Integration notes with other workflows
-- Character count optimization
-
-## Windsurf Tools Used
-
-- `find_by_name`: Locate existing workflows and check for conflicts
-- `view_file`: Examine existing workflow patterns for consistency
-- `write_to_file`: Create new workflow files
-- `run_command`: Validate character limits and file structure
-- `codebase_search`: Understand existing workflow patterns
-- `grep_search`: Search for workflow naming conflicts and patterns
-
-## Windsurf Features Used
-
-- **Memories**: After creating complex workflows, ask Cascade to "create a memory of this workflow pattern and its structure"
-
----
-
-*🔧 Building workflows that build workflows - meta automation at its finest.*

package/windsurf/workflows/status.md

@@ -1,213 +0,0 @@
----
-description: Code Captain status report for project orientation and next actions
----
-
-# Code Captain Status Workflow
-
-## Overview
-Provides comprehensive status report when starting work or switching context. Analyzes git state, active work, and project health to orient developers and suggest next actions.
-
-## Core Functionality
-
-### 1. Git Status & Context Analysis
-Use `run_command` to gather git information:
-- Current branch and relationship to main/origin
-- Commits ahead/behind main branch  
-- Last commit message and timestamp
-- Uncommitted changes summary
-- Stash status
-
-### 2. Active Work Detection
-Use `codebase_search` and `view_file` to find:
-- Code Captain specs in `.code-captain/specs/`
-- Current task progress from most recent spec
-- Completed vs pending tasks
-- Current user story context
-
-### 3. Project Health Check
-Use `run_command` for language-specific checks:
-- Can the project build/compile?
-- Dependencies status (package.json, requirements.txt, etc.)
-- Configuration issues
-- Missing environment variables
-
-### 4. Contextual Suggestions
-Based on current state, suggest appropriate next commands.
-
-## Implementation Steps
-
-### Step 1: Git Analysis
-```bash
-# Use run_command for these git operations:
-git status --porcelain              # File changes
-git log --oneline -5                # Recent commits  
-git log main..HEAD --oneline        # Commits ahead
-git log HEAD..main --oneline        # Commits behind
-git stash list                      # Stashed changes
-git branch -v                       # Branch info
-```
-
-### Step 2: Code Captain Integration
-Use `find_by_name` to locate specs:
-```bash
-# Find most recent spec directory
-find .code-captain/specs -name "spec.md" -type f
-```
-
-Use `view_file` to read spec content and task progress:
-- Read overall progress from user stories overview
-- Parse individual story files for task completion
-- Count completed tasks (marked with [x])
-- Find next incomplete task
-
-### Step 3: Project Health
-Use `run_command` for health checks:
-```bash
-# Node.js
-npm run build --if-present
-node -c package.json
-
-# Python
-python -m py_compile main.py
-pip check
-```
-
-### Step 4: Generate Status Report
-
-**Output Format** (clean formatted text, not code blocks):
-
-```
-⚓ Code Captain Status Report
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-📍 CURRENT POSITION
-   Branch: feature/dashboard-websockets (2 commits ahead of main)
-   Last commit: "Add WebSocket connection hook" (2 hours ago)
-   Uncommitted: 3 modified files in src/components/
-
-📋 ACTIVE WORK
-   Spec: Real-time Dashboard with WebSocket Integration 
-   Progress: Story 2 (User receives real-time notifications) - In Progress
-   Tasks completed: 3/6 tasks (50%)
-   Next task: 2.4 Implement client-side WebSocket connection
-
-🎯 SUGGESTED ACTIONS
-   • Continue with task 2.4 (WebSocket connection management)
-   • Commit current changes before switching tasks
-   • Review recent main branch changes
-
-⚡ QUICK COMMANDS
-   Execute task workflow    # Continue current task
-   Code cleanup workflow    # Quick code improvements
-   Sync main workflow       # Pull latest from main
-```
-
-## Task Progress Analysis
-
-### Parsing Logic
-For each story file in `user-stories/story-N-{name}.md`:
-
-1. **Count completed tasks**:
-   ```bash
-   grep -c "^\- \[x\].*✅" story-file.md
-   ```
-
-2. **Count total tasks**:
-   ```bash
-   grep -c "^\- \[[x ]\]" story-file.md
-   ```
-
-3. **Find next incomplete task**:
-   ```bash
-   grep -n "^\- \[ \]" story-file.md | head -1
-   ```
-
-4. **Extract status from story header**:
-   ```bash
-   grep "^> \*\*Status:\*\*" story-file.md
-   ```
-
-### Status Detection
-- `Not Started` - No tasks completed
-- `In Progress` - Some tasks completed, some remaining
-- `Completed ✅` - All tasks and acceptance criteria completed
-
-## Error Handling
-
-### Not a Git Repository
-```
-❌ Not in a git repository
-   Initialize git first: git init
-```
-
-### No Code Captain Structure
-```
-📋 ACTIVE WORK
-   No Code Captain specifications found
-   Project structure: Standard git repository
-
-🎯 SUGGESTED ACTIONS
-   • Set up Code Captain workflow
-   • Create first feature specification
-```
-
-### Project Issues
-```
-⚠️  PROJECT ISSUES DETECTED
-   • package.json syntax error
-   • Missing critical dependencies
-   • Build process failing
-
-🔧 SUGGESTED FIXES
-   • Fix package.json syntax
-   • Run npm install or equivalent
-   • Check build configuration
-```
-
-## Decision Tree for Suggestions
-
-1. **Merge conflict?** → Suggest conflict resolution
-2. **Working directory dirty?** → Suggest commit or stash
-3. **Branch behind main?** → Suggest sync
-4. **Active task?** → Suggest continue task
-5. **Current task complete?** → Suggest next task
-6. **No active work?** → Suggest create spec
-7. **Always** → Suggest code cleanup
-
-## Usage Patterns
-
-### Morning Routine
-Developer starts day, gets oriented on yesterday's work, sees exactly what to do next.
-
-### Context Switching  
-After meetings or interruptions, quick reminder of current state, resume work efficiently.
-
-### Project Handoff
-When picking up someone else's work, understand current project state without diving into code.
-
-## Performance Considerations
-
-- Target <2 second execution time
-- Limit git log queries to reasonable ranges
-- Cache expensive operations when possible
-- Use efficient file scanning with `find_by_name`
-
-## Windsurf Tools Used
-
-- `run_command`: Git operations, build checks
-- `codebase_search`: Find specs and project structure
-- `view_file`: Read spec content and progress
-- `find_by_name`: Locate Code Captain files
-- `grep_search`: Parse task completion status
-- `list_dir`: Directory structure analysis
-
-## Security & Privacy
-
-- All analysis happens locally
-- No external API calls or data transmission
-- Git history and file contents remain private
-- Sanitize sensitive information in output
-
----
-
-*⚓ Keep your bearings, maintain your heading, and always know where you stand in the code.*