appiq-solution 1.4.8 → 1.5.0

package/#Tools/APPIQ-METHOD/bmad-core/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/#Tools/APPIQ-METHOD/bmad-core/templates/prd-tmpl.yaml

@@ -1,202 +0,0 @@
-template:
-  id: 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: 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: 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:
-      
-      - Each epic should deliver a significant, end-to-end, fully deployable increment of testable functionality
-      - Epic 1 must establish foundational project infrastructure (app setup, Git, CI/CD, core services) unless we are adding new functionality to an existing app, while also delivering an initial piece of functionality, even as simple as a health-check route or display of a simple canary page - remember this when we produce the stories for the first epic!
-      - Each subsequent epic builds upon previous epics' functionality delivering major blocks of functionality that provide tangible value to users or business when deployed
-      - 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 & Core Infrastructure: Establish project setup, authentication, and basic user management"
-      - "Epic 2: Core Business Entities: Create and manage primary domain objects with CRUD operations"
-      - "Epic 3: User Workflows & Interactions: Enable key user journeys and business processes"
-      - "Epic 4: Reporting & Analytics: Provide insights and data visualization for users"
-
-  - 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/#Tools/APPIQ-METHOD/bmad-core/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.