vibefast-cli 0.6.2 → 0.7.1

package/2/vf-agent/templates/market-research-tmpl.yaml

@@ -1,252 +0,0 @@
-template:
-  id: market-research-template-v2
-  name: Market Research Report
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/market-research.md
-    title: "Market Research Report: {{project_product_name}}"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-  custom_elicitation:
-    title: "Market Research Elicitation Actions"
-    options:
-      - "Expand market sizing calculations with sensitivity analysis"
-      - "Deep dive into a specific customer segment"
-      - "Analyze an emerging market trend in detail"
-      - "Compare this market to an analogous market"
-      - "Stress test market assumptions"
-      - "Explore adjacent market opportunities"
-      - "Challenge market definition and boundaries"
-      - "Generate strategic scenarios (best/base/worst case)"
-      - "If only we had considered [X market factor]..."
-      - "Proceed to next section"
-
-sections:
-  - id: executive-summary
-    title: Executive Summary
-    instruction: Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.
-
-  - id: research-objectives
-    title: Research Objectives & Methodology
-    instruction: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.
-    sections:
-      - id: objectives
-        title: Research Objectives
-        instruction: |
-          List the primary objectives of this market research:
-          - What decisions will this research inform?
-          - What specific questions need to be answered?
-          - What are the success criteria for this research?
-      - id: methodology
-        title: Research Methodology
-        instruction: |
-          Describe the research approach:
-          - Data sources used (primary/secondary)
-          - Analysis frameworks applied
-          - Data collection timeframe
-          - Limitations and assumptions
-
-  - id: market-overview
-    title: Market Overview
-    sections:
-      - id: market-definition
-        title: Market Definition
-        instruction: |
-          Define the market being analyzed:
-          - Product/service category
-          - Geographic scope
-          - Customer segments included
-          - Value chain position
-      - id: market-size-growth
-        title: Market Size & Growth
-        instruction: |
-          Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
-          - Top-down: Start with industry data, narrow down
-          - Bottom-up: Build from customer/unit economics
-          - Value theory: Based on value provided vs. alternatives
-        sections:
-          - id: tam
-            title: Total Addressable Market (TAM)
-            instruction: Calculate and explain the total market opportunity
-          - id: sam
-            title: Serviceable Addressable Market (SAM)
-            instruction: Define the portion of TAM you can realistically reach
-          - id: som
-            title: Serviceable Obtainable Market (SOM)
-            instruction: Estimate the portion you can realistically capture
-      - id: market-trends
-        title: Market Trends & Drivers
-        instruction: Analyze key trends shaping the market using appropriate frameworks like PESTEL
-        sections:
-          - id: key-trends
-            title: Key Market Trends
-            instruction: |
-              List and explain 3-5 major trends:
-              - Trend 1: Description and impact
-              - Trend 2: Description and impact
-              - etc.
-          - id: growth-drivers
-            title: Growth Drivers
-            instruction: Identify primary factors driving market growth
-          - id: market-inhibitors
-            title: Market Inhibitors
-            instruction: Identify factors constraining market growth
-
-  - id: customer-analysis
-    title: Customer Analysis
-    sections:
-      - id: segment-profiles
-        title: Target Segment Profiles
-        instruction: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay
-        repeatable: true
-        sections:
-          - id: segment
-            title: "Segment {{segment_number}}: {{segment_name}}"
-            template: |
-              - **Description:** {{brief_overview}}
-              - **Size:** {{number_of_customers_market_value}}
-              - **Characteristics:** {{key_demographics_firmographics}}
-              - **Needs & Pain Points:** {{primary_problems}}
-              - **Buying Process:** {{purchasing_decisions}}
-              - **Willingness to Pay:** {{price_sensitivity}}
-      - id: jobs-to-be-done
-        title: Jobs-to-be-Done Analysis
-        instruction: Uncover what customers are really trying to accomplish
-        sections:
-          - id: functional-jobs
-            title: Functional Jobs
-            instruction: List practical tasks and objectives customers need to complete
-          - id: emotional-jobs
-            title: Emotional Jobs
-            instruction: Describe feelings and perceptions customers seek
-          - id: social-jobs
-            title: Social Jobs
-            instruction: Explain how customers want to be perceived by others
-      - id: customer-journey
-        title: Customer Journey Mapping
-        instruction: Map the end-to-end customer experience for primary segments
-        template: |
-          For primary customer segment:
-          
-          1. **Awareness:** {{discovery_process}}
-          2. **Consideration:** {{evaluation_criteria}}
-          3. **Purchase:** {{decision_triggers}}
-          4. **Onboarding:** {{initial_expectations}}
-          5. **Usage:** {{interaction_patterns}}
-          6. **Advocacy:** {{referral_behaviors}}
-
-  - id: competitive-landscape
-    title: Competitive Landscape
-    sections:
-      - id: market-structure
-        title: Market Structure
-        instruction: |
-          Describe the overall competitive environment:
-          - Number of competitors
-          - Market concentration
-          - Competitive intensity
-      - id: major-players
-        title: Major Players Analysis
-        instruction: |
-          For top 3-5 competitors:
-          - Company name and brief description
-          - Market share estimate
-          - Key strengths and weaknesses
-          - Target customer focus
-          - Pricing strategy
-      - id: competitive-positioning
-        title: Competitive Positioning
-        instruction: |
-          Analyze how competitors are positioned:
-          - Value propositions
-          - Differentiation strategies
-          - Market gaps and opportunities
-
-  - id: industry-analysis
-    title: Industry Analysis
-    sections:
-      - id: porters-five-forces
-        title: Porter's Five Forces Assessment
-        instruction: Analyze each force with specific evidence and implications
-        sections:
-          - id: supplier-power
-            title: "Supplier Power: {{power_level}}"
-            template: "{{analysis_and_implications}}"
-          - id: buyer-power
-            title: "Buyer Power: {{power_level}}"
-            template: "{{analysis_and_implications}}"
-          - id: competitive-rivalry
-            title: "Competitive Rivalry: {{intensity_level}}"
-            template: "{{analysis_and_implications}}"
-          - id: threat-new-entry
-            title: "Threat of New Entry: {{threat_level}}"
-            template: "{{analysis_and_implications}}"
-          - id: threat-substitutes
-            title: "Threat of Substitutes: {{threat_level}}"
-            template: "{{analysis_and_implications}}"
-      - id: adoption-lifecycle
-        title: Technology Adoption Lifecycle Stage
-        instruction: |
-          Identify where the market is in the adoption curve:
-          - Current stage and evidence
-          - Implications for strategy
-          - Expected progression timeline
-
-  - id: opportunity-assessment
-    title: Opportunity Assessment
-    sections:
-      - id: market-opportunities
-        title: Market Opportunities
-        instruction: Identify specific opportunities based on the analysis
-        repeatable: true
-        sections:
-          - id: opportunity
-            title: "Opportunity {{opportunity_number}}: {{name}}"
-            template: |
-              - **Description:** {{what_is_the_opportunity}}
-              - **Size/Potential:** {{quantified_potential}}
-              - **Requirements:** {{needed_to_capture}}
-              - **Risks:** {{key_challenges}}
-      - id: strategic-recommendations
-        title: Strategic Recommendations
-        sections:
-          - id: go-to-market
-            title: Go-to-Market Strategy
-            instruction: |
-              Recommend approach for market entry/expansion:
-              - Target segment prioritization
-              - Positioning strategy
-              - Channel strategy
-              - Partnership opportunities
-          - id: pricing-strategy
-            title: Pricing Strategy
-            instruction: |
-              Based on willingness to pay analysis and competitive landscape:
-              - Recommended pricing model
-              - Price points/ranges
-              - Value metric
-              - Competitive positioning
-          - id: risk-mitigation
-            title: Risk Mitigation
-            instruction: |
-              Key risks and mitigation strategies:
-              - Market risks
-              - Competitive risks
-              - Execution risks
-              - Regulatory/compliance risks
-
-  - id: appendices
-    title: Appendices
-    sections:
-      - id: data-sources
-        title: A. Data Sources
-        instruction: List all sources used in the research
-      - id: calculations
-        title: B. Detailed Calculations
-        instruction: Include any complex calculations or models
-      - id: additional-analysis
-        title: C. Additional Analysis
-        instruction: Any supplementary analysis not included in main body

package/2/vf-agent/templates/project-brief-tmpl.yaml

@@ -1,221 +0,0 @@
-template:
-  id: project-brief-template-v2
-  name: Project Brief
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/brief.md
-    title: "Project Brief: {{project_name}}"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-  custom_elicitation:
-    title: "Project Brief Elicitation Actions"
-    options:
-      - "Expand section with more specific details"
-      - "Validate against similar successful products"
-      - "Stress test assumptions with edge cases"
-      - "Explore alternative solution approaches"
-      - "Analyze resource/constraint trade-offs"
-      - "Generate risk mitigation strategies"
-      - "Challenge scope from MVP minimalist view"
-      - "Brainstorm creative feature possibilities"
-      - "If only we had [resource/capability/time]..."
-      - "Proceed to next section"
-
-sections:
-  - id: introduction
-    instruction: |
-      This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
-      
-      Start by asking the user which mode they prefer:
-      
-      1. **Interactive Mode** - Work through each section collaboratively
-      2. **YOLO Mode** - Generate complete draft for review and refinement
-      
-      Before beginning, understand what inputs are available (brainstorming results, market research, competitive analysis, initial ideas) and gather project context.
-
-  - id: executive-summary
-    title: Executive Summary
-    instruction: |
-      Create a concise overview that captures the essence of the project. Include:
-      - Product concept in 1-2 sentences
-      - Primary problem being solved
-      - Target market identification
-      - Key value proposition
-    template: "{{executive_summary_content}}"
-
-  - id: problem-statement
-    title: Problem Statement
-    instruction: |
-      Articulate the problem with clarity and evidence. Address:
-      - Current state and pain points
-      - Impact of the problem (quantify if possible)
-      - Why existing solutions fall short
-      - Urgency and importance of solving this now
-    template: "{{detailed_problem_description}}"
-
-  - id: proposed-solution
-    title: Proposed Solution
-    instruction: |
-      Describe the solution approach at a high level. Include:
-      - Core concept and approach
-      - Key differentiators from existing solutions
-      - Why this solution will succeed where others haven't
-      - High-level vision for the product
-    template: "{{solution_description}}"
-
-  - id: target-users
-    title: Target Users
-    instruction: |
-      Define and characterize the intended users with specificity. For each user segment include:
-      - Demographic/firmographic profile
-      - Current behaviors and workflows
-      - Specific needs and pain points
-      - Goals they're trying to achieve
-    sections:
-      - id: primary-segment
-        title: "Primary User Segment: {{segment_name}}"
-        template: "{{primary_user_description}}"
-      - id: secondary-segment
-        title: "Secondary User Segment: {{segment_name}}"
-        condition: Has secondary user segment
-        template: "{{secondary_user_description}}"
-
-  - id: goals-metrics
-    title: Goals & Success Metrics
-    instruction: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
-    sections:
-      - id: business-objectives
-        title: Business Objectives
-        type: bullet-list
-        template: "- {{objective_with_metric}}"
-      - id: user-success-metrics
-        title: User Success Metrics
-        type: bullet-list
-        template: "- {{user_metric}}"
-      - id: kpis
-        title: Key Performance Indicators (KPIs)
-        type: bullet-list
-        template: "- {{kpi}}: {{definition_and_target}}"
-
-  - id: mvp-scope
-    title: MVP Scope
-    instruction: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.
-    sections:
-      - id: core-features
-        title: Core Features (Must Have)
-        type: bullet-list
-        template: "- **{{feature}}:** {{description_and_rationale}}"
-      - id: out-of-scope
-        title: Out of Scope for MVP
-        type: bullet-list
-        template: "- {{feature_or_capability}}"
-      - id: mvp-success-criteria
-        title: MVP Success Criteria
-        template: "{{mvp_success_definition}}"
-
-  - id: post-mvp-vision
-    title: Post-MVP Vision
-    instruction: Outline the longer-term product direction without overcommitting to specifics
-    sections:
-      - id: phase-2-features
-        title: Phase 2 Features
-        template: "{{next_priority_features}}"
-      - id: long-term-vision
-        title: Long-term Vision
-        template: "{{one_two_year_vision}}"
-      - id: expansion-opportunities
-        title: Expansion Opportunities
-        template: "{{potential_expansions}}"
-
-  - id: technical-considerations
-    title: Technical Considerations
-    instruction: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.
-    sections:
-      - id: platform-requirements
-        title: Platform Requirements
-        template: |
-          - **Target Platforms:** {{platforms}}
-          - **Browser/OS Support:** {{specific_requirements}}
-          - **Performance Requirements:** {{performance_specs}}
-      - id: technology-preferences
-        title: Technology Preferences
-        template: |
-          - **Frontend:** {{frontend_preferences}}
-          - **Backend:** {{backend_preferences}}
-          - **Database:** {{database_preferences}}
-          - **Hosting/Infrastructure:** {{infrastructure_preferences}}
-      - id: architecture-considerations
-        title: Architecture Considerations
-        template: |
-          - **Repository Structure:** {{repo_thoughts}}
-          - **Service Architecture:** {{service_thoughts}}
-          - **Integration Requirements:** {{integration_needs}}
-          - **Security/Compliance:** {{security_requirements}}
-
-  - id: constraints-assumptions
-    title: Constraints & Assumptions
-    instruction: Clearly state limitations and assumptions to set realistic expectations
-    sections:
-      - id: constraints
-        title: Constraints
-        template: |
-          - **Budget:** {{budget_info}}
-          - **Timeline:** {{timeline_info}}
-          - **Resources:** {{resource_info}}
-          - **Technical:** {{technical_constraints}}
-      - id: key-assumptions
-        title: Key Assumptions
-        type: bullet-list
-        template: "- {{assumption}}"
-
-  - id: risks-questions
-    title: Risks & Open Questions
-    instruction: Identify unknowns and potential challenges proactively
-    sections:
-      - id: key-risks
-        title: Key Risks
-        type: bullet-list
-        template: "- **{{risk}}:** {{description_and_impact}}"
-      - id: open-questions
-        title: Open Questions
-        type: bullet-list
-        template: "- {{question}}"
-      - id: research-areas
-        title: Areas Needing Further Research
-        type: bullet-list
-        template: "- {{research_topic}}"
-
-  - id: appendices
-    title: Appendices
-    sections:
-      - id: research-summary
-        title: A. Research Summary
-        condition: Has research findings
-        instruction: |
-          If applicable, summarize key findings from:
-          - Market research
-          - Competitive analysis
-          - User interviews
-          - Technical feasibility studies
-      - id: stakeholder-input
-        title: B. Stakeholder Input
-        condition: Has stakeholder feedback
-        template: "{{stakeholder_feedback}}"
-      - id: references
-        title: C. References
-        template: "{{relevant_links_and_docs}}"
-
-  - id: next-steps
-    title: Next Steps
-    sections:
-      - id: immediate-actions
-        title: Immediate Actions
-        type: numbered-list
-        template: "{{action_item}}"
-      - id: pm-handoff
-        title: PM Handoff
-        content: |
-          This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.

package/2/vf-agent/templates/story-tmpl.yaml

@@ -1,143 +0,0 @@
-template:
-  id: story-template-v2
-  name: Story Document
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
-    title: 'Story {{epic_num}}.{{story_num}}: {{story_title_short}}'
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-
-agent_config:
-  editable_sections:
-    - Status
-    - Story Type
-    - Story
-    - Acceptance Criteria
-    - Tasks / Subtasks
-    - Dev Notes
-    - Testing
-    - Change Log
-
-sections:
-  - id: status
-    title: Status
-    type: choice
-    choices: [Draft, Approved, InProgress, Review, Done]
-    instruction: Select the current status of the story
-    owner: scrum-master
-
-  - id: story-type
-    title: Story Type
-    type: choice
-    choices: [Backend (API Contract), Frontend (API Consumer)]
-    instruction: Define if this story is for backend API creation or frontend UI implementation.
-    owner: scrum-master
-
-  - id: story
-    title: Story
-    type: template-text
-    template: |
-      **As a** {{role}},
-      **I want** {{action}},
-      **so that** {{benefit}}
-    instruction: Define the user story using the standard format with role, action, and benefit
-    elicit: true
-    owner: scrum-master
-
-  - id: acceptance-criteria
-    title: Acceptance Criteria
-    type: numbered-list
-    instruction: Copy the acceptance criteria numbered list from the epic file
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-
-  - id: tasks-subtasks
-    title: Tasks / Subtasks
-    type: bullet-list
-    instruction: |
-      Break down the story into specific tasks and subtasks needed for implementation.
-      Reference applicable acceptance criteria numbers where relevant.
-    template: |
-      - [ ] Task 1 (AC: # if applicable)
-        - [ ] Subtask1.1...
-      - [ ] Task 2 (AC: # if applicable)
-        - [ ] Subtask 2.1...
-      - [ ] Task 3 (AC: # if applicable)
-        - [ ] Subtask 3.1...
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master, dev-agent]
-
-  - id: dev-notes
-    title: Dev Notes
-    instruction: |
-      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
-      - Do not invent information
-      - If known add Relevant Source Tree info that relates to this story
-      - If there were important notes from previous story that are relevant to this one, include them here
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-    sections:
-      - id: testing-standards
-        title: Testing
-        instruction: |
-          List Relevant Testing Standards from Architecture the Developer needs to conform to:
-          - Test file location
-          - Test standards
-          - Testing frameworks and patterns to use
-          - Any specific testing requirements for this story
-        elicit: true
-        owner: scrum-master
-        editors: [scrum-master]
-
-  - id: change-log
-    title: Change Log
-    type: table
-    columns: [Date, Version, Description, Author]
-    instruction: Track changes made to this story document
-    owner: scrum-master
-    editors: [scrum-master, dev-agent, qa-agent]
-
-  - id: dev-agent-record
-    title: Dev Agent Record
-    instruction: This section is populated by the development agent during implementation
-    owner: dev-agent
-    editors: [dev-agent]
-    sections:
-      - id: agent-model
-        title: Agent Model Used
-        template: '{{agent_model_name_version}}'
-        instruction: Record the specific AI agent model and version used for development
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: debug-log-references
-        title: Debug Log References
-        instruction: Reference any debug logs or traces generated during development
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: completion-notes
-        title: Completion Notes List
-        instruction: Notes about the completion of tasks and any issues encountered
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: file-list
-        title: File List
-        instruction: List all files created, modified, or affected during story implementation
-        owner: dev-agent
-        editors: [dev-agent]
-
-  - id: qa-results
-    title: QA Results
-    instruction: Results from QA Agent QA review of the completed story implementation
-    owner: qa-agent
-    editors: [qa-agent]