@devobsessed/code-captain 0.0.8 → 0.1.0

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/plan-product.md

@@ -1,330 +0,0 @@
----
-description: "Generate comprehensive product planning documentation using contract-first approach with structured discovery"
----
-
-# Plan Product Workflow
-
-## Overview
-
-Generate comprehensive product planning documentation using contract-first approach. Establishes clear product vision, mission, and roadmap through structured discovery, then creates complete product planning package.
-
-## Usage
-
-```bash
-/plan-product "product idea description"
-```
-
-## Process
-
-### Phase 1: Product Discovery & Contract (No Files Created)
-
-**Mission:** Transform rough product idea into comprehensive, actionable product plan. Challenge ideas that don't make business or technical sense.
-
-#### Step 1.1: Context Scan
-- Scan existing `.code-captain/product/` for product documentation
-- Load project context from `.code-captain/docs/` (tech-stack.md if available)
-- Review existing product mission or objectives
-- **Output:** Product context summary and foundation assessment
-
-#### Step 1.2: Gap Analysis (Internal)
-Silently identify missing details across:
-- Product vision and core value proposition
-- Target market and user personas
-- Key features and functionality scope
-- Business model and monetization strategy
-- Technical feasibility and architecture requirements
-- Competitive landscape and differentiation
-- Success metrics and validation criteria
-- Timeline expectations and resource constraints
-- Risk factors and mitigation strategies
-
-#### Step 1.3: Structured Discovery Loop
-
-**Rules:**
-- Ask ONE focused question at a time
-- After each answer, re-analyze context and technical feasibility
-- Continue until reaching 95% confidence on product deliverable
-- **Challenge ideas that don't make business or technical sense**
-- Never declare "final question" - let conversation flow naturally
-
-**Critical Analysis Examples:**
-- "I see a potential issue with [scope] because [business/technical reason]. Would focusing on [core value] first work better?"
-- "Based on your existing codebase, [proposed approach] might require significant architecture changes. Are you prepared for that?"
-- "The market you're describing sounds very broad. Should we focus on [specific segment] to start?"
-
-**Question Categories:**
-- "Who specifically has this problem, and how painful is it for them?"
-- "What would make someone switch from their current solution to yours?"
-- "How will you measure product success in the first 6 months?"
-- "What's your biggest constraint - time, budget, technical expertise, or market access?"
-
-#### Step 1.4: Product Contract Proposal
-
-When confident, present contract proposal:
-
-```
-## Product Planning Contract
-
-**Product Vision:** [One clear sentence describing product and primary value]
-
-**Target Market:** [Specific user segment with core problem]
-
-**Unique Value:** [What makes this different/better than alternatives]
-
-**Success Criteria:** [How you'll measure product-market fit and growth]
-
-**MVP Scope:** 
-- Core Features: [3-5 essential features for first version]
-- Success Metrics: [Key performance indicators]
-
-**Product Architecture:**
-- Complexity Level: [Simple/Moderate/Complex based on features]
-- Integration Needs: [How this fits with existing business systems]
-- Scale Requirements: [Expected user growth and feature expansion]
-
-**⚠️ Product Risks (if any):**
-- [Market risk, technical risk, or business model concerns]
-- [Suggested validation approach or risk mitigation]
-
-**💡 Recommendations:**
-- [Suggestions for improving product-market fit]
-- [Ways to validate assumptions early and reduce risk]
-
-**Roadmap Phases:**
-- Phase 1 (MVP): [Core value delivery - weeks/months]
-- Phase 2 (Growth): [Key expansion features - months]
-- Phase 3 (Scale): [Advanced capabilities - quarters]
-
----
-Options:
-- Type 'yes' to lock this contract and create the product planning package
-- Type 'edit: [your changes]' to modify the contract
-- Type 'risks' to explore potential market/technical risks in detail
-- Ask more questions if anything needs clarification
-```
-
-### Phase 2: Product Planning Package Creation (Post-Agreement Only)
-
-**Triggered only after user confirms contract with 'yes'**
-
-#### Step 2.1: Initialize Tracking
-Use memory feature to track creation process:
-1. Create product planning folder structure
-2. Generate core product mission document
-3. Develop product roadmap with phases
-4. Create decision log and rationale
-5. Generate lite mission for AI context
-6. Present package for user review and validation
-
-#### Step 2.2: Create Directory Structure
-
-**Generated folder:**
-```
-.code-captain/product/
-├── mission.md                 # Complete product vision and strategy
-├── mission-lite.md           # Condensed version for AI context
-├── roadmap.md                # Development phases and timeline
-├── decisions.md              # Decision log with rationale
-└── research/                 # Supporting research and analysis
-```
-
-#### Step 2.3: Generate Core Documents
-
-**mission.md** - Built from locked contract:
-```markdown
-# Product Mission
-
-> Created: [DATE]
-> Status: Planning
-> Contract Locked: ✅
-
-## Pitch
-[PRODUCT_NAME] is a [PRODUCT_TYPE] that helps [TARGET_USERS] [SOLVE_PROBLEM] by providing [KEY_VALUE_PROPOSITION].
-
-## Users
-### Primary Customers
-- [CUSTOMER_SEGMENT]: [DESCRIPTION and pain points]
-
-### User Personas
-**[PRIMARY_USER_TYPE]** ([AGE_RANGE])
-- **Role:** [JOB_TITLE or context]
-- **Context:** [Where/when they encounter the problem]
-- **Pain Points:** [Specific problems this product solves]
-- **Goals:** [What success looks like for them]
-
-## The Problem
-### [MAIN_PROBLEM_TITLE]
-[Problem description with quantifiable impact where possible]
-
-**Our Solution:** [How the product specifically addresses this problem]
-
-## Differentiators
-### [KEY_DIFFERENTIATOR]
-Unlike [EXISTING_ALTERNATIVES], we provide [SPECIFIC_ADVANTAGE]. This results in [MEASURABLE_BENEFIT].
-
-## Key Features
-### Core Features (MVP)
-- **[FEATURE_NAME]:** [User benefit and value]
-
-### Growth Features (Phase 2)
-- **[FEATURE_NAME]:** [User benefit and expansion value]
-
-### Scale Features (Phase 3)
-- **[FEATURE_NAME]:** [Advanced capabilities]
-```
-
-**roadmap.md** - Phased development plan:
-```markdown
-# Product Roadmap
-
-> Based on Product Contract: [DATE]
-
-## Phase 1: MVP (Minimum Viable Product)
-**Timeline:** [Weeks/months]
-**Goal:** Validate core value proposition with target users
-
-### Success Criteria
-- [Measurable criteria for product-market fit]
-- [Key metrics to track]
-
-### Core Features
-- [ ] [FEATURE] - [User value] `[Effort: XS/S/M/L/XL]`
-- [ ] [FEATURE] - [User value] `[Effort: XS/S/M/L/XL]`
-
-### Technical Foundation
-- [ ] [Infrastructure setup]
-- [ ] [Core architecture implementation]
-- [ ] [Testing and deployment pipeline]
-
-### Validation Targets
-- [Number] active users using core feature
-- [Metric] user retention rate
-- [Feedback] qualitative validation criteria
-
-## Phase 2: Growth (Market Expansion)
-**Timeline:** [Months]
-**Goal:** Scale user base and expand feature set
-
-### Growth Features
-- [ ] [FEATURE] - [Expansion value] `[Effort]`
-- [ ] [FEATURE] - [User experience improvement] `[Effort]`
-
-## Phase 3: Scale (Advanced Capabilities)
-**Timeline:** [Quarters]
-**Goal:** Establish market leadership and advanced functionality
-
-### Advanced Features
-- [ ] [FEATURE] - [Competitive advantage] `[Effort]`
-- [ ] [FEATURE] - [Enterprise/scale capability] `[Effort]`
-
-## Effort Sizing
-- **XS:** 1-2 days
-- **S:** 3-5 days  
-- **M:** 1-2 weeks
-- **L:** 3-4 weeks
-- **XL:** 1+ months
-```
-
-#### Step 2.4: Generate Decision Log
-
-**decisions.md** - Key product and technical decisions:
-```markdown
-# Product Decisions Log
-
-> Override Priority: Highest
-
-## [DATE]: Initial Product Planning
-**ID:** DEC-001
-**Status:** Accepted
-**Category:** Product
-
-### Decision
-[Summarize: product vision, target market, key features, technical approach]
-
-### Context
-[Market opportunity, user problems, strategic rationale]
-
-### Alternatives Considered
-1. **[ALTERNATIVE_APPROACH]**
-   - Pros: [Benefits]
-   - Cons: [Drawbacks]
-   - Why rejected: [Reasoning]
-
-### Rationale
-[Key factors that drove this product direction]
-
-### Consequences
-**Positive:**
-- [Expected benefits and advantages]
-
-**Negative:**
-- [Known tradeoffs and constraints]
-
-### Success Metrics
-- [How we'll measure if this decision was correct]
-```
-
-#### Step 2.5: Create Mission-Lite
-
-**mission-lite.md** - Condensed product context for AI:
-```markdown
-# Product Mission (Lite)
-
-> Source: Complete mission.md
-> Purpose: Efficient AI context for development
-
-## Core Value
-[1-2 sentences capturing essential product value proposition]
-
-## Target Users
-[Primary user segment and core problem]
-
-## Key Differentiator
-[What makes this unique in 1 sentence]
-
-## Success Definition
-[How we measure product success]
-
-## Current Phase
-[MVP/Growth/Scale - what we're building now]
-```
-
-#### Step 2.6: Final Package Review
-
-Present complete package:
-```
-✅ Product planning package created successfully!
-
-📁 .code-captain/product/
-├── 📋 mission.md - Complete product vision and strategy
-├── 📝 mission-lite.md - AI context summary
-├── 🗺️ roadmap.md - Phased development plan
-└── 📊 decisions.md - Decision log and rationale
-
-Please review the planning documents and let me know:
-- Does this accurately capture your product vision?
-- Are there any missing requirements or incorrect assumptions?
-- Should any product decisions be reconsidered?
-- Does the roadmap timeline align with your expectations?
-
-Once satisfied, you can use:
-- `/create-spec` to detail specific features from the roadmap
-- `/execute-task` to begin implementing planned features
-- `/research` to investigate any market or product unknowns
-```
-
-## Implementation with Windsurf Tools
-
-**File Operations:**
-- Use `write_to_file` to create product planning documents
-- Use `view_file` to review existing product documentation
-- Use `find_by_name` to locate related files
-
-**Research Tools:**
-- Use `search_web` for market research and competitive analysis
-- Use memory feature to track discovery progress and key decisions
-
-**Integration:**
-- Works with existing `.code-captain/product/` directory structure
-- Feeds into feature specification and development workflows
-- Supports cross-command integration with research and ADR workflows