create-byan-agent 2.18.0 → 2.19.0

package/install/templates/_byan/bmb/workflows/module/steps-v/step-08-report.md

@@ -1,197 +0,0 @@
----
-name: 'step-08-report'
-description: 'Generate final validation report'
-
-validationReportOutput: '{validation_report_output}'
-agentValidationWorkflow: '{project-root}/_byan/bmb/workflows/agent/steps-v/step-01-validate.md'
-workflowValidationWorkflow: '{project-root}/_byan/bmb/workflows/workflow/steps-v/step-01-validate.md'
----
-
-# Step 8: Validation Report
-
-## STEP GOAL:
-
-Compile all validation results into a final report with actionable recommendations, including sub-process validation opportunities for built agents and workflows.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are the **Quality Assurance** — reporting results
-- ✅ Clear, actionable feedback
-- ✅ Sub-process validation for built components
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Compile Overall Status
-
-Review all validation sections and determine overall status:
-
-**PASS:** All checks passed, ready to proceed
-**WARNINGS:** Minor issues found, can proceed with fixes
-**FAIL:** Critical issues found, must fix before proceeding
-
-### 2. Generate Summary
-
-Add to `{validationReportOutput}`:
-
-```markdown
----
-
-## Overall Summary
-
-**Status:** {PASS/WARNINGS/FAIL}
-
-**Breakdown:**
-- File Structure: {status}
-- module.yaml: {status}
-- Agent Specs: {status} ({built_count} built, {spec_count} specs)
-- Workflow Specs: {status} ({built_count} built, {spec_count} specs)
-- Documentation: {status}
-- Installation Readiness: {status}
-
----
-
-## Component Status
-
-### Agents
-- **Built Agents:** {count} — {list}
-- **Spec Agents:** {count} — {list}
-
-### Workflows
-- **Built Workflows:** {count} — {list}
-- **Spec Workflows:** {count} — {list}
-
----
-
-## Recommendations
-
-{priority-listed-recommendations}
-
-### Priority 1 - Critical (must fix)
-
-{critical_issues}
-
-### Priority 2 - High (should fix)
-
-{high_priority_issues}
-
-### Priority 3 - Medium (nice to have)
-
-{medium_priority_issues}
-
----
-
-## Sub-Process Validation
-
-{if built_agents_exist}
-### Built Agent Deep Validation
-
-The following built agents can be validated in detail using the agent validation workflow:
-
-{for each built_agent}
-- **{agent_name}** — Use `{agentValidationWorkflow}`
-
-**Recommendation:** Run agent validation workflow on each built agent to verify:
-- Frontmatter completeness
-- Persona quality
-- Menu structure compliance
-- Sidecar validation
-
-**After fixing any module-level issues, I can spawn sub-processes to validate each built agent in parallel.**
-{endif}
-
-{if built_workflows_exist}
-### Built Workflow Deep Validation
-
-The following built workflows can be validated in detail using the workflow validation workflow:
-
-{for each built_workflow}
-- **{workflow_name}** — Use `{workflowValidationWorkflow}`
-
-**Recommendation:** Run workflow validation workflow on each built workflow to verify:
-- Step file compliance
-- Tri-modal structure (steps-c/steps-e/steps-v/)
-- Frontmatter completeness
-- Size limits compliance
-
-**After fixing any module-level issues, I can spawn sub-processes to validate each built workflow in parallel.**
-{endif}
-
----
-
-## Next Steps
-
-{based_on_status}
-
-{if specs_exist}
-### Build Spec Components
-
-**Spec Agents:** {spec_count}
-- Use `bmad:bmb:agents:agent-builder` to create: {spec_agent_names}
-
-**Spec Workflows:** {spec_count}
-- Use `bmad:bmb:workflows:workflow` to create: {spec_workflow_names}
-
-**After building specs, re-run validation to verify compliance.**
-{endif}
-
----
-
-**Validation Completed:** {timestamp}
-```
-
-### 3. Present Report
-
-"**✓ Validation complete!**"
-
-**Overall Status:** {overall_status}
-
-**Report saved to:** `{validationReportOutput}`
-
-{if built_components_exist}
-"**Built components found:**"
-- Built Agents: {count}
-- Built Workflows: {count}
-
-"**These can be validated in depth via sub-process.**"
-{endif}
-
-### 4. Offer Next Actions
-
-"**What would you like to do?**"
-
-- **[R]ead report** — Show the full validation report
-- **[S]ub-process validation** — Run deep validation on built agents/workflows
-- **[F]ix issues** — Edit mode to fix identified problems
-- **[D]one** — Complete validation
-
-### 5. Menu Handling
-
-- IF R: Display the full report
-- IF S:
-  - {if built_components_exist}
-  - Offer to run agent validation on built agents
-  - Offer to run workflow validation on built workflows
-  - Can run in parallel for efficiency
-  - {else}
-  - "No built components found for sub-process validation."
-  - {endif}
-- IF F: Offer to load Edit mode
-- IF D: Complete validation session
-
----
-
-## Success Metrics
-
-✅ Overall status determined
-✅ Complete report generated
-✅ Actionable recommendations provided
-✅ Sub-process validation opportunities identified
-✅ Next steps offered

package/install/templates/_byan/bmb/workflows/module/workflow.md

@@ -1,100 +0,0 @@
----
-name: module
-description: Quad-modal workflow for creating BMAD modules (Brief + Create + Edit + Validate)
-web_bundle: true
-installed_path: '{project-root}/_byan/bmb/workflows/module'
----
-
-# Module Workflow
-
-The module workflow guides users through creating complete, installable BMAD modules through a quad-modal process: **Brief → Create → Edit → Validate**.
-
-## What This Workflow Does
-
-- **Brief mode** — Collaboratively explore and design your module vision
-- **Create mode** — Build the module structure from a brief
-- **Edit mode** — Modify existing briefs or modules
-- **Validate mode** — Check compliance and completeness
-
-## Role
-
-You are the **Module Architect** — a specialist in BMAD module design. You understand that modules are complex entities requiring careful planning before implementation.
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Mode Determination
-
-**Check invocation context:**
-- Look for existing module brief or plan
-- Check if user is starting fresh or continuing work
-- Determine what mode they need
-
-**Ask the user:**
-
-**"Welcome to the Module workflow! What would you like to do?"**
-
-- **[B] Brief** — Create a module brief (exploratory, creative discovery)
-- **[C] Create** — Build a module from a brief
-- **[E] Edit** — Modify an existing brief or module
-- **[V] Validate** — Validate a brief or module
-
-### 2. Route to First Step
-
-**IF mode == brief (B):**
-Load `{installed_path}/steps-b/step-01-welcome.md`
-
-**IF mode == create (C):**
-Ask: "Where is the module brief?" → Load `{installed_path}/steps-c/step-01-load-brief.md`
-
-**IF mode == edit (E):**
-Ask: "What would you like to edit?" → Load `{installed_path}/steps-e/step-01-assess.md`
-
-**IF mode == validate (V):**
-Ask: "What would you like to validate?" → Load `{installed_path}/steps-v/step-01-validate.md`
-
----
-
-## Configuration
-
-This workflow references:
-- `{installed_path}/data/` — Module standards and templates
-- `{installed_path}/templates/` — Output templates
-
----
-
-## Workflow Structure
-
-```
-module/
-├── workflow.md              # This file - mode routing
-├── data/                    # Shared standards
-│   ├── module-standards.md
-│   ├── module-yaml-conventions.md
-│   ├── agent-architecture.md
-│   └── module-installer-standards.md
-├── templates/               # Output templates
-│   ├── brief-template.md
-│   ├── agent-spec-template.md
-│   └── workflow-spec-template.md
-├── steps-b/                 # Brief mode (13 steps)
-├── steps-c/                 # Create mode (8 steps)
-├── steps-e/                 # Edit mode
-└── steps-v/                 # Validate mode
-```
-
----
-
-## Output
-
-**Brief mode produces:**
-- `module-brief-{code}.md` — Complete module vision document
-
-**Create mode produces:**
-- Module directory structure
-- `module.yaml` with install configuration
-- `_module-installer/` folder (if needed)
-- Agent placeholder/spec files
-- Workflow placeholder/spec files
-- `README.md` and `TODO.md`

package/install/templates/_byan/bmb/workflows/workflow/data/common-workflow-tools.csv

@@ -1,19 +0,0 @@
-propose,type,tool_name,description,url,requires_install
-always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions about workflow steps or work in progress.",{project-root}/_byan/core/workflows/party-mode/workflow.md,no
-always,workflow,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs, forcing assessment from multiple perspectives and techniques.",{project-root}/_byan/core/workflows/advanced-elicitation/workflow.xml,no
-always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions, encouraging divergent thinking, and synthesizing concepts into actionable insights through collaborative creative exploration.",{project-root}/_byan/core/tasks/brainstorming.xml,no
-always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches, extract relevant data, and incorporate current information into responses when up-to-date information is required beyond training knowledge.",,no
-always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files, facilitating seamless data handling, storage, and document management within user environments.",,no
-always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents that handle specific tasks or modules within larger workflows, improving efficiency through parallel processing and modular task delegation.",,no
-always,llm-tool-feature,sub-processes,"Enables LLM to initiate and manage subprocesses that operate independently, allowing for parallel processing of complex tasks and improved resource utilization during long-running operations.",,no
-always,tool-memory,sidecar-file,"Creates a persistent history file that gets written during workflow execution and loaded on future runs, enabling continuity through session-to-session state management. Used for agent or workflow initialization with previous session context, learning from past interactions, and maintaining progress across multiple executions.",,no
-example,tool-memory,vector-database,"Stores and retrieves semantic information through embeddings for intelligent memory access, enabling workflows to find relevant past experiences, patterns, or context based on meaning rather than exact matches. Useful for complex learning systems, pattern recognition, and semantic search across workflow history.",https://github.com/modelcontextprotocol/servers/tree/main/src/rag-agent,yes
-example,mcp,context-7,"A curated knowledge base of API documentation and third-party tool references, enabling LLM to access accurate and current information for integration and development tasks when specific technical documentation is needed.",https://github.com/modelcontextprotocol/servers/tree/main/src/context-7,yes
-example,mcp,playwright,"Provides capabilities for LLM to perform web browser automation including navigation, form submission, data extraction, and testing actions on web pages, facilitating automated web interactions and quality assurance.",https://github.com/modelcontextprotocol/servers/tree/main/src/playwright,yes
-example,workflow,security-auditor,"Analyzes workflows and code for security vulnerabilities, compliance issues, and best practices violations, providing detailed security assessments and remediation recommendations for production-ready systems.",,no
-example,task,code-review,"Performs systematic code analysis with peer review perspectives, identifying bugs, performance issues, style violations, and architectural problems through adversarial review techniques.",,no
-example,mcp,git-integration,"Enables direct Git repository operations including commits, branches, merges, and history analysis, allowing workflows to interact with version control systems for code management and collaboration.",https://github.com/modelcontextprotocol/servers/tree/main/src/git,yes
-example,mcp,database-connector,"Provides direct database connectivity for querying, updating, and managing data across multiple database types, enabling workflows to interact with structured data sources and perform data-driven operations.",https://github.com/modelcontextprotocol/servers/tree/main/src/postgres,yes
-example,task,api-testing,"Automated API endpoint testing with request/response validation, authentication handling, and comprehensive reporting for REST, GraphQL, and other API types through systematic test generation.",,no
-example,workflow,deployment-manager,"Orchestrates application deployment across multiple environments with rollback capabilities, health checks, and automated release pipelines for continuous integration and delivery workflows.",,no
-example,task,data-validator,"Validates data quality, schema compliance, and business rules through comprehensive data profiling with detailed reporting and anomaly detection for data-intensive workflows.",,no

package/install/templates/_byan/bmb/workflows/workflow/data/frontmatter-standards.md

@@ -1,225 +0,0 @@
-# Frontmatter Standards
-
-**Purpose:** Variables, paths, and frontmatter rules for workflow steps.
-
----
-
-## Golden Rules
-
-1. **Only variables USED in the step** may be in frontmatter
-2. **All file references MUST use `{variable}` format** - no hardcoded paths
-3. **Paths within workflow folder MUST be relative** - NO `workflow_path` variable allowed
-
----
-
-## Standard Variables (Always Available)
-
-| Variable                     | Example Value                        |
-| ---------------------------- | ------------------------------------ |
-| `{project-root}`             | `/Users/user/dev/BMAD-METHOD`        |
-| `{project_name}`             | `my-project`                         |
-| `{output_folder}`            | `/Users/user/dev/BMAD-METHOD/output` |
-| `{user_name}`                | `Brian`                              |
-| `{communication_language}`   | `english`                            |
-| `{document_output_language}` | `english`                            |
-
----
-
-## Module-Specific Variables
-
-Workflows in a MODULE can access additional variables from its `module.yaml`.
-
-**BMB Module example:**
-```yaml
-bmb_creations_output_folder: '{project-root}/_byan/bmb-creations'
-```
-
-**Standalone workflows:** Only have access to standard variables.
-
----
-
-## Frontmatter Structure
-
-### Required Fields
-```yaml
----
-name: 'step-[N]-[name]'
-description: '[what this step does]'
----
-```
-
-### File References - ONLY variables used in this step
-```yaml
----
-# Step to step (SAME folder) - use ./filename.md
-nextStepFile: './step-02-vision.md'
-
-# Step to template (PARENT folder) - use ../filename.md
-productBriefTemplate: '../product-brief.template.md'
-
-# Step to data (SUBFOLDER) - use ./data/filename.md
-someData: './data/config.csv'
-
-# Output files - use variable
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
-
-# External references - use {project-root}
-advancedElicitationTask: '{project-root}/_byan/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_byan/core/workflows/party-mode/workflow.md'
----
-```
-
----
-
-## Critical Rule: Unused Variables Forbidden
-
-### ❌ VIOLATION - Variable defined but never used
-```yaml
----
-outputFile: '{output_folder}/output.md'
-thisStepFile: './step-01-init.md'      # ❌ NEVER USED in body
-workflowFile: './workflow.md'           # ❌ NEVER USED in body
----
-# Step body never mentions {thisStepFile} or {workflowFile}
-```
-
-### ✅ CORRECT - Only variables that are used
-```yaml
----
-outputFile: '{output_folder}/output.md'
-nextStepFile: './step-02-foo.md'
----
-# Step body uses {outputFile} and {nextStepFile}
-```
-
-**Detection Rule:** For EVERY variable in frontmatter, search the step body for `{variableName}`. If not found, it's a violation.
-
----
-
-## Path Rules - NO EXCEPTIONS
-
-### 1. Step to Step (SAME folder) = ./filename.md
-```yaml
-# ❌ WRONG
-nextStepFile: './step-02.md'
-nextStepFile: '{project-root}/_byan/bmm/workflows/foo/steps/step-02.md'
-
-# ✅ CORRECT
-nextStepFile: './step-02-vision.md'
-```
-
-### 2. Step to Template (PARENT folder) = ../filename.md
-```yaml
-# ❌ WRONG
-someTemplate: '{workflow_path}/templates/template.md'
-
-# ✅ CORRECT
-someTemplate: '../template.md'
-```
-
-### 3. Step to Subfolder = ./subfolder/file.md
-```yaml
-# ❌ WRONG
-dataFile: '{workflow_path}/data/config.csv'
-
-# ✅ CORRECT
-dataFile: './data/config.csv'
-```
-
-### 4. External References = {project-root}/...
-```yaml
-# ✅ CORRECT
-advancedElicitationTask: '{project-root}/_byan/core/workflows/advanced-elicitation/workflow.xml'
-```
-
-### 5. Output Files = Use folder variable
-```yaml
-# ✅ CORRECT
-outputFile: '{planning_artifacts}/workflow-output-{project_name}.md'
-outputFile: '{output_folder}/output.md'
-```
-
----
-
-## ❌ FORBIDDEN Patterns
-
-These patterns are **NEVER ALLOWED** in workflow step frontmatter:
-
-| Pattern                               | Why It's Wrong                                        |
-| ------------------------------------- | ----------------------------------------------------- |
-| `workflow_path: '{project-root}/...'` | Use relative paths instead                            |
-| `thisStepFile: './step-XX.md'`        | Almost never used - remove unless actually referenced |
-| `workflowFile: './workflow.md'`       | Almost never used - remove unless actually referenced |
-| `./...`                               | Use `./step-XX.md` (same folder)                      |
-| `{workflow_path}/templates/...`       | Use `../template.md` (parent folder)                  |
-| `{workflow_path}/data/...`            | Use `./data/file.md` (subfolder)                      |
-
----
-
-## Variable Naming
-
-Use `snake_case` with descriptive prefixes:
-
-| Pattern        | Usage               | Example                      |
-| -------------- | ------------------- | ---------------------------- |
-| `{*_File}`     | File references     | `outputFile`, `nextStepFile` |
-| `{*_Task}`     | Task references     | `advancedElicitationTask`    |
-| `{*_Workflow}` | Workflow references | `partyModeWorkflow`          |
-| `{*_Template}` | Templates           | `productBriefTemplate`       |
-| `{*_Data}`     | Data files          | `dietaryData`                |
-
----
-
-## Defining New Variables
-
-Steps can define NEW variables that future steps will use.
-
-**Step 01 defines:**
-```yaml
----
-targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{workflow_name}'
----
-# Uses {targetWorkflowPath} in body
-```
-
-**Step 02 uses:**
-```yaml
----
-targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{workflow_name}'
-workflowPlanFile: '{targetWorkflowPath}/plan.md'
----
-# Uses {targetWorkflowPath} and {workflowPlanFile} in body
-```
-
----
-
-## Continuable Workflow Frontmatter
-
-```yaml
----
-stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
-lastStep: 'step-03-design'
-lastContinued: '2025-01-02'
-date: '2025-01-01'
----
-```
-
-**Step tracking:** Each step appends its NAME to `stepsCompleted`.
-
----
-
-## Validation Checklist
-
-For EVERY step frontmatter, verify:
-
-- [ ] `name` present, kebab-case format
-- [ ] `description` present
-- [ ] Extract ALL variable names from frontmatter (between `---` markers)
-- [ ] For EACH variable, search body: is `{variableName}` present?
-- [ ] If variable NOT in body → ❌ VIOLATION, remove from frontmatter
-- [ ] All step-to-step paths use `./filename.md` format (same folder)
-- [ ] All parent-folder paths use `../filename.md` format
-- [ ] All subfolder paths use `./subfolder/filename.md` format
-- [ ] NO `{workflow_path}` variable exists
-- [ ] External paths use `{project-root}` variable
-- [ ] Module variables only used if workflow belongs to that module