@ngocsangairvds/vsaf 3.2.16 → 4.0.1

package/tools/skills/bmad-help/SKILL.md

@@ -1,75 +0,0 @@
----
-name: bmad-help
-description: 'Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.'
----
-
-# BMad Help
-
-## Purpose
-
-Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
-
-## Desired Outcomes
-
-When this skill completes, the user should:
-
-1. **Know where they are** — which module and phase they're in, what's already been completed
-2. **Know what to do next** — the next recommended and/or required step, with clear reasoning
-3. **Know how to invoke it** — skill name, menu code, action context, and any args that shortcut the conversation
-4. **Get offered a quick start** — when a single skill is the clear next step, offer to run it for the user right now rather than just listing it
-5. **Feel oriented, not overwhelmed** — surface only what's relevant to their current position; don't dump the entire catalog
-6. **Get answers to general questions** — when the question doesn't map to a specific skill, use the module's registered documentation to give a grounded answer
-
-## Data Sources
-
-- **Catalog**: `{project-root}/_bmad/_config/bmad-help.csv` — assembled manifest of all installed module skills
-- **Config**: `config.yaml` and `user-config.yaml` files in `{project-root}/_bmad/` and its subfolders — resolve `output-location` variables, provide `communication_language` and `project_knowledge`
-- **Artifacts**: Files matching `outputs` patterns at resolved `output-location` paths reveal which steps are possibly completed; their content may also provide grounding context for recommendations
-- **Project knowledge**: If `project_knowledge` resolves to an existing path, read it for grounding context. Never fabricate project-specific details.
-- **Module docs**: Rows with `_meta` in the `skill` column carry a URL or path in `output-location` pointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.
-
-## CSV Interpretation
-
-The catalog uses this format:
-
-```
-module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
-```
-
-**Phases** determine the high-level flow:
-- `anytime` — available regardless of workflow state
-- Numbered phases (`1-analysis`, `2-planning`, etc.) flow in order; naming varies by module
-
-**Dependencies** determine ordering within and across phases:
-- `after` — skills that should ideally complete before this one
-- `before` — skills that should run after this one
-- Format: `skill-name` for single-action skills, `skill-name:action` for multi-action skills
-
-**Required gates**:
-- `required=true` items must complete before the user can meaningfully proceed to later phases
-- A phase with no required items is entirely optional — recommend it but be clear about what's actually required next
-
-**Completion detection**:
-- Search resolved output paths for `outputs` patterns
-- Fuzzy-match found files to catalog rows
-- User may also state completion explicitly, or it may be evident from the current conversation
-
-**Descriptions carry routing context** — some contain cycle info and alternate paths (e.g., "back to DS if fixes needed"). Read them as navigation hints, not just display text.
-
-## Response Format
-
-For each recommended item, present:
-- `[menu-code]` **Display name** — e.g., "[CP] Create PRD"
-- Skill name in backticks — e.g., `bmad-create-prd`
-- For multi-action skills: action invocation context — e.g., "tech-writer lets create a mermaid diagram!"
-- Description if present in CSV; otherwise your existing knowledge of the skill suffices
-- Args if available
-
-**Ordering**: Show optional items first, then the next required item. Make it clear which is which.
-
-## Constraints
-
-- Present all output in `{communication_language}`
-- Recommend running each skill in a **fresh context window**
-- Match the user's tone — conversational when they're casual, structured when they want specifics
-- If the active module is ambiguous, retrieve all meta rows remote sources to find relevant info also to help answer their question

package/tools/skills/bmad-index-docs/SKILL.md

@@ -1,66 +0,0 @@
----
-name: bmad-index-docs
-description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
----
-
-# Index Docs
-
-**Goal:** Generate or update an index.md to reference all docs in a target folder.
-
-
-## EXECUTION
-
-### Step 1: Scan Directory
-
-- List all files and subdirectories in the target location
-
-### Step 2: Group Content
-
-- Organize files by type, purpose, or subdirectory
-
-### Step 3: Generate Descriptions
-
-- Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the filename
-
-### Step 4: Create/Update Index
-
-- Write or update index.md with organized file listings
-
-
-## OUTPUT FORMAT
-
-```markdown
-# Directory Index
-
-## Files
-
-- **[filename.ext](./filename.ext)** - Brief description
-- **[another-file.ext](./another-file.ext)** - Brief description
-
-## Subdirectories
-
-### subfolder/
-
-- **[file1.ext](./subfolder/file1.ext)** - Brief description
-- **[file2.ext](./subfolder/file2.ext)** - Brief description
-
-### another-folder/
-
-- **[file3.ext](./another-folder/file3.ext)** - Brief description
-```
-
-
-## HALT CONDITIONS
-
-- HALT if target directory does not exist or is inaccessible
-- HALT if user does not have write permissions to create index.md
-
-
-## VALIDATION
-
-- Use relative paths starting with ./
-- Group similar files together
-- Read file contents to generate accurate descriptions - don't guess from filenames
-- Keep descriptions concise but informative (3-10 words)
-- Sort alphabetically within groups
-- Skip hidden files (starting with .) unless specified

package/tools/skills/bmad-market-research/SKILL.md

@@ -1,6 +0,0 @@
----
-name: bmad-market-research
-description: 'Conduct market research on competition and customers. Use when the user says they need market research'
----
-
-Follow the instructions in ./workflow.md.

package/tools/skills/bmad-market-research/research.template.md

@@ -1,29 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'research'
-lastStep: 1
-research_type: '{{research_type}}'
-research_topic: '{{research_topic}}'
-research_goals: '{{research_goals}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-web_research_enabled: true
-source_verification: true
----
-
-# Research Report: {{research_type}}
-
-**Date:** {{date}}
-**Author:** {{user_name}}
-**Research Type:** {{research_type}}
-
----
-
-## Research Overview
-
-[Research overview and methodology will be appended here]
-
----
-
-<!-- Content will be appended sequentially through research workflow steps -->

package/tools/skills/bmad-market-research/steps/step-01-init.md

@@ -1,184 +0,0 @@
-# Market Research Step 1: Market Research Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate research content in init step
-- ✅ ALWAYS confirm understanding of user's research goals
-- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
-- 💬 FOCUS on clarifying scope and approach
-- 🔍 NO WEB RESEARCH in init - that's for later steps
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Confirm research understanding before proceeding
-- ⚠️ Present [C] continue option after scope clarification
-- 💾 Write initial scope document immediately
-- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from main workflow discovery are available
-- Research type = "market" is already set
-- **Research topic = "{{research_topic}}"** - discovered from initial discussion
-- **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on market research scope clarification
-- Web search capabilities are enabled for later steps
-
-## YOUR TASK:
-
-Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
-
-## MARKET RESEARCH INITIALIZATION:
-
-### 1. Confirm Research Understanding
-
-**INITIALIZE - DO NOT RESEARCH YET**
-
-Start with research confirmation:
-"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
-
-**My Understanding of Your Research Needs:**
-
-- **Research Topic**: {{research_topic}}
-- **Research Goals**: {{research_goals}}
-- **Research Type**: Market Research
-- **Approach**: Comprehensive market analysis with source verification
-
-**Market Research Areas We'll Cover:**
-
-- Market size, growth dynamics, and trends
-- Customer insights and behavior analysis
-- Competitive landscape and positioning
-- Strategic recommendations and implementation guidance
-
-**Does this accurately capture what you're looking for?**"
-
-### 2. Refine Research Scope
-
-Gather any clarifications needed:
-
-#### Scope Clarification Questions:
-
-- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
-- "Should we focus on specific geographic regions or global market?"
-- "Is this for market entry, expansion, product development, or other business purpose?"
-- "Any competitors or market segments you specifically want us to analyze?"
-
-### 3. Document Initial Scope
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Write initial research scope to document:
-
-```markdown
-# Market Research: {{research_topic}}
-
-## Research Initialization
-
-### Research Understanding Confirmed
-
-**Topic**: {{research_topic}}
-**Goals**: {{research_goals}}
-**Research Type**: Market Research
-**Date**: {{date}}
-
-### Research Scope
-
-**Market Analysis Focus Areas:**
-
-- Market size, growth projections, and dynamics
-- Customer segments, behavior patterns, and insights
-- Competitive landscape and positioning analysis
-- Strategic recommendations and implementation guidance
-
-**Research Methodology:**
-
-- Current web data with source verification
-- Multiple independent sources for critical claims
-- Confidence level assessment for uncertain data
-- Comprehensive coverage with no critical gaps
-
-### Next Steps
-
-**Research Workflow:**
-
-1. ✅ Initialization and scope setting (current step)
-2. Customer Insights and Behavior Analysis
-3. Competitive Landscape Analysis
-4. Strategic Synthesis and Recommendations
-
-**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
-```
-
-### 4. Present Confirmation and Continue Option
-
-Show initial scope document and present continue option:
-"I've documented our understanding and initial scope for **{{research_topic}}** market research.
-
-**What I've established:**
-
-- Research topic and goals confirmed
-- Market analysis focus areas defined
-- Research methodology verification
-- Clear workflow progression
-
-**Document Status:** Initial scope written to research file for your review
-
-**Ready to begin detailed market research?**
-[C] Continue - Confirm scope and proceed to customer insights analysis
-[Modify] Suggest changes to research scope before proceeding
-
-**HALT — wait for user response before proceeding.**
-
-### 5. Handle User Response
-
-#### If 'C' (Continue):
-
-- Update frontmatter: `stepsCompleted: [1]`
-- Add confirmation note to document: "Scope confirmed by user on {{date}}"
-- Load: `./step-02-customer-behavior.md`
-
-#### If 'Modify':
-
-- Gather user changes to scope
-- Update document with modifications
-- Re-present updated scope for confirmation
-
-## SUCCESS METRICS:
-
-✅ Research topic and goals accurately understood
-✅ Market research scope clearly defined
-✅ Initial scope document written immediately
-✅ User opportunity to review and modify scope
-✅ [C] continue option presented and handled correctly
-✅ Document properly updated with scope confirmation
-
-## FAILURE MODES:
-
-❌ Not confirming understanding of research topic and goals
-❌ Generating research content instead of just scope clarification
-❌ Not writing initial scope document to file
-❌ Not providing opportunity for user to modify scope
-❌ Proceeding to next step without user confirmation
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## INITIALIZATION PRINCIPLES:
-
-This step ensures:
-
-- Clear mutual understanding of research objectives
-- Well-defined research scope and approach
-- Immediate documentation for user review
-- User control over research direction before detailed work begins
-
-## NEXT STEP:
-
-After user confirmation and scope finalization, load `./step-02-customer-behavior.md` to begin detailed market research with customer insights analysis.
-
-Remember: Init steps confirm understanding and scope, not generate research content!

package/tools/skills/bmad-market-research/steps/step-02-customer-behavior.md

@@ -1,239 +0,0 @@
-# Market Research Step 2: Customer Behavior and Segments
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without web search verification
-- ✅ Search the web to verify and supplement your knowledge with current facts
-- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
-- 💬 FOCUS on customer behavior patterns and demographic analysis
-- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
-- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after customer behavior content generation
-- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
-- 💾 ONLY proceed when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Current document and frontmatter from step-01 are available
-- Focus on customer behavior patterns and demographic analysis
-- Web search capabilities with source verification are enabled
-- Previous step confirmed research scope and goals
-- **Research topic = "{{research_topic}}"** - established from initial discussion
-- **Research goals = "{{research_goals}}"** - established from initial discussion
-
-## YOUR TASK:
-
-Conduct customer behavior and segment analysis with emphasis on patterns and demographics.
-
-## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
-
-### 1. Begin Customer Behavior Analysis
-
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
-
-Start with customer behavior research approach:
-"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
-
-**Customer Behavior Focus:**
-
-- Customer behavior patterns and preferences
-- Demographic profiles and segmentation
-- Psychographic characteristics and values
-- Behavior drivers and influences
-- Customer interaction patterns and engagement
-
-**Let me search for current customer behavior insights.**"
-
-### 2. Parallel Customer Behavior Research Execution
-
-**Execute multiple web searches simultaneously:**
-
-Search the web: "{{research_topic}} customer behavior patterns"
-Search the web: "{{research_topic}} customer demographics"
-Search the web: "{{research_topic}} psychographic profiles"
-Search the web: "{{research_topic}} customer behavior drivers"
-
-**Analysis approach:**
-
-- Look for customer behavior studies and research reports
-- Search for demographic segmentation and analysis
-- Research psychographic profiling and value systems
-- Analyze behavior drivers and influencing factors
-- Study customer interaction and engagement patterns
-
-### 3. Analyze and Aggregate Results
-
-**Collect and analyze findings from all parallel searches:**
-
-"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
-
-**Research Coverage:**
-
-- Customer behavior patterns and preferences
-- Demographic profiles and segmentation
-- Psychographic characteristics and values
-- Behavior drivers and influences
-- Customer interaction patterns and engagement
-
-**Cross-Behavior Analysis:**
-[Identify patterns connecting demographics, psychographics, and behaviors]
-
-**Quality Assessment:**
-[Overall confidence levels and research gaps identified]"
-
-### 4. Generate Customer Behavior Content
-
-**WRITE IMMEDIATELY TO DOCUMENT**
-
-Prepare customer behavior analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Customer Behavior and Segments
-
-### Customer Behavior Patterns
-
-[Customer behavior patterns analysis with source citations]
-_Behavior Drivers: [Key motivations and patterns from web search]_
-_Interaction Preferences: [Customer engagement and interaction patterns]_
-_Decision Habits: [How customers typically make decisions]_
-_Source: [URL]_
-
-### Demographic Segmentation
-
-[Demographic analysis with source citations]
-_Age Demographics: [Age groups and preferences]_
-_Income Levels: [Income segments and purchasing behavior]_
-_Geographic Distribution: [Regional/city differences]_
-_Education Levels: [Education impact on behavior]_
-_Source: [URL]_
-
-### Psychographic Profiles
-
-[Psychographic analysis with source citations]
-_Values and Beliefs: [Core values driving customer behavior]_
-_Lifestyle Preferences: [Lifestyle choices and behaviors]_
-_Attitudes and Opinions: [Customer attitudes toward products/services]_
-_Personality Traits: [Personality influences on behavior]_
-_Source: [URL]_
-
-### Customer Segment Profiles
-
-[Detailed customer segment profiles with source citations]
-_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
-_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
-_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
-_Source: [URL]_
-
-### Behavior Drivers and Influences
-
-[Behavior drivers analysis with source citations]
-_Emotional Drivers: [Emotional factors influencing behavior]_
-_Rational Drivers: [Logical decision factors]_
-_Social Influences: [Social and peer influences]_
-_Economic Influences: [Economic factors affecting behavior]_
-_Source: [URL]_
-
-### Customer Interaction Patterns
-
-[Customer interaction analysis with source citations]
-_Research and Discovery: [How customers find and research options]_
-_Purchase Decision Process: [Steps in purchase decision making]_
-_Post-Purchase Behavior: [After-purchase engagement patterns]_
-_Loyalty and Retention: [Factors driving customer loyalty]_
-_Source: [URL]_
-```
-
-### 5. Present Analysis and Continue Option
-
-**Show analysis and present continue option:**
-
-"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
-
-**Key Customer Behavior Findings:**
-
-- Customer behavior patterns clearly identified with drivers
-- Demographic segmentation thoroughly analyzed
-- Psychographic profiles mapped and documented
-- Customer interaction patterns captured
-- Multiple sources verified for critical insights
-
-**Ready to proceed to customer pain points?**
-[C] Continue - Save this to document and proceed to pain points analysis
-
-**HALT — wait for user response before proceeding.**
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- **CONTENT ALREADY WRITTEN TO DOCUMENT**
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-customer-pain-points.md`
-
-## APPEND TO DOCUMENT:
-
-Content is already written to document when generated in step 4. No additional append needed.
-
-## SUCCESS METRICS:
-
-✅ Customer behavior patterns identified with current citations
-✅ Demographic segmentation thoroughly analyzed
-✅ Psychographic profiles clearly documented
-✅ Customer interaction patterns captured
-✅ Multiple sources verified for critical insights
-✅ Content written immediately to document
-✅ [C] continue option presented and handled correctly
-✅ Proper routing to next step (customer pain points)
-✅ Research goals alignment maintained
-
-## FAILURE MODES:
-
-❌ Relying solely on training data without web verification for current facts
-
-❌ Missing critical customer behavior patterns
-❌ Incomplete demographic segmentation analysis
-❌ Missing psychographic profile documentation
-❌ Not writing content immediately to document
-❌ Not presenting [C] continue option after content generation
-❌ Not routing to customer pain points analysis step
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## CUSTOMER BEHAVIOR RESEARCH PROTOCOLS:
-
-- Research customer behavior studies and market research
-- Use demographic data from authoritative sources
-- Research psychographic profiling and value systems
-- Analyze customer interaction and engagement patterns
-- Focus on current behavior data and trends
-- Present conflicting information when sources disagree
-- Apply confidence levels appropriately
-
-## BEHAVIOR ANALYSIS STANDARDS:
-
-- Always cite URLs for web search results
-- Use authoritative customer research sources
-- Note data currency and potential limitations
-- Present multiple perspectives when sources conflict
-- Apply confidence levels to uncertain data
-- Focus on actionable customer insights
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
-
-Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification!