@devobsessed/code-captain 0.2.0 → 0.2.1

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

@@ -1,20 +1,16 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Modify existing feature specifications with change tracking"
 ---
 
-# Edit Spec Command
+# You are executing the Edit Spec command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Modify existing feature specifications using a contract-first approach that ensures complete alignment between developer and AI before updating any supporting files. This command prevents assumptions by establishing a clear "modification contract" through structured clarification rounds.
-
-## Command Process
+Your mission: Modify an existing feature specification safely and precisely using a contract-first approach. Establish complete alignment on the modifications before updating any files.
 
 ### Phase 1: Specification Loading & Change Contract (No File Modifications)
 
-**Mission Statement:**
-> Your goal is to help me modify an existing specification safely and precisely. You will deliver the updated spec package only after we both agree on the modification contract. **Important: Challenge changes that could break existing functionality or create technical debt - it's better to surface concerns early than implement problematic modifications.**
-
 #### Step 1.1: Specification Discovery & Loading
 
 **Locate Target Specification:**
@@ -83,13 +79,6 @@ Modify existing feature specifications using a contract-first approach that ensu
 - **Scope Creep**: Are we expanding beyond the original contract boundaries?
 - **Business Value**: Do changes improve or compromise original user value?
 
-**Question Categories (examples):**
-- "This change would affect [existing user story]. Should we modify that story or create a new one?"
-- "I see this conflicts with [existing implementation]. Should we plan a migration strategy?"
-- "This modification increases complexity in [area]. Is the added value worth the technical cost?"
-- "The original spec was focused on [goal]. How does this change serve that same goal?"
-- "This would require changes to [dependent system]. Have you considered the downstream impact?"
-
 #### Step 1.4: Modification Contract Proposal
 
 When confident about changes, present a modification contract:
@@ -109,7 +98,7 @@ When confident about changes, present a modification contract:
 - **New Stories Required:** [Any additional story files to be created]
 - **Stories to Remove/Combine:** [Any story files that become obsolete]
 - **Task Groups Affected:** [Which task groups within stories need modification]
-- **Technical Components Affected:** [Code/architecture areas needing updates]  
+- **Technical Components Affected:** [Code/architecture areas needing updates]
 - **Implementation Status:** [How much existing work across stories is affected]
 
 **Migration Strategy:**
@@ -125,11 +114,11 @@ When confident about changes, present a modification contract:
 - **Removed From Scope:** [What gets removed]
 - **Still Out of Scope:** [Unchanged exclusions]
 
-**⚠️ Risks & Concerns:**
+**Risks & Concerns:**
 - [Specific technical or business risks from the changes]
 - [Potential complications or dependencies]
 
-**💡 Recommendations:**
+**Recommendations:**
 - [Suggestions for safer implementation approaches]
 - [Ways to minimize disruption to existing work]
 
@@ -217,74 +206,11 @@ Options:
 - **Combine stories** if task counts become too small
 - **Reorder stories** if dependencies changed
 
-**Story-Level Task Annotations:**
-```markdown
-# In story-1-user-auth.md:
-- [x] 1.1 Write tests for user authentication ✅ (Still valid)
-- [ ] 1.2 Implement OAuth provider ⚠️ (Needs modification)
-- [ ] 1.3 Create social login UI 🆕 (New task from scope change)
-- [~~] 1.4 Implement mobile-specific auth ❌ (Moved to new story-4-mobile-auth.md)
-
-# New story-4-mobile-auth.md created if mobile auth becomes separate feature
-```
-
-**Story Management:**
-- **Split large stories**: If modifications would create >7 tasks, create additional story files
-- **Archive obsolete stories**: Move removed stories to archived/ subfolder with timestamp
-- **Update story dependencies**: Modify README.md to reflect new story relationships
-- **Maintain story cohesion**: Ensure each story delivers standalone user value
-
 #### Step 2.5: Final Update Review & Validation
 
-Present updated package with change summary:
-```
-✅ Specification successfully updated!
-
-📁 .code-captain/specs/[DATE]-feature-name/
-├── 📋 spec.md - ⭐ Updated specification
-├── 📝 spec-lite.md - ⭐ Updated AI context summary  
-├── 👥 user-stories/ - ⭐ Updated story organization
-│   ├── 📊 README.md - ⭐ Updated progress tracking and dependencies
-│   ├── 📝 story-1-{name}.md - ⭐ Modified stories (5-7 tasks each)
-│   ├── 📝 story-2-{name}.md - 🆕 New stories or combinations
-│   ├── 📂 archived/ - 🗃️ Obsolete stories (if any)
-│   └── 📝 story-N-{name}.md - ⭐ Focused task groups
-├── 📂 sub-specs/
-│   ├── 🔧 technical-spec.md - ⭐ Updated if affected
-│   └── [other sub-specs...]
-├── 💾 backups/[timestamp]/ - Original files and stories preserved
-└── 📝 CHANGELOG.md - ⭐ Change documentation
-
-## Summary of Changes:
-- **Stories Modified:** [X] existing story files updated
-- **Stories Added:** [Y] new story files created
-- **Stories Removed/Archived:** [Z] story files no longer needed
-- **Task Groups Affected:** [N] task groups reorganized
-- **Modified Components:** [List of changed technical components]
-
-## Impact on Implementation:
-- **Stories Still Valid:** [X] out of [Y] stories remain unchanged  
-- **Stories Requiring Rework:** [N] stories need modification
-- **New Stories Added:** [N] new stories created (with focused task groups)
-- **Stories Archived:** [N] stories no longer needed
-- **Total Tasks:** [N] tasks across all stories (max 5-7 per story)
-
-Please review the updated specification:
-- Does this accurately reflect the agreed modifications?
-- Are the user stories appropriately organized (5-7 tasks per story)?
-- Should any stories be further split or combined?
-- Are story dependencies correctly updated in the README?
-- Should any additional changes be made?
-
-The updated user-stories folder structure provides:
-- **Focused development**: Work on one story at a time
-- **Better organization**: Each story file is manageable and self-contained
-- **Team collaboration**: Different stories can be assigned to different developers
-- **Clear progress tracking**: README overview shows status across all stories
-- **Flexible workflow**: Stories can be completed independently where possible
-
-The original version is safely backed up in the backups folder. If you need to rollback any changes, I can help restore from backup.
-```
+Present updated package with change summary showing files modified, stories added/removed/archived, task groups reorganized, and total task count.
+
+The original version is safely backed up in the backups folder. If the user needs to rollback any changes, offer to help restore from backup.
 
 ## Tool Integration
 
@@ -299,98 +225,3 @@ The original version is safely backed up in the backups folder. If you need to r
 - Backup system for safe modification tracking
 - Change logs for audit trail and rollback capability
 - User stories organized in individual files for better management
-
-## Key Features
-
-### 1. Safe Modification Process
-- **Backup creation** before any changes
-- **Change tracking** with detailed logs
-- **Rollback capability** to restore previous versions
-- **Impact assessment** before making changes
-
-### 2. Precise Change Control
-- **Focused clarification** about specific modifications
-- **Risk assessment** for breaking changes
-- **Migration strategy** for existing implementation
-- **Selective updates** only to affected components
-
-### 3. Implementation Continuity
-- **Task status preservation** for completed work
-- **Clear annotation** of what needs rework
-- **Priority reassessment** based on changes
-- **Timeline impact** analysis
-
-### 4. Change Documentation
-- **Detailed change logs** for audit trail
-- **Before/after comparison** capability
-- **Modification rationale** capture
-- **Rollback instructions** for safety
-
-## Example Usage Flow
-
-```
-Developer: /edit-spec "user-auth" "add biometric authentication"
-
-Agent: I found your user authentication specification from 2024-01-15. Let me load the current state...
-
-[Loads spec.md, tasks.md, and sub-specs]
-
-Current specification includes email/password auth with OAuth social login. I see there are 8 user stories, with 3 already implemented in your codebase.
-
-I have a concern about adding biometric authentication: your current implementation is web-focused, but biometric auth typically requires native mobile or desktop apps. I see no mobile components in your existing specification.
-
-First question: Are you planning to add mobile app development to this specification, or do you want to use WebAuthn for browser-based biometric authentication?
-
-Developer: WebAuthn for browser-based
-
-Agent: That makes more sense with your existing web architecture. However, WebAuthn requires HTTPS and has limited browser support. I see your current implementation supports users who may be on older browsers.
-
-Should we make biometric authentication an optional enhancement for supported browsers, or do you want to require it for all users (which might break compatibility)?
-
-Developer: Optional enhancement for supported browsers
-
-Agent: [Continues with more questions about UX, fallback behavior, etc.]
-
-## Modification Contract
-
-**Target Specification:** User Authentication System (2024-01-15)
-
-**Proposed Changes:** Add WebAuthn biometric authentication as optional enhancement
-
-**Change Type:** Addition (with graceful degradation)
-
-**Impact Assessment:**
-- **User Stories Affected:** Story 2 (Login flow) needs biometric option
-- **Technical Components Affected:** Frontend auth component, browser capability detection
-- **Implementation Status:** 3/8 stories completed, none affected by this change
-
-**Migration Strategy:**
-- Existing auth flows remain unchanged
-- Add biometric as progressive enhancement
-- No breaking changes to current implementation
-
-**Updated Success Criteria:** Users can log in with biometrics on supported browsers, fallback to existing methods
-
-**⚠️ Risks & Concerns:**
-- Browser support varies (Chrome 67+, Firefox 60+, Safari 14+)
-- Requires HTTPS in production
-- UX complexity for unsupported browsers
-
-**💡 Recommendations:**
-- Feature detection before offering biometric option
-- Clear messaging when biometric unavailable
-- Analytics to track adoption rates
-
-**Effort Estimate:** ~2-3 additional days (1 story addition, modest technical complexity)
-
----
-Options: [yes/edit/compare/risks/rollback]
-
-Developer: yes
-
-Agent: ✅ Modification contract locked! Updating specification...
-
-[Updates files, creates backups, documents changes]
-```
-
-This approach ensures that specification modifications are as careful and controlled as the original creation process, while preserving existing work and providing safety mechanisms for complex changes.

package/copilot/prompts/execute-task.prompt.md

@@ -1,20 +1,18 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Execute implementation tasks using TDD from specifications"
 ---
 
-# Execute Task Command
+# You are executing the Execute Task command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Execute a specific task and its sub-tasks systematically following a Test-Driven Development (TDD) workflow. This command reads task specifications from `.code-captain/specs/` directories and implements features with comprehensive testing, following established code standards and best practices.
-
-**Note:** This command automatically detects and lists available task specifications for selection, or executes a specific task if context is clear.
+Your mission: Execute a specific task and its sub-tasks systematically following a Test-Driven Development (TDD) workflow. Read task specifications from `.code-captain/specs/` directories and implement features with comprehensive testing.
 
 ## CRITICAL REQUIREMENT: 100% Test Pass Rate
 
-**⚠️ ZERO TOLERANCE FOR FAILING TESTS ⚠️**
+**ZERO TOLERANCE FOR FAILING TESTS**
 
-This command enforces strict test validation:
 - **NO story can be marked "COMPLETED" with ANY failing tests**
 - **100% test pass rate is MANDATORY before completion**
 - **"Edge case" or "minor" test failures are NOT acceptable**
@@ -22,8 +20,6 @@ This command enforces strict test validation:
 
 If tests fail, the story remains "IN PROGRESS" until all failures are resolved.
 
-## Command Process
-
 ### Step 1: Task Discovery & Selection
 
 **Scan for available specifications:**
@@ -110,7 +106,7 @@ For each implementation task within the story:
 4. **Validate all acceptance criteria are met for the user story**
 5. **Confirm story delivers the specified user value**
 
-**⚠️ STORY CANNOT BE MARKED COMPLETE WITH ANY FAILING TESTS ⚠️**
+**STORY CANNOT BE MARKED COMPLETE WITH ANY FAILING TESTS**
 
 ### Step 5: Story Completion & Status Updates
 
@@ -131,14 +127,3 @@ Update story file status and progress tracking files with completion details, en
 - File-based progress tracking in `.code-captain/current-task-progress.md`
 - Story status updates in specification files
 - Test execution results documentation
-
-## Quality Standards
-
-**Test-Driven Development:**
-- Tests written before implementation
-- **100% test pass rate MANDATORY before task completion**
-- **ZERO TOLERANCE for failing tests - no story completion with any failures**
-- Comprehensive coverage including edge cases
-- Regression testing for existing functionality
-
-This command ensures systematic, test-driven implementation with proper documentation and progress tracking using file-based systems compatible with GitHub Copilot.

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

@@ -1,12 +1,13 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Generate comprehensive code explanations with diagrams"
 ---
 
-# Explain Code Command
+# You are executing the Explain Code command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Provide comprehensive, AI-powered explanations of code segments, functions, classes, or entire files. This command combines natural language explanations with visual diagrams to help developers understand complex code quickly and thoroughly.
+Your mission: Provide a comprehensive, visual explanation of the specified code target. Combine natural language explanations with Mermaid diagrams to help the developer understand the code quickly and thoroughly.
 
 ## Parameters
 
@@ -46,31 +47,31 @@ The command automatically:
 
 ## Output Structure
 
-All explanations are displayed in chat and automatically saved to `.code-captain/explanations/`
+Display in chat and automatically save to `.code-captain/explanations/`.
 
 ### Chat Display
 
 ```
-📋 Function Overview
+Function Overview
 ├── Purpose: What this code does
 ├── Parameters: Input expectations
 ├── Return Value: What it outputs
 ├── Key Logic: Step-by-step breakdown
 └── Usage Examples: How to call it
 
-🔄 Execution Flow
+Execution Flow
 ├── [Flowchart diagram showing decision paths]
 ├── Decision points and branches
 ├── Error handling paths
 └── Performance characteristics
 
-🏗️ Architecture Context
+Architecture Context
 ├── Where this fits in the system
 ├── Dependencies and related components
 ├── Design patterns used
 └── Integration points
 
-⚡ Technical Details
+Technical Details
 ├── Time complexity
 ├── Memory usage
 ├── Potential issues
@@ -79,6 +80,8 @@ All explanations are displayed in chat and automatically saved to `.code-captain
 
 ### Saved Format
 
+Save as `.code-captain/explanations/[DATE]-[target-name].md`:
+
 ````markdown
 # Code Explanation: [Target Name]
 
@@ -116,99 +119,11 @@ _Generated by Code Captain on [timestamp]_
 _Last updated: [timestamp]_
 ````
 
-## File Organization
-
-Saved explanations are stored with date prefixes for chronological organization:
-
-```
-.code-captain/
-└── explanations/
-    ├── 2024-01-15-AuthenticationFlow.md
-    ├── 2024-01-16-PaymentProcessor.md
-    ├── 2024-01-16-UserService.md
-    └── 2024-01-17-SearchAlgorithm.md
-```
-
-Files are named using the format: `[DATE]-[target-name].md` where DATE is YYYY-MM-DD format.
-
 ## Auto-Save Behavior
 
-All explanations are automatically saved to `.code-captain/explanations/` using the format `[DATE]-[target-name].md`.
-
 Get current date by running: `npx @devobsessed/code-captain date`
 
-**Example filename:** `.code-captain/explanations/2025-09-27-AuthenticationFlow.md`
-
-## Integration Points
-
-### With Other Commands
-
-```
-# Saved explanations can be referenced by other commands
-/research authentication
-/create-spec payment-processing
-/execute-task "optimize the user search"
-
-# AI can access saved explanations from .code-captain/explanations/
-# to provide better context for other commands
-```
-
-### With IDE Integration
-
-- Hover over function calls to see saved explanations
-- Right-click context menu: "Explain with Code Captain"
-- Inline explanation widgets for complex code blocks
-
-## Management Commands
-
-```
-# List all saved explanations
-/list-explanations
-
-# Search explanations
-/search-explanations "authentication"
-
-# Show explanation history
-/explanation-history calculateDiscount
-
-# Update outdated explanations when code changes
-/refresh-explanations --check-code-changes
-```
-
-## Diagram Types Generated
-
-### Flowcharts
-
-- Control flow through functions
-- Decision trees for complex logic
-- Error handling paths
-
-### Sequence Diagrams
-
-- Function call sequences
-- API interaction flows
-- Database transaction flows
-
-### Class Diagrams
-
-- Object relationships
-- Inheritance hierarchies
-- Dependency structures
-
-### Architecture Diagrams
-
-- Component interactions
-- Data flow through system
-- Service communication patterns
-
-## Output Characteristics
-
-All explanations use a consistent intermediate technical level that balances accessibility with depth:
-
-- **Technical but accessible**: Explains how the code works with some optimization details
-- **Full context**: Always includes related functions, dependencies, and architectural context
-- **Visual diagrams**: Every explanation includes appropriate flowcharts, sequence diagrams, or class diagrams
-- **Comprehensive coverage**: Shows how the code fits in the entire system
+Save all explanations automatically to `.code-captain/explanations/` using the format `[DATE]-[target-name].md`.
 
 ## AI Processing Workflow
 
@@ -217,7 +132,7 @@ All explanations use a consistent intermediate technical level that balances acc
 3. **Explanation Generation**: Create intermediate-level natural language description
 4. **Diagram Creation**: Generate appropriate visual representations (flowcharts, sequence, class diagrams)
 5. **Formatting**: Structure output for both chat display and markdown file
-6. **Auto-Save**: Save explanation to `.code-captain/explanations/` with date-prefixed filename `[DATE]-[target-name].md`
+6. **Auto-Save**: Save explanation to `.code-captain/explanations/` with date-prefixed filename
 
 ## Tool Integration
 
@@ -234,43 +149,3 @@ All explanations use a consistent intermediate technical level that balances acc
 - Explanations stored in `.code-captain/explanations/`
 - Date-prefixed filenames for chronological organization
 - Cross-references to related explanations and components
-
-## Error Handling
-
-### Common Issues
-
-- **Code not found**: "Could not locate [target]. Please check the path/name."
-- **Too complex**: "This code is very complex. Consider breaking into smaller explanations."
-- **Limited context**: "Some context may be missing. Ensure related files are accessible."
-
-### Fallback Behaviors
-
-- If diagrams fail to generate, provide text-based flow description
-- If target is ambiguous, offer multiple options to choose from
-- If code is too large, suggest breaking into smaller segments
-
-## Success Metrics
-
-Track effectiveness through:
-
-- Explanation clarity ratings from users
-- Frequency of re-explanations for same code
-- Time saved in code reviews and onboarding
-- Reduction in "what does this do?" questions during development
-
-## Future Enhancements
-
-### Planned Features
-
-- Interactive explanations with expandable sections
-- Voice-generated explanations for accessibility
-- Integration with code review tools
-- Automatic explanation updates when code changes
-- Explanation versioning and history tracking
-
-### Advanced Capabilities
-
-- Performance profiling integration
-- Security vulnerability highlighting in explanations
-- Code quality suggestions as part of explanations
-- Integration with documentation generation tools

package/copilot/prompts/initialize.prompt.md

@@ -1,14 +1,13 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Analyze and set up project foundation with documentation"
 ---
 
-# Initialize Command
+# You are executing the Initialize command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Analyze and set up technical foundation for either greenfield (new) or brownfield (existing) projects. This command intelligently detects project type, scans the codebase, and generates foundational documentation including technology stack analysis, code style guide, and architectural overview.
-
-## Command Process
+Your mission: Analyze the current project and set up the technical foundation. Detect whether this is a greenfield (new) or brownfield (existing) project, scan the codebase, and generate foundational documentation.
 
 ### Step 1: Project Type Detection
 
@@ -35,10 +34,10 @@ Analyze and set up technical foundation for either greenfield (new) or brownfiel
 
 Generate foundational documents in `.code-captain/docs/`:
 
-**tech-stack.md** - Complete technology inventory and analysis
-**code-style.md** - Observed patterns and coding conventions  
-**objective.md** - Inferred or defined project purpose and goals
-**architecture.md** - System architecture overview and decisions
+- **tech-stack.md** - Complete technology inventory and analysis
+- **code-style.md** - Observed patterns and coding conventions
+- **objective.md** - Inferred or defined project purpose and goals
+- **architecture.md** - System architecture overview and decisions
 
 ### Step 4: Next Steps Recommendation
 
@@ -61,5 +60,3 @@ Provide clear guidance on next steps, typically:
 **Documentation organization:**
 - Progress documented in `.code-captain/initialization-progress.md`
 - Results organized in `.code-captain/docs/` folder
-
-This command provides comprehensive project analysis and setup using GitHub Copilot's native capabilities.