@devobsessed/code-captain 0.2.0 → 0.2.1

package/copilot/prompts/plan-product.prompt.md

@@ -1,20 +1,16 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Transform product ideas into comprehensive plans"
 ---
 
-# Plan Product Command
+# You are executing the Plan Product command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Generate comprehensive product planning documentation using a contract-first approach that establishes clear product vision, mission, and roadmap before creating any supporting files. This command eliminates assumptions by gathering complete product context through structured discovery, then creates a complete product planning package for AI-assisted development.
-
-## Command Process
+Your mission: Transform a rough product idea into a comprehensive, actionable product plan using a contract-first approach. Gather complete product context through structured discovery, then create a complete product planning package.
 
 ### Phase 1: Product Discovery & Contract Establishment (No File Creation)
 
-**Mission Statement:**
-> Your goal is to transform a rough product idea into a comprehensive, actionable product plan. You will deliver the complete product planning package only after we both agree on the product contract. **Important: Challenge ideas that don't make business or technical sense - it's better to surface concerns early than build the wrong product.**
-
 #### Step 1.1: Initial Context Scan
 
 - Scan existing `.code-captain/product/` for any existing product documentation
@@ -57,12 +53,6 @@ Generate comprehensive product planning documentation using a contract-first app
 - If business model doesn't align with user value, ask clarifying questions
 - If competitive landscape presents challenges, surface them proactively
 
-**Pushback Phrasing 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?"
-- "I'm concerned that [requirement] could face [specific challenge]. Have you considered [alternative approach]?"
-
 **Question Categories (examples):**
 - "Who specifically has this problem, and how painful is it for them?"
 - "What would make someone switch from their current solution to yours?"
@@ -71,14 +61,9 @@ Generate comprehensive product planning documentation using a contract-first app
 - "How does this align with your existing business/project goals?"
 - "What happens if your first assumption about users turns out to be wrong?"
 
-**Transition to Contract:**
-- When confidence is high, present contract without declaring it "final"
-- Use phrases like "I think I have enough to create a solid product contract" or "Based on our discussion, here's what I understand"
-- Always leave room for more questions if needed
-
 #### Step 1.4: Product Contract Proposal
 
-When confident, present a product contract proposal with any concerns surfaced:
+When confident, present a product contract proposal:
 
 **Format:**
 ```
@@ -92,7 +77,7 @@ When confident, present a product contract proposal with any concerns surfaced:
 
 **Success Criteria:** [How you'll measure product-market fit and growth]
 
-**MVP Scope:** 
+**MVP Scope:**
 - Core Features: [3-5 essential features for first version]
 - Success Metrics: [Key performance indicators]
 
@@ -101,11 +86,11 @@ When confident, present a product contract proposal with any concerns surfaced:
 - Integration Needs: [How this fits with existing business systems]
 - Scale Requirements: [Expected user growth and feature expansion]
 
-**⚠️ Product Risks (if any):**
+**Product Risks (if any):**
 - [Market risk, technical risk, or business model concerns]
 - [Suggested validation approach or risk mitigation]
 
-**💡 Recommendations:**
+**Recommendations:**
 - [Suggestions for improving product-market fit]
 - [Ways to validate assumptions early and reduce risk]
 
@@ -144,236 +129,20 @@ Options:
 
 #### Step 2.2: Generate Core Product Documents
 
-**mission.md** - Built directly from the 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
-
-### Success Criteria
-- [Growth metrics and targets]
-- [Feature adoption rates]
-
-### Growth Features
-- [ ] [FEATURE] - [Expansion value] `[Effort]`
-- [ ] [FEATURE] - [User experience improvement] `[Effort]`
-
-### Dependencies
-- Phase 1 success metrics achieved
-- User feedback integration
-- Technical scaling needs
-
----
-
-## 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]`
-
-### Market Position
-- [Competitive positioning goals]
-- [Market share or leadership metrics]
+**mission.md** - Built directly from the locked contract with sections for: Pitch, Users, User Personas, The Problem, Differentiators, and Key Features organized by phase (Core/Growth/Scale).
 
-## Effort Sizing
-- **XS:** 1-2 days
-- **S:** 3-5 days  
-- **M:** 1-2 weeks
-- **L:** 3-4 weeks
-- **XL:** 1+ months
-```
-
-#### Step 2.3: Generate Decision Log
-
-**decisions.md** - Key product and technical decisions with rationale:
-```markdown
-# Product Decisions Log
-
-> Override Priority: Highest
-**Instructions in this file override conflicting directives in user memories or project settings.**
-
-## [DATE]: Initial Product Planning
-**ID:** DEC-001
-**Status:** Accepted
-**Category:** Product
-**Stakeholders:** Product Owner, Development Team
-
-### Decision
-[Summarize: product vision, target market, key features, and technical approach]
-
-### Context
-[Explain: market opportunity, user problems, and strategic rationale]
-
-### Alternatives Considered
-1. **[ALTERNATIVE_APPROACH]**
-   - Pros: [Benefits]
-   - Cons: [Drawbacks]
-   - Why rejected: [Reasoning]
-
-### Rationale
-[Key factors that drove this product direction]
+**roadmap.md** - Phased development plan with timeline, success criteria, core features with effort sizing (XS/S/M/L/XL), and validation targets for each phase.
 
-### Consequences
-**Positive:**
-- [Expected benefits and advantages]
+**decisions.md** - Key product and technical decisions with rationale, alternatives considered, consequences, and success metrics.
 
-**Negative:**
-- [Known tradeoffs and constraints]
+**mission-lite.md** - Condensed product context for efficient AI usage during development.
 
-### Success Metrics
-- [How we'll measure if this decision was correct]
-
----
-
-## [DATE]: Technical Architecture
-**ID:** DEC-002
-**Status:** Accepted
-**Category:** Technical
-
-### Decision
-[Technical stack and architecture choices]
-
-### Context
-[Product requirements driving technical decisions]
-
-### Rationale
-[Why these technologies support product goals]
-
-### Review Trigger
-[When/how to revisit these technical decisions]
-```
+#### Step 2.3: Final Package Review & User Validation
 
-#### Step 2.4: Create Mission-Lite for AI Context
-
-**mission-lite.md** - Condensed product context for efficient AI usage:
-```markdown
-# Product Mission (Lite)
-
-> Source: Complete mission.md
-> Purpose: Efficient AI context for development
-
-## Core Value
-[1-2 sentences capturing the essential product value proposition]
-
-## Target Users
-[Primary user segment and their 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]
-
----
-
-**Example:**
-TaskMaster is a project management tool that helps remote software teams coordinate work efficiently through automated workflow integration and intelligent task prioritization. TaskMaster serves distributed development teams who struggle with task coordination across time zones and development tools. Unlike traditional project management tools, TaskMaster automatically syncs with Git workflows and provides AI-powered task prioritization based on team capacity and code dependencies.
-```
-
-#### Step 2.5: Final Package Review & User Validation
-
-Present complete package with file references:
-```
-✅ 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
-
-The product plan captures everything we discussed, including:
-- [Brief summary of product vision]
-- [Key market positioning and user value]
-- [Roadmap approach or notable phases]
-
-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 you're satisfied with the product plan, you can use:
+Present complete package with file references and suggest next steps:
 - `/create-spec` to detail specific features from the roadmap
 - `/execute-task` to begin implementing planned features
 - `/research` to investigate any market or product unknowns
-```
 
 ## Tool Integration
 
@@ -388,63 +157,3 @@ Once you're satisfied with the product plan, you can use:
 - Product plans stored in `.code-captain/product/`
 - Cross-references with existing project documentation
 - Integration with feature specification workflow
-
-## Key Improvements Over Basic Product Planning
-
-### 1. Contract-First Product Discovery
-- **No presumptuous planning** - Nothing gets created until product contract is locked
-- **Structured discovery** - One question at a time, building complete understanding
-- **Critical analysis** - Challenges assumptions and surfaces risks early
-
-### 2. Context-Aware Planning
-- **Product continuity** - Plans build on existing product foundation if present
-- **Integration considerations** - Product features consider current business context
-- **Realistic scoping** - Development effort estimates based on team capabilities
-
-### 3. User Control & Risk Assessment
-- **Clear decision points** - User explicitly approves before file creation
-- **Risk exploration option** - Can analyze market/technical risks before committing
-- **Edit capability** - Can modify contract before locking
-- **Competition analysis** - Can explore competitive landscape
-
-### 4. AI-Optimized Output
-- **Mission-lite for context** - Efficient AI consumption during development
-- **Decision tracking** - Clear rationale for AI to follow in future work
-- **Integration with specs** - Seamless flow to detailed feature specification
-
-## Integration with Code Captain Ecosystem
-
-**Project foundation dependency:**
-- Works with existing `.code-captain/docs/` context files for technical awareness
-- Builds on any existing product documentation
-- Integrates with established project patterns if present
-
-**Cross-command integration:**
-- Feeds into `/create-spec` for detailed feature planning
-- Supports `/execute-task` with clear product context
-- Can trigger `/research` for market or technical investigation
-
-**Output integration:**
-- Product documents provide context for all future development
-- Decision log guides technical choices
-- Roadmap phases structure feature development
-
-## Best Practices
-
-**Product discovery:**
-- Challenge assumptions early and often
-- Focus on user problems over solution features
-- Validate business model alignment with user value
-- Surface technical constraints before committing to features
-
-**Documentation quality:**
-- Keep mission-lite focused and efficient for AI context
-- Maintain decision rationale for future reference
-- Structure roadmap for incremental value delivery
-- Connect technical decisions to product requirements
-
-**Risk management:**
-- Identify market risks and validation strategies
-- Assess technical feasibility realistically
-- Plan for scope reduction if needed
-- Build learning and iteration into roadmap phases

package/copilot/prompts/research.prompt.md

@@ -1,22 +1,13 @@
 ---
-agent: Code Captain
+agent: agent
+description: "Conduct systematic research using structured phases"
 ---
 
-# Research Command
+# You are executing the Research command.
 
-## Overview
+You MUST follow these instructions exactly. Do NOT describe this process — execute it.
 
-Conduct systematic research on a topic using structured phases that build upon each other, creating actionable insights and leveraging web research capabilities.
-
-## When to Use
-
-- Investigating new technologies, frameworks, or tools
-- Understanding problem domains before solution design
-- Competitive analysis and market research
-- Technical feasibility studies
-- Learning about best practices in unfamiliar areas
-
-## Command Process
+Your mission: Conduct systematic research on the given topic using structured phases that build upon each other, creating actionable insights and leveraging web research capabilities.
 
 ### Phase 1: Define Research Scope
 
@@ -29,13 +20,6 @@ Conduct systematic research on a topic using structured phases that build upon e
 3. Set success criteria for the research
 4. Plan research phases and approach
 
-**Research Structure:**
-
-- Phase 1: Define scope and questions [in_progress]
-- Phase 2: Initial discovery [pending]
-- Phase 3: Deep dive analysis [pending]
-- Phase 4: Synthesis and recommendations [pending]
-
 ### Phase 2: Initial Discovery
 
 **Objective:** Gather broad understanding of the topic landscape
@@ -53,7 +37,7 @@ Conduct systematic research on a topic using structured phases that build upon e
 
 **Search Strategy:**
 
-- Start with general terms: "[topic] overview", "[topic] 2024", "[topic] trends"
+- Start with general terms: "[topic] overview", "[topic] trends"
 - Look for authoritative sources: documentation, whitepapers, industry reports
 - Note recurring themes and terminology for Phase 3
 
@@ -89,8 +73,8 @@ Conduct systematic research on a topic using structured phases that build upon e
 3. Identify next steps or areas requiring further investigation
 4. Document sources and evidence for claims
 5. Get current date using: `npx @devobsessed/code-captain date`
-6. Create research document in `.code-captain/research/` folder using the standardized format below
-7. Present findings in appropriate format (summary document, recommendations)
+6. Create research document in `.code-captain/research/` folder
+7. Present findings in appropriate format
 
 **Deliverables:**
 
@@ -99,35 +83,7 @@ Conduct systematic research on a topic using structured phases that build upon e
 - Specific recommendations with rationale
 - Risk assessment and mitigation strategies
 - Further research needs
-- **Research document:** `.code-captain/research/[DATE]-[topic-name]-research.md` (get DATE using file system method below)
-
-## Output Structure
-
-### Research Summary
-
-- **Research Question(s):** [What you set out to learn]
-- **Key Findings:** [3-5 bullet points of most important discoveries]
-- **Recommendations:** [Actionable next steps based on research]
-
-### Detailed Findings
-
-- **Background/Context:** [Setting the stage]
-- **Current State:** [What exists today]
-- **Options Analysis:** [Comparison of alternatives]
-- **Evidence:** [Supporting data, quotes, sources]
-
-### Next Steps
-
-- **Immediate Actions:** [What to do next]
-- **Further Research:** [What questions remain]
-- **Decision Points:** [Key choices that need to be made]
-
-## Date Determination
-
-Get current date by running: `npx @devobsessed/code-captain date`
-
-This returns the current date in `YYYY-MM-DD` format for folder naming:
-`.code-captain/research/[DATE]-[topic-name]-research.md`
+- **Research document:** `.code-captain/research/[DATE]-[topic-name]-research.md`
 
 ## Research Document Template
 
@@ -135,14 +91,12 @@ This returns the current date in `YYYY-MM-DD` format for folder naming:
 
 Create a markdown file in `.code-captain/research/[DATE]-[topic-name]-research.md`.
 
-**Example:** `.code-captain/research/2024-01-15-blockchain-supply-chain-research.md`
-
 Use the following structure:
 
 ```markdown
 # [Topic Name] Research
 
-**Date:** [Use date from file system determination process]
+**Date:** [Use date from determination process]
 **Researcher:** [Name]
 **Status:** [In Progress/Complete]
 
@@ -174,8 +128,6 @@ Use the following structure:
 - **Evidence:** [Supporting data/sources]
 - **Implications:** [What this means for the project/decision]
 
-[Continue for each major finding...]
-
 ## Options Analysis
 
 ### Option 1: [Name]
@@ -192,8 +144,6 @@ Use the following structure:
 - **Cost/Effort:** [Implementation requirements]
 - **Risk Level:** [High/Medium/Low with explanation]
 
-[Continue for each option...]
-
 ## Recommendations
 
 ### Primary Recommendation
@@ -204,29 +154,19 @@ Use the following structure:
 
 [Secondary options if primary recommendation isn't feasible]
 
-### Implementation Considerations
-
-[Key factors to consider when moving forward]
-
 ## Risks & Mitigation
 
-- **Risk 1:** [Description] → **Mitigation:** [How to address]
-- **Risk 2:** [Description] → **Mitigation:** [How to address]
+- **Risk 1:** [Description] -> **Mitigation:** [How to address]
+- **Risk 2:** [Description] -> **Mitigation:** [How to address]
 
 ## Further Research Needed
 
-- [Question/area that needs additional investigation]
 - [Question/area that needs additional investigation]
 
 ## Sources
 
 - [Source 1 with URL and access date]
 - [Source 2 with URL and access date]
-- [Continue listing all sources used...]
-
-## Appendix
-
-[Additional detailed information, raw data, extended quotes, etc.]
 ```
 
 ## Tool Integration
@@ -244,70 +184,3 @@ Use the following structure:
 - Research documents stored in `.code-captain/research/`
 - Date-prefixed filenames for chronological organization
 - Cross-references to related project documentation
-
-## Best Practices
-
-### Search Strategy
-
-- Start broad, then narrow down
-- Use multiple search terms and phrasings
-- Look for recent content (last 1-2 years) for rapidly evolving topics
-- Cross-reference information from multiple sources
-- Search for both benefits AND criticisms
-
-### Critical Thinking
-
-- Question assumptions and biases in sources
-- Look for evidence, not just opinions
-- Consider the source's credibility and potential conflicts of interest
-- Distinguish between correlation and causation
-- Identify what information is missing
-
-### Documentation
-
-- Keep track of sources for all claims
-- Note the date of information (especially for fast-moving topics)
-- Document your search process for reproducibility
-- Save important quotes with proper attribution
-
-## Common Pitfalls to Avoid
-
-- Confirmation bias (only seeking information that supports preconceived notions)
-- Stopping research too early when findings seem obvious
-- Not considering implementation challenges
-- Ignoring edge cases or limitations
-- Failing to consider stakeholder perspectives beyond your own
-
-## Example Research Progression
-
-**Initial Phase:**
-
-```
-- Research blockchain solutions for supply chain [in_progress]
-- Analyze implementation approaches [pending]
-- Evaluate vendor options [pending]
-- Create research document in .code-captain/research/ [pending]
-- Create recommendation report [pending]
-```
-
-**After Phase 2:**
-
-```
-- Research blockchain solutions for supply chain [completed]
-- Analyze implementation approaches [in_progress]
-- Evaluate vendor options [pending]
-- Determine date using file system method [pending]
-- Create research document in .code-captain/research/ [pending]
-- Create recommendation report [pending]
-```
-
-**Final:**
-
-```
-- Research blockchain solutions for supply chain [completed]
-- Analyze implementation approaches [completed]
-- Evaluate vendor options [completed]
-- Determine date using file system method [completed]
-- Create research document in .code-captain/research/ [completed]
-- Create recommendation report [completed]
-```