vibefast-cli 0.2.3 → 0.3.0

package/2/vf-agent/templates/brownfield-prd-tmpl.yaml

@@ -0,0 +1,247 @@
+template:
+  id: brownfield-prd-template-v2
+  name: Product Requirements Document
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/prd.md
+    title: '{{project_name}} Product Requirements Document (PRD)'
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+
+sections:
+  - id: goals-context
+    title: Goals and Background Context
+    instruction: |
+      Ask if Project Brief document is available. If NO Project Brief exists, STRONGLY recommend creating one first using project-brief-tmpl (it provides essential foundation: problem statement, target users, success metrics, MVP scope, constraints). If user insists on PRD without brief, gather this information during Goals section. If Project Brief exists, review and use it to populate Goals (bullet list of desired outcomes) and Background Context (1-2 paragraphs on what this solves and why) so we can determine what is and is not in scope for PRD mvp. Either way this is critical to determine the requirements. Include Change Log table.
+    sections:
+      - id: goals
+        title: Goals
+        type: bullet-list
+        instruction: Bullet list of 1 line desired outcomes the PRD will deliver if successful - user and project desires
+      - id: background
+        title: Background Context
+        type: paragraphs
+        instruction: 1-2 short paragraphs summarizing the background context, such as what we learned in the brief without being redundant with the goals, what and why this solves a problem, what the current landscape or need is
+      - id: changelog
+        title: Change Log
+        type: table
+        columns: [Date, Version, Description, Author]
+        instruction: Track document versions and changes
+
+ - id: existing-feature-integration
+    title: Existing Feature Integration
+    instruction: |
+      CRITICAL: Before defining new requirements, you must first analyze the VibeFast starter kit's built-in features. Consult `starter-docs/feature-reference-index.md`. In this section, create a list of all existing features (e.g., Authentication, Payments, AI Chatbot) that will be used, configured, or leveraged to meet the goals of this PRD. This prevents re-planning work that is already done.
+    elicit: true
+    type: bullet-list
+    template: "- **{{feature_name}}:** {{how_it_will_be_used}}"
+
+  - id: requirements
+    title: Requirements
+    instruction: Draft the list of functional and non functional requirements under the two child sections
+    elicit: true
+    sections:
+      - id: functional
+        title: Functional
+        type: numbered-list
+        prefix: FR
+        instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with FR
+        examples:
+          - 'FR6: The Todo List uses AI to detect and warn against potentially duplicate todo items that are worded differently.'
+      - id: non-functional
+        title: Non Functional
+        type: numbered-list
+        prefix: NFR
+        instruction: Each Requirement will be a bullet markdown and an identifier sequence starting with NFR
+        examples:
+          - 'NFR1: AWS service usage must aim to stay within free-tier limits where feasible.'
+
+  - id: ui-goals
+    title: User Interface Design Goals
+    condition: PRD has UX/UI requirements
+    instruction: |
+      Capture high-level UI/UX vision to guide Design Architect and to inform story creation. Steps:
+
+      1. Pre-fill all subsections with educated guesses based on project context
+      2. Present the complete rendered section to user
+      3. Clearly let the user know where assumptions were made
+      4. Ask targeted questions for unclear/missing elements or areas needing more specification
+      5. This is NOT detailed UI spec - focus on product vision and user goals
+    elicit: true
+    choices:
+      accessibility: [None, WCAG AA, WCAG AAA]
+      platforms: [Web Responsive, Mobile Only, Desktop Only, Cross-Platform]
+    sections:
+      - id: ux-vision
+        title: Overall UX Vision
+      - id: interaction-paradigms
+        title: Key Interaction Paradigms
+      - id: core-screens
+        title: Core Screens and Views
+        instruction: From a product perspective, what are the most critical screens or views necessary to deliver the the PRD values and goals? This is meant to be Conceptual High Level to Drive Rough Epic or User Stories
+        examples:
+          - 'Login Screen'
+          - 'Main Dashboard'
+          - 'Item Detail Page'
+          - 'Settings Page'
+      - id: accessibility
+        title: 'Accessibility: {None|WCAG AA|WCAG AAA|Custom Requirements}'
+      - id: branding
+        title: Branding
+        instruction: Any known branding elements or style guides that must be incorporated?
+        examples:
+          - 'Replicate the look and feel of early 1900s black and white cinema, including animated effects replicating film damage or projector glitches during page or state transitions.'
+          - 'Attached is the full color pallet and tokens for our corporate branding.'
+      - id: target-platforms
+        title: 'Target Device and Platforms: {Web Responsive|Mobile Only|Desktop Only|Cross-Platform}'
+        examples:
+          - 'Web Responsive, and all mobile platforms'
+          - 'iPhone Only'
+          - 'ASCII Windows Desktop'
+
+  - id: technical-assumptions
+    title: Technical Assumptions
+    instruction: |
+      Gather technical decisions that will guide the Architect. Steps:
+
+      1. Check if {root}/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
+      3. For unknowns, offer guidance based on project goals and MVP scope
+      4. Document ALL technical choices with rationale (why this choice fits the project)
+      5. These become constraints for the Architect - be specific and complete
+    elicit: true
+    choices:
+      repository: [Monorepo, Polyrepo]
+      architecture: [Monolith, Microservices, Serverless]
+      testing: [Unit Only, Unit + Integration, Full Testing Pyramid]
+    sections:
+      - id: repository-structure
+        title: 'Repository Structure: {Monorepo|Polyrepo|Multi-repo}'
+      - id: service-architecture
+        title: Service Architecture
+        instruction: 'CRITICAL DECISION - Document the high-level service architecture (e.g., Monolith, Microservices, Serverless functions within a Monorepo).'
+      - id: testing-requirements
+        title: Testing Requirements
+        instruction: 'CRITICAL DECISION - Document the testing requirements, unit only, integration, e2e, manual, need for manual testing convenience methods).'
+      - id: additional-assumptions
+        title: Additional Technical Assumptions and Requests
+        instruction: Throughout the entire process of drafting this document, if any other technical assumptions are raised or discovered appropriate for the architect, add them here as additional bulleted items
+
+  - id: core-app-structure
+    title: Core Application Structure
+    instruction: |
+      CRITICAL FOR SCAFFOLDING: Define the foundational structure of your new application. This will be used to automatically clean up the starter kit and set up your project.
+      1.  **Primary Navigation Tabs:** List the main tabs for your app's bottom navigation bar.
+      2.  **Core Features:** List the names of the main new features you will be building. These will become the top-level folders in `src/features/`.
+      3.  **Starter Features to Keep:** List any of the VibeFast demo features (e.g., "Chatbot", "Image Generator") that you want to KEEP in your final application. Any feature not listed here will be deleted.
+    elicit: true
+    sections:
+      - id: primary-navigation
+        title: Primary Navigation Tabs
+        type: numbered-list
+        instruction: List the primary tabs for the bottom navigator (e.g., "Dashboard", "Log Food", "Profile").
+        examples:
+          - 'Dashboard'
+          - 'Log Food'
+          - 'History'
+          - 'Profile'
+      - id: core-features
+        title: Core App Features
+        type: numbered-list
+        instruction: List the main feature domains of your new app (e.g., "food-logging", "user-dashboard", "recipe-browser").
+        examples:
+          - 'dashboard'
+          - 'food-logging'
+          - 'user-profile'
+          - 'recipe-browser'
+      - id: starter-features-to-keep
+        title: Starter Features to Keep
+        type: numbered-list
+        instruction: List ONLY the VibeFast demo features you want to keep (e.g., "Chatbot"). If none, leave blank.
+        examples:
+          - 'Chatbot'
+          - 'Image Analyzer'
+
+  - id: epic-list
+    title: Epic List
+    instruction: |
+      Present a high-level list of all epics for user approval. Each epic should have a title and a short (1 sentence) goal statement. This allows the user to review the overall structure before diving into details.
+
+      CRITICAL: Epics MUST be logically sequential following agile best practices:
+
+      - **Epic 1 (Foundation & Application Transformation):** This first epic is non-negotiable. It MUST include stories to:
+        1. Establish foundational project infrastructure (CI/CD, etc.).
+        2. **Decommission and remove the starter kit's demo home screen.**
+        3. **Create the new, application-specific home screen** that provides immediate value to the end-user (e.g., a dashboard, a primary call-to-action).
+        4. Implement the core authentication flow for the new app.
+      - Each subsequent epic builds upon this new foundation...
+      - Not every project needs multiple epics, an epic needs to deliver value. For example, an API completed can deliver value even if a UI is not complete and planned for a separate epic.
+      - Err on the side of less epics, but let the user know your rationale and offer options for splitting them if it seems some are too large or focused on disparate things.
+      - Cross Cutting Concerns should flow through epics and stories and not be final stories. For example, adding a logging framework as a last story of an epic, or at the end of a project as a final epic or story would be terrible as we would not have logging from the beginning.
+    elicit: true
+    examples:
+      - 'Epic 1: Foundation & App Rebranding: Establish project setup, replace demo home screen, and implement basic user authentication.'
+      - 'Epic 2: Core Feature - [Feature Name]: Implement the primary business logic and UI for the core feature.'
+      - 'Epic 3: User Workflows & Interactions: Enable key user journeys and business processes.'
+
+  - id: epic-details
+    title: Epic {{epic_number}} {{epic_title}}
+    repeatable: true
+    instruction: |
+      After the epic list is approved, present each epic with all its stories and acceptance criteria as a complete review unit.
+
+      For each epic provide expanded goal (2-3 sentences describing the objective and value all the stories will achieve).
+
+      CRITICAL STORY SEQUENCING REQUIREMENTS:
+
+      - Stories within each epic MUST be logically sequential
+      - Each story should be a "vertical slice" delivering complete functionality aside from early enabler stories for project foundation
+      - No story should depend on work from a later story or epic
+      - Identify and note any direct prerequisite stories
+      - Focus on "what" and "why" not "how" (leave technical implementation to Architect) yet be precise enough to support a logical sequential order of operations from story to story.
+      - Ensure each story delivers clear user or business value, try to avoid enablers and build them into stories that deliver value.
+      - Size stories for AI agent execution: Each story must be completable by a single AI agent in one focused session without context overflow
+      - Think "junior developer working for 2-4 hours" - stories must be small, focused, and self-contained
+      - If a story seems complex, break it down further as long as it can deliver a vertical slice
+    elicit: true
+    template: '{{epic_goal}}'
+    sections:
+      - id: story
+        title: Story {{epic_number}}.{{story_number}} {{story_title}}
+        repeatable: true
+        template: |
+          As a {{user_type}},
+          I want {{action}},
+          so that {{benefit}}.
+        sections:
+          - id: acceptance-criteria
+            title: Acceptance Criteria
+            type: numbered-list
+            item_template: '{{criterion_number}}: {{criteria}}'
+            repeatable: true
+            instruction: |
+              Define clear, comprehensive, and testable acceptance criteria that:
+
+              - Precisely define what "done" means from a functional perspective
+              - Are unambiguous and serve as basis for verification
+              - Include any critical non-functional requirements from the PRD
+              - Consider local testability for backend/data components
+              - Specify UI/UX requirements and framework adherence where applicable
+              - Avoid cross-cutting concerns that should be in other stories or PRD sections
+
+  - id: checklist-results
+    title: Checklist Results Report
+    instruction: Before running the checklist and drafting the prompts, offer to output the full updated PRD. If outputting it, confirm with the user that you will be proceeding to run the checklist and produce the report. Once the user confirms, execute the pm-checklist and populate the results in this section.
+
+  - id: next-steps
+    title: Next Steps
+    sections:
+      - id: ux-expert-prompt
+        title: UX Expert Prompt
+        instruction: This section will contain the prompt for the UX Expert, keep it short and to the point to initiate create architecture mode using this document as input.
+      - id: architect-prompt
+        title: Architect Prompt
+        instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.

package/2/vf-agent/templates/competitor-analysis-tmpl.yaml

@@ -0,0 +1,293 @@
+template:
+  id: competitor-analysis-template-v2
+  name: Competitive Analysis Report
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/competitor-analysis.md
+    title: "Competitive Analysis Report: {{project_product_name}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Competitive Analysis Elicitation Actions"
+    options:
+      - "Deep dive on a specific competitor's strategy"
+      - "Analyze competitive dynamics in a specific segment"
+      - "War game competitive responses to your moves"
+      - "Explore partnership vs. competition scenarios"
+      - "Stress test differentiation claims"
+      - "Analyze disruption potential (yours or theirs)"
+      - "Compare to competition in adjacent markets"
+      - "Generate win/loss analysis insights"
+      - "If only we had known about [competitor X's plan]..."
+      - "Proceed to next section"
+
+sections:
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide high-level competitive insights, main threats and opportunities, and recommended strategic actions. Write this section LAST after completing all analysis.
+
+  - id: analysis-scope
+    title: Analysis Scope & Methodology
+    instruction: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.
+    sections:
+      - id: analysis-purpose
+        title: Analysis Purpose
+        instruction: |
+          Define the primary purpose:
+          - New market entry assessment
+          - Product positioning strategy
+          - Feature gap analysis
+          - Pricing strategy development
+          - Partnership/acquisition targets
+          - Competitive threat assessment
+      - id: competitor-categories
+        title: Competitor Categories Analyzed
+        instruction: |
+          List categories included:
+          - Direct Competitors: Same product/service, same target market
+          - Indirect Competitors: Different product, same need/problem
+          - Potential Competitors: Could enter market easily
+          - Substitute Products: Alternative solutions
+          - Aspirational Competitors: Best-in-class examples
+      - id: research-methodology
+        title: Research Methodology
+        instruction: |
+          Describe approach:
+          - Information sources used
+          - Analysis timeframe
+          - Confidence levels
+          - Limitations
+
+  - id: competitive-landscape
+    title: Competitive Landscape Overview
+    sections:
+      - id: market-structure
+        title: Market Structure
+        instruction: |
+          Describe the competitive environment:
+          - Number of active competitors
+          - Market concentration (fragmented/consolidated)
+          - Competitive dynamics
+          - Recent market entries/exits
+      - id: prioritization-matrix
+        title: Competitor Prioritization Matrix
+        instruction: |
+          Help categorize competitors by market share and strategic threat level
+          
+          Create a 2x2 matrix:
+          - Priority 1 (Core Competitors): High Market Share + High Threat
+          - Priority 2 (Emerging Threats): Low Market Share + High Threat
+          - Priority 3 (Established Players): High Market Share + Low Threat
+          - Priority 4 (Monitor Only): Low Market Share + Low Threat
+
+  - id: competitor-profiles
+    title: Individual Competitor Profiles
+    instruction: Create detailed profiles for each Priority 1 and Priority 2 competitor. For Priority 3 and 4, create condensed profiles.
+    repeatable: true
+    sections:
+      - id: competitor
+        title: "{{competitor_name}} - Priority {{priority_level}}"
+        sections:
+          - id: company-overview
+            title: Company Overview
+            template: |
+              - **Founded:** {{year_founders}}
+              - **Headquarters:** {{location}}
+              - **Company Size:** {{employees_revenue}}
+              - **Funding:** {{total_raised_investors}}
+              - **Leadership:** {{key_executives}}
+          - id: business-model
+            title: Business Model & Strategy
+            template: |
+              - **Revenue Model:** {{revenue_model}}
+              - **Target Market:** {{customer_segments}}
+              - **Value Proposition:** {{value_promise}}
+              - **Go-to-Market Strategy:** {{gtm_approach}}
+              - **Strategic Focus:** {{current_priorities}}
+          - id: product-analysis
+            title: Product/Service Analysis
+            template: |
+              - **Core Offerings:** {{main_products}}
+              - **Key Features:** {{standout_capabilities}}
+              - **User Experience:** {{ux_assessment}}
+              - **Technology Stack:** {{tech_stack}}
+              - **Pricing:** {{pricing_model}}
+          - id: strengths-weaknesses
+            title: Strengths & Weaknesses
+            sections:
+              - id: strengths
+                title: Strengths
+                type: bullet-list
+                template: "- {{strength}}"
+              - id: weaknesses
+                title: Weaknesses
+                type: bullet-list
+                template: "- {{weakness}}"
+          - id: market-position
+            title: Market Position & Performance
+            template: |
+              - **Market Share:** {{market_share_estimate}}
+              - **Customer Base:** {{customer_size_notables}}
+              - **Growth Trajectory:** {{growth_trend}}
+              - **Recent Developments:** {{key_news}}
+
+  - id: comparative-analysis
+    title: Comparative Analysis
+    sections:
+      - id: feature-comparison
+        title: Feature Comparison Matrix
+        instruction: Create a detailed comparison table of key features across competitors
+        type: table
+        columns: ["Feature Category", "{{your_company}}", "{{competitor_1}}", "{{competitor_2}}", "{{competitor_3}}"]
+        rows:
+          - category: "Core Functionality"
+            items:
+              - ["Feature A", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
+              - ["Feature B", "{{status}}", "{{status}}", "{{status}}", "{{status}}"]
+          - category: "User Experience"
+            items:
+              - ["Mobile App", "{{rating}}", "{{rating}}", "{{rating}}", "{{rating}}"]
+              - ["Onboarding Time", "{{time}}", "{{time}}", "{{time}}", "{{time}}"]
+          - category: "Integration & Ecosystem"
+            items:
+              - ["API Availability", "{{availability}}", "{{availability}}", "{{availability}}", "{{availability}}"]
+              - ["Third-party Integrations", "{{number}}", "{{number}}", "{{number}}", "{{number}}"]
+          - category: "Pricing & Plans"
+            items:
+              - ["Starting Price", "{{price}}", "{{price}}", "{{price}}", "{{price}}"]
+              - ["Free Tier", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}", "{{yes_no}}"]
+      - id: swot-comparison
+        title: SWOT Comparison
+        instruction: Create SWOT analysis for your solution vs. top competitors
+        sections:
+          - id: your-solution
+            title: Your Solution
+            template: |
+              - **Strengths:** {{strengths}}
+              - **Weaknesses:** {{weaknesses}}
+              - **Opportunities:** {{opportunities}}
+              - **Threats:** {{threats}}
+          - id: vs-competitor
+            title: "vs. {{main_competitor}}"
+            template: |
+              - **Competitive Advantages:** {{your_advantages}}
+              - **Competitive Disadvantages:** {{their_advantages}}
+              - **Differentiation Opportunities:** {{differentiation}}
+      - id: positioning-map
+        title: Positioning Map
+        instruction: |
+          Describe competitor positions on key dimensions
+          
+          Create a positioning description using 2 key dimensions relevant to the market, such as:
+          - Price vs. Features
+          - Ease of Use vs. Power
+          - Specialization vs. Breadth
+          - Self-Serve vs. High-Touch
+
+  - id: strategic-analysis
+    title: Strategic Analysis
+    sections:
+      - id: competitive-advantages
+        title: Competitive Advantages Assessment
+        sections:
+          - id: sustainable-advantages
+            title: Sustainable Advantages
+            instruction: |
+              Identify moats and defensible positions:
+              - Network effects
+              - Switching costs
+              - Brand strength
+              - Technology barriers
+              - Regulatory advantages
+          - id: vulnerable-points
+            title: Vulnerable Points
+            instruction: |
+              Where competitors could be challenged:
+              - Weak customer segments
+              - Missing features
+              - Poor user experience
+              - High prices
+              - Limited geographic presence
+      - id: blue-ocean
+        title: Blue Ocean Opportunities
+        instruction: |
+          Identify uncontested market spaces
+          
+          List opportunities to create new market space:
+          - Underserved segments
+          - Unaddressed use cases
+          - New business models
+          - Geographic expansion
+          - Different value propositions
+
+  - id: strategic-recommendations
+    title: Strategic Recommendations
+    sections:
+      - id: differentiation-strategy
+        title: Differentiation Strategy
+        instruction: |
+          How to position against competitors:
+          - Unique value propositions to emphasize
+          - Features to prioritize
+          - Segments to target
+          - Messaging and positioning
+      - id: competitive-response
+        title: Competitive Response Planning
+        sections:
+          - id: offensive-strategies
+            title: Offensive Strategies
+            instruction: |
+              How to gain market share:
+              - Target competitor weaknesses
+              - Win competitive deals
+              - Capture their customers
+          - id: defensive-strategies
+            title: Defensive Strategies
+            instruction: |
+              How to protect your position:
+              - Strengthen vulnerable areas
+              - Build switching costs
+              - Deepen customer relationships
+      - id: partnership-ecosystem
+        title: Partnership & Ecosystem Strategy
+        instruction: |
+          Potential collaboration opportunities:
+          - Complementary players
+          - Channel partners
+          - Technology integrations
+          - Strategic alliances
+
+  - id: monitoring-plan
+    title: Monitoring & Intelligence Plan
+    sections:
+      - id: key-competitors
+        title: Key Competitors to Track
+        instruction: Priority list with rationale
+      - id: monitoring-metrics
+        title: Monitoring Metrics
+        instruction: |
+          What to track:
+          - Product updates
+          - Pricing changes
+          - Customer wins/losses
+          - Funding/M&A activity
+          - Market messaging
+      - id: intelligence-sources
+        title: Intelligence Sources
+        instruction: |
+          Where to gather ongoing intelligence:
+          - Company websites/blogs
+          - Customer reviews
+          - Industry reports
+          - Social media
+          - Patent filings
+      - id: update-cadence
+        title: Update Cadence
+        instruction: |
+          Recommended review schedule:
+          - Weekly: {{weekly_items}}
+          - Monthly: {{monthly_items}}
+          - Quarterly: {{quarterly_analysis}}