siesa-agents 2.1.78 → 2.1.79

package/siesa-agents/observability/scripts/sa-init-project.js

@@ -0,0 +1,294 @@
+#!/usr/bin/env node
+// sa-init-project.js — Initialize a `.siesa-project` file that consolidates observability
+// metrics across multiple sub-repos belonging to the same logical project.
+//
+// Why this exists:
+//   sa-emit.js derives `project_id` from `git remote get-url origin` by default. For projects
+//   split across docs/backend/frontend sub-repos (each with a different remote), the same
+//   logical project ends up fragmented in GCP under several `project_id` values. A
+//   `.siesa-project` file placed in a parent directory above all sub-repos lets sa-emit.js
+//   collapse them under one consistent slug.
+//
+// Two modes:
+//   --detect                       Inspect the cwd, propose a logical slug and list candidate
+//                                  parent directories. Outputs a single JSON object to stdout.
+//   --write --slug <s> --dir <d>   Write `<d>/.siesa-project` with `<s>` as its only line.
+//                                  Outputs a JSON status object. Refuses to overwrite unless
+//                                  `--force` is passed.
+//
+// Exit codes:
+//   0  Success (detect produced a proposal OR write succeeded)
+//   1  Argument / usage error
+//   2  Detection completed but no action is required (single-repo, no remote, already
+//      configured) — the JSON `status` field explains which case
+//   3  Write failed (target exists without --force, permission error, etc.)
+
+'use strict'
+
+const fs = require('fs')
+const path = require('path')
+const { execSync } = require('child_process')
+
+function parseArgs(argv) {
+  const out = {}
+  let i = 0
+  while (i < argv.length) {
+    const a = argv[i]
+    if (a.startsWith('--')) {
+      const key = a.slice(2)
+      const next = argv[i + 1]
+      if (next !== undefined && !next.startsWith('--')) {
+        out[key] = next
+        i += 2
+      } else {
+        out[key] = true
+        i += 1
+      }
+    } else {
+      i += 1
+    }
+  }
+  return out
+}
+
+function emit(obj) {
+  process.stdout.write(JSON.stringify(obj, null, 2) + '\n')
+}
+
+function tryExec(cmd, opts) {
+  try {
+    return execSync(cmd, Object.assign({ encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] }, opts || {})).trim()
+  } catch (_) {
+    return null
+  }
+}
+
+// Walk up from `startDir` looking for an existing `.siesa-project`. Returns
+// { path, value } of the first match found, or null.
+function findExistingSiesaProject(startDir) {
+  let cur = path.resolve(startDir)
+  for (let i = 0; i < 40; i++) {
+    const candidate = path.join(cur, '.siesa-project')
+    if (fs.existsSync(candidate)) {
+      try {
+        const first = fs.readFileSync(candidate, 'utf8').split(/\r?\n/)[0].trim()
+        return { path: candidate, value: first }
+      } catch (_) {
+        return { path: candidate, value: null }
+      }
+    }
+    const parent = path.dirname(cur)
+    if (parent === cur) return null
+    cur = parent
+  }
+  return null
+}
+
+// Parse `<org>/<repo>` from a git remote URL. Returns { org, repo } or null.
+function parseRemote(url) {
+  if (!url) return null
+  const m = url.match(/[:/]([^/:]+)\/([^/:]+?)(?:\.git)?$/)
+  if (!m) return null
+  return { org: m[1], repo: m[2] }
+}
+
+// Apply the Siesa multi-repo naming convention to derive a logical slug.
+//
+//   business-pos-backend-pdv        → pos-pdv
+//   business-pos-docs-tomapedido    → pos-tomapedido
+//   foo-frontend-bar                → foo-bar
+//
+// Returns { matched: true, slug, module, role, rest } if the convention applies,
+// or { matched: false } if the repo name has no docs|backend|frontend segment.
+function deriveLogicalSlug(repoName) {
+  if (!repoName) return { matched: false }
+  const parts = repoName.split('-')
+  const roleIdx = parts.findIndex(p => p === 'docs' || p === 'backend' || p === 'frontend')
+  if (roleIdx === -1) return { matched: false }
+
+  // Drop a leading "business-" prefix if present — it is an organizational marker, not
+  // part of the logical project name.
+  const cleaned = parts[0] === 'business' ? parts.slice(1) : parts.slice()
+  const adjustedRoleIdx = parts[0] === 'business' ? roleIdx - 1 : roleIdx
+  if (adjustedRoleIdx < 0) return { matched: false }
+
+  const role = cleaned[adjustedRoleIdx]
+  const before = cleaned.slice(0, adjustedRoleIdx)
+  const after = cleaned.slice(adjustedRoleIdx + 1)
+  if (before.length === 0 || after.length === 0) return { matched: false }
+
+  const slug = before.concat(after).join('-')
+  return {
+    matched: true,
+    slug,
+    module: before.join('-'),
+    role,
+    rest: after.join('-'),
+  }
+}
+
+function listParentCandidates(gitRoot) {
+  const candidates = []
+  let cur = path.resolve(gitRoot)
+  const labels = [
+    'git root',
+    '1 level up',
+    '2 levels up (typical parent of docs/apps/)',
+    '3 levels up',
+    '4 levels up',
+  ]
+  for (let i = 0; i < labels.length; i++) {
+    candidates.push({ path: cur, label: labels[i], levelsUp: i })
+    const parent = path.dirname(cur)
+    if (parent === cur) break
+    cur = parent
+  }
+  return candidates
+}
+
+function runDetect() {
+  const cwd = process.cwd()
+  const gitRoot = tryExec('git rev-parse --show-toplevel')
+  if (!gitRoot) {
+    emit({
+      status: 'no-git-repo',
+      message: 'The current directory is not inside a git repository. .siesa-project resolution relies on walking up from a git-tracked sub-repo, so initializing here is unlikely to help.',
+      cwd,
+    })
+    process.exit(2)
+  }
+
+  const remoteUrl = tryExec('git remote get-url origin')
+  const remoteParsed = parseRemote(remoteUrl)
+  const repoName = remoteParsed ? remoteParsed.repo : null
+
+  const existing = findExistingSiesaProject(gitRoot)
+  if (existing) {
+    emit({
+      status: 'already-configured',
+      message: 'A .siesa-project file already exists above this repo. sa-emit.js will use it as-is.',
+      git_root: gitRoot,
+      remote_url: remoteUrl,
+      existing_siesa_project: existing,
+    })
+    process.exit(2)
+  }
+
+  if (!remoteUrl) {
+    emit({
+      status: 'no-remote',
+      message: 'This repo has no `origin` remote. Without it sa-emit.js falls back to "unknown" — set up a remote or pass --slug to write a .siesa-project manually.',
+      git_root: gitRoot,
+    })
+    process.exit(2)
+  }
+
+  const derived = deriveLogicalSlug(repoName)
+
+  if (!derived.matched) {
+    emit({
+      status: 'single-repo',
+      message: 'This repo name does not match the multi-repo convention (no docs|backend|frontend segment). sa-emit.js will report project_id based on the git remote, which is already unambiguous for single-repo projects. No .siesa-project is required.',
+      git_root: gitRoot,
+      remote_url: remoteUrl,
+      remote_repo: repoName,
+      fallback_project_id: remoteParsed ? `${remoteParsed.org}/${remoteParsed.repo}` : null,
+    })
+    process.exit(2)
+  }
+
+  const candidates = listParentCandidates(gitRoot)
+  // For the multi-repo convention the typical layout is:
+  //   <parent>/docs/         (git remote: business-pos-docs-pdv)
+  //   <parent>/apps/backend/ (git remote: business-pos-backend-pdv)
+  //   <parent>/apps/frontend/(git remote: business-pos-frontend-pdv)
+  // The git root for backend/frontend sits 2 levels under <parent>; for docs it sits 1 level
+  // under. We surface both as the recommended choice and let the user pick.
+  const recommendedLevels = derived.role === 'docs' ? 1 : 2
+  const recommended = candidates.find(c => c.levelsUp === recommendedLevels) || candidates[candidates.length - 1]
+
+  emit({
+    status: 'ready',
+    message: 'Multi-repo convention detected. Pick the parent directory that contains every sub-repo of this logical project, then re-run with --write.',
+    git_root: gitRoot,
+    remote_url: remoteUrl,
+    remote_repo: repoName,
+    convention_match: true,
+    proposed_slug: derived.slug,
+    convention_breakdown: {
+      module: derived.module,
+      role: derived.role,
+      rest: derived.rest,
+    },
+    parent_candidates: candidates,
+    recommended_dir: recommended.path,
+    next_step_example: `node sa-init-project.js --write --slug "${derived.slug}" --dir "${recommended.path}"`,
+  })
+  process.exit(0)
+}
+
+function runWrite(args) {
+  const slug = args['slug']
+  const dir = args['dir']
+  const force = Boolean(args['force'])
+
+  if (!slug || typeof slug !== 'string') {
+    console.error('Error: --slug "<value>" is required for --write')
+    process.exit(1)
+  }
+  if (!dir || typeof dir !== 'string') {
+    console.error('Error: --dir "<path>" is required for --write')
+    process.exit(1)
+  }
+
+  const normalizedSlug = slug.trim()
+  if (!/^[a-z0-9][a-z0-9-]*[a-z0-9]$/.test(normalizedSlug)) {
+    console.error(`Error: slug "${normalizedSlug}" must be lowercase letters, digits and dashes (e.g. "pos-pdv"). No spaces, no uppercase, no leading/trailing dash.`)
+    process.exit(1)
+  }
+
+  const resolvedDir = path.resolve(dir)
+  if (!fs.existsSync(resolvedDir) || !fs.statSync(resolvedDir).isDirectory()) {
+    console.error(`Error: directory does not exist: ${resolvedDir}`)
+    process.exit(3)
+  }
+
+  const target = path.join(resolvedDir, '.siesa-project')
+  if (fs.existsSync(target) && !force) {
+    let current = null
+    try { current = fs.readFileSync(target, 'utf8').split(/\r?\n/)[0].trim() } catch (_) {}
+    emit({
+      status: 'exists',
+      message: '.siesa-project already exists at this location. Pass --force to overwrite.',
+      path: target,
+      current_value: current,
+      requested_slug: normalizedSlug,
+    })
+    process.exit(3)
+  }
+
+  try {
+    fs.writeFileSync(target, normalizedSlug + '\n', { encoding: 'utf8' })
+  } catch (err) {
+    emit({ status: 'error', message: `Failed to write ${target}: ${err.message}` })
+    process.exit(3)
+  }
+
+  emit({
+    status: 'written',
+    message: `Wrote ${target}. sa-emit.js will now report project_id="${normalizedSlug}" from anywhere inside ${resolvedDir}.`,
+    path: target,
+    slug: normalizedSlug,
+    parent_dir: resolvedDir,
+  })
+  process.exit(0)
+}
+
+const args = parseArgs(process.argv.slice(2))
+
+if (args['write']) {
+  runWrite(args)
+} else {
+  // --detect is the default mode. Treat any other invocation as a detection request.
+  runDetect()
+}

package/siesa-agents/resources/architecture/architecture-both.md

@@ -1,6 +1,8 @@
 ---
 type: base-architecture
 status: base
+stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
+lastStep: 8
 note: >
   This document was automatically generated during siesa-agents installation.
   It represents the Siesa corporate base architecture applicable to all microservices.
@@ -151,33 +153,35 @@ builder.Services.AddHealthChecks();                    // 9. Health Checks
 ## 3. Solution Structure (Backend)
 
 ```
-src/
-├── {Service}.API/              # Presentation Layer — Minimal API Endpoints
-│   ├── Endpoints/
-│   │   └── {Feature}/         # Endpoint classes per feature
-│   ├── Middleware/
-│   └── Program.cs
-├── {Service}.Application/      # Application Layer — CQRS, DTOs, Validators
-│   └── {Feature}/
-│       ├── Commands/
-│       ├── Queries/
-│       ├── DTOs/
-│       ├── Validators/
-│       └── Interfaces/
-├── {Service}.Domain/           # Domain Layer — Entities, Value Objects, Events
-│   └── {Feature}/
-│       ├── Entities/
-│       ├── ValueObjects/
-│       └── Events/
-└── {Service}.Infrastructure/   # Infrastructure Layer — EF Core, Repositories
-    ├── Data/
-    │   ├── Configurations/
-    │   ├── Migrations/
-    │   └── {Service}DbContext.cs
-    └── Repositories/
-tests/
-├── {Service}.UnitTests/        # xUnit + EF Core InMemory
-└── {Service}.IntegrationTests/ # xUnit + Testcontainers.PostgreSql
+apps/
+└── backend/
+    ├── src/
+    │   ├── {Service}.API/              # Presentation Layer — Minimal API Endpoints
+    │   │   ├── Endpoints/
+    │   │   │   └── {Feature}/         # Endpoint classes per feature
+    │   │   ├── Middleware/
+    │   │   └── Program.cs
+    │   ├── {Service}.Application/      # Application Layer — CQRS, DTOs, Validators
+    │   │   └── {Feature}/
+    │   │       ├── Commands/
+    │   │       ├── Queries/
+    │   │       ├── DTOs/
+    │   │       ├── Validators/
+    │   │       └── Interfaces/
+    │   ├── {Service}.Domain/           # Domain Layer — Entities, Value Objects, Events
+    │   │   └── {Feature}/
+    │   │       ├── Entities/
+    │   │       ├── ValueObjects/
+    │   │       └── Events/
+    │   └── {Service}.Infrastructure/   # Infrastructure Layer — EF Core, Repositories
+    │       ├── Data/
+    │       │   ├── Configurations/
+    │       │   ├── Migrations/
+    │       │   └── {Service}DbContext.cs
+    │       └── Repositories/
+    └── tests/
+        ├── {Service}.UnitTests/        # xUnit + EF Core InMemory
+        └── {Service}.IntegrationTests/ # xUnit + Testcontainers.PostgreSql
 ```
 
 ---
@@ -187,37 +191,39 @@ tests/
 ### 4.1 Folder Structure
 
 ```
-src/
-├── main.tsx
-├── router.tsx
-├── routeTree.gen.ts            # Auto-generated by TanStack Router
-├── globals.css
-├── routes/                     # TanStack Router — file-based routing
-│   ├── __root.tsx              # Root layout
-│   ├── index.tsx
-│   ├── _auth.tsx               # Pathless layout
-│   ├── _auth/login.tsx
-│   ├── _app.tsx                # Protected layout
-│   └── _app/{module}/*
-├── modules/                    # DDD business modules
-│   └── {module}/
-│       ├── domain/             # Entities, repository interfaces, types
-│       ├── application/        # Use-cases, hooks, store
-│       ├── infrastructure/     # Repository impl, api, adapters
-│       └── presentation/       # Components
-├── shared/                     # Reusable code
-│   ├── components/             # UI components, shadcn/ui
-│   ├── hooks/
-│   ├── lib/                    # Utilities, api-client
-│   ├── types/
-│   └── constants/
-├── app/                        # Global configuration
-│   ├── providers/
-│   └── store/
-└── infrastructure/             # Global external services
-    ├── api/
-    ├── storage/
-    └── pwa/
+apps/
+└── frontend/
+    └── src/
+        ├── main.tsx
+        ├── router.tsx
+        ├── routeTree.gen.ts            # Auto-generated by TanStack Router
+        ├── globals.css
+        ├── routes/                     # TanStack Router — file-based routing
+        │   ├── __root.tsx              # Root layout
+        │   ├── index.tsx
+        │   ├── _auth.tsx               # Pathless layout
+        │   ├── _auth/login.tsx
+        │   ├── _app.tsx                # Protected layout
+        │   └── _app/{module}/*
+        ├── modules/                    # DDD business modules
+        │   └── {module}/
+        │       ├── domain/             # Entities, repository interfaces, types
+        │       ├── application/        # Use-cases, hooks, store
+        │       ├── infrastructure/     # Repository impl, api, adapters
+        │       └── presentation/       # Components
+        ├── shared/                     # Reusable code
+        │   ├── components/             # UI components, shadcn/ui
+        │   ├── hooks/
+        │   ├── lib/                    # Utilities, api-client
+        │   ├── types/
+        │   └── constants/
+        ├── app/                        # Global configuration
+        │   ├── providers/
+        │   └── store/
+        └── infrastructure/             # Global external services
+            ├── api/
+            ├── storage/
+            └── pwa/
 ```
 
 ### 4.2 TanStack Router — File Conventions

package/siesa-agents/resources/architecture/architecture-single-backend.md

@@ -2,6 +2,8 @@
 type: base-architecture
 scope: backend
 status: base
+stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]
+lastStep: 8
 note: >
   This document was automatically generated during siesa-agents installation.
   It represents the Siesa corporate base architecture applicable to all microservices.
@@ -135,33 +137,35 @@ builder.Services.AddHealthChecks();                    // 9. Health Checks
 ## 3. Solution Structure (Backend)
 
 ```
-src/
-├── {Service}.API/              # Presentation Layer — Minimal API Endpoints
-│   ├── Endpoints/
-│   │   └── {Feature}/         # Endpoint classes per feature
-│   ├── Middleware/
-│   └── Program.cs
-├── {Service}.Application/      # Application Layer — CQRS, DTOs, Validators
-│   └── {Feature}/
-│       ├── Commands/
-│       ├── Queries/
-│       ├── DTOs/
-│       ├── Validators/
-│       └── Interfaces/
-├── {Service}.Domain/           # Domain Layer — Entities, Value Objects, Events
-│   └── {Feature}/
-│       ├── Entities/
-│       ├── ValueObjects/
-│       └── Events/
-└── {Service}.Infrastructure/   # Infrastructure Layer — EF Core, Repositories
-    ├── Data/
-    │   ├── Configurations/
-    │   ├── Migrations/
-    │   └── {Service}DbContext.cs
-    └── Repositories/
-tests/
-├── {Service}.UnitTests/        # xUnit + EF Core InMemory
-└── {Service}.IntegrationTests/ # xUnit + Testcontainers.PostgreSql
+apps/
+└── backend/
+    ├── src/
+    │   ├── {Service}.API/              # Presentation Layer — Minimal API Endpoints
+    │   │   ├── Endpoints/
+    │   │   │   └── {Feature}/         # Endpoint classes per feature
+    │   │   ├── Middleware/
+    │   │   └── Program.cs
+    │   ├── {Service}.Application/      # Application Layer — CQRS, DTOs, Validators
+    │   │   └── {Feature}/
+    │   │       ├── Commands/
+    │   │       ├── Queries/
+    │   │       ├── DTOs/
+    │   │       ├── Validators/
+    │   │       └── Interfaces/
+    │   ├── {Service}.Domain/           # Domain Layer — Entities, Value Objects, Events
+    │   │   └── {Feature}/
+    │   │       ├── Entities/
+    │   │       ├── ValueObjects/
+    │   │       └── Events/
+    │   └── {Service}.Infrastructure/   # Infrastructure Layer — EF Core, Repositories
+    │       ├── Data/
+    │       │   ├── Configurations/
+    │       │   ├── Migrations/
+    │       │   └── {Service}DbContext.cs
+    │       └── Repositories/
+    └── tests/
+        ├── {Service}.UnitTests/        # xUnit + EF Core InMemory
+        └── {Service}.IntegrationTests/ # xUnit + Testcontainers.PostgreSql
 ```
 
 ---

package/siesa-agents/resources/ux-ui/ux-design-specification.md

@@ -1,6 +1,8 @@
 ---
 type: base-ux-design-specification.md
 status: base
+stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14]
+lastStep: 14
 note: >
   This document was automatically generated during siesa-agents installation.
   It represents the Siesa corporate base UX/UI specification applicable to all frontend projects.

package/siesa-agents/sa/sync-epics-stories/steps/step-01-init.md

@@ -17,8 +17,8 @@ epicsFileFallback: '{output_folder}/planning-artifacts/epics.md'
 storiesFolder: '{output_folder}/implementation-artifacts/'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+partyModeWorkflow: 'skill:bmad-party-mode'
 
 ---
 

package/siesa-agents/sa/sync-epics-stories/steps/step-01b-continue.md

@@ -11,8 +11,8 @@ outputFile: '{project-root}/_bmad-output/jira_docs/project_config.yaml'
 workflowFile: '{workflow_path}/workflow.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: 'skill:bmad-advanced-elicitation'
+partyModeWorkflow: 'skill:bmad-party-mode'
 
 # Step 1B: Workflow Continuation
 

package/bmad/_config/agent-manifest.csv

@@ -1,20 +0,0 @@
-name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
-"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","- "Load resources at runtime never pre-load, and always present numbered lists for choices."","core","_bmad/core/agents/bmad-master.md"
-"agent-builder","Bond","Agent Building Expert","🤖","Agent Architecture Specialist + BMAD Compliance Expert","Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.","Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references.","- Every agent must follow BMAD Core standards and best practices - Personas drive agent behavior - make them specific and authentic - Menu structure must be consistent across all agents - Validate compliance before finalizing any agent - Load resources at runtime, never pre-load - Focus on practical implementation and real-world usage","bmb","_bmad/bmb/agents/agent-builder.md"
-"module-builder","Morgan","Module Creation Master","🏗️","Module Architecture Specialist + Full-Stack Systems Designer","Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.","Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability.","- Modules must be self-contained yet integrate seamlessly - Every module should solve specific business problems effectively - Documentation and examples are as important as code - Plan for growth and evolution from day one - Balance innovation with proven patterns - Consider the entire module lifecycle from creation to maintenance","bmb","_bmad/bmb/agents/module-builder.md"
-"workflow-builder","Wendy","Workflow Building Master","🔄","Workflow Architecture Specialist + Process Design Expert","Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.","Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow.","- Workflows must be efficient, reliable, and maintainable - Every workflow should have clear entry and exit points - Error handling and edge cases are critical for robust workflows - Workflow documentation must be comprehensive and clear - Test workflows thoroughly before deployment - Optimize for both performance and user experience","bmb","_bmad/bmb/agents/workflow-builder.md"
-"analyst","Mary","Business Analyst","📊","Strategic Business Analyst + Requirements Expert","Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.","Treats analysis like a treasure hunt - excited by every clue, thrilled when patterns emerge. Asks questions that spark 'aha!' moments while structuring insights with precision.","- Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. - Articulate requirements with absolute precision. Ensure all stakeholder voices heard. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm","_bmad/bmm/agents/analyst.md"
-"architect","Winston","Architect","🏗️","System Architect + Technical Design Leader","Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.","Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Champions boring technology that actually works.","- User journeys drive technical decisions. Embrace boring technology for stability. - Design simple solutions that scale when needed. Developer productivity is architecture. Connect every decision to business value and user impact. - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm","_bmad/bmm/agents/architect.md"
-"dev","Amelia","Developer Agent","💻","Senior Software Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","- The Story File is the single source of truth - tasks/subtasks sequence is authoritative over any model priors - Follow red-green-refactor cycle: write failing test, make it pass, improve code while keeping tests green - Never implement anything not mapped to a specific task/subtask in the story file - All existing tests must pass 100% before story is ready for review - Every task/subtask must be covered by comprehensive unit tests before marking complete - Project context provides coding standards but never overrides story requirements - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm","_bmad/bmm/agents/dev.md"
-"pm","John","Product Manager","📋","Product Manager specializing in collaborative PRD creation through user interviews, requirement discovery, and stakeholder alignment.","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","- Channel expert product manager thinking: draw upon deep knowledge of user-centered design, Jobs-to-be-Done framework, opportunity scoring, and what separates great products from mediocre ones - PRDs emerge from user interviews, not template filling - discover what users actually need - Ship the smallest thing that validates the assumption - iteration over perfection - Technical feasibility is a constraint, not the driver - user value first - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`","bmm","_bmad/bmm/agents/pm.md"
-"quick-flow-solo-dev","Barry","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","Barry handles Quick Flow - from tech spec creation through implementation. Minimum ceremony, lean artifacts, ruthless efficiency.","Direct, confident, and implementation-focused. Uses tech slang (e.g., refactor, patch, extract, spike) and gets straight to the point. No fluff, just results. Stays focused on the task at hand.","- Planning and execution are two sides of the same coin. - Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. - If `**/project-context.md` exists, follow it. If absent, proceed without.","bmm","_bmad/bmm/agents/quick-flow-solo-dev.md"
-"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","- Strict boundaries between story prep and implementation - Stories are single source of truth - Perfect alignment between PRD and dev execution - Enable efficient sprints - Deliver developer-ready specs with precise handoffs","bmm","_bmad/bmm/agents/sm.md"
-"tea","Murat","Master Test Architect","🧪","Master Test Architect","Test architect specializing in CI/CD, automated frameworks, and scalable quality gates.","Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments.","- Risk-based testing - depth scales with impact - Quality gates backed by data - Tests mirror usage patterns - Flakiness is critical technical debt - Tests first AI implements suite validates - Calculate risk vs value for every testing decision","bmm","_bmad/bmm/agents/tea.md"
-"tech-writer","Paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","- Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. - Docs are living artifacts that evolve with code. Know when to simplify vs when to be detailed.","bmm","_bmad/bmm/agents/tech-writer.md"
-"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","- Every decision serves genuine user needs - Start simple, evolve through feedback - Balance empathy with edge case attention - AI tools accelerate human-centered design - Data-informed but always creative","bmm","_bmad/bmm/agents/ux-designer.md"
-"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis","_bmad/cis/agents/brainstorming-coach.md"
-"creative-problem-solver","Dr. Quinn","Master Problem Solver","🔬","Systematic Problem-Solving Expert + Solutions Architect","Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.","Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments","Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.","cis","_bmad/cis/agents/creative-problem-solver.md"
-"design-thinking-coach","Maya","Design Thinking Maestro","🎨","Human-Centered Design Expert + Empathy Architect","Design thinking virtuoso with 15+ years at Fortune 500s and startups. Expert in empathy mapping, prototyping, and user insights.","Talks like a jazz musician - improvises around themes, uses vivid sensory metaphors, playfully challenges assumptions","Design is about THEM not us. Validate through real human interaction. Failure is feedback. Design WITH users not FOR them.","cis","_bmad/cis/agents/design-thinking-coach.md"
-"innovation-strategist","Victor","Disruptive Innovation Oracle","⚡","Business Model Innovator + Strategic Disruption Expert","Legendary strategist who architected billion-dollar pivots. Expert in Jobs-to-be-Done, Blue Ocean Strategy. Former McKinsey consultant.","Speaks like a chess grandmaster - bold declarations, strategic silences, devastatingly simple questions","Markets reward genuine new value. Innovation without business model thinking is theater. Incremental thinking means obsolete.","cis","_bmad/cis/agents/innovation-strategist.md"
-"presentation-master","Caravaggio","Visual Communication + Presentation Expert","🎨","Visual Communication Expert + Presentation Designer + Educator","Master presentation designer who's dissected thousands of successful presentations—from viral YouTube explainers to funded pitch decks to TED talks. Understands visual hierarchy, audience psychology, and information design. Knows when to be bold and casual, when to be polished and professional. Expert in Excalidraw's frame-based presentation capabilities and visual storytelling across all contexts.","Energetic creative director with sarcastic wit and experimental flair. Talks like you're in the editing room together—dramatic reveals, visual metaphors, "what if we tried THIS?!" energy. Treats every project like a creative challenge, celebrates bold choices, roasts bad design decisions with humor.","- Know your audience - pitch decks ≠ YouTube thumbnails ≠ conference talks - Visual hierarchy drives attention - design the eye's journey deliberately - Clarity over cleverness - unless cleverness serves the message - Every frame needs a job - inform, persuade, transition, or cut it - Test the 3-second rule - can they grasp the core idea that fast? - White space builds focus - cramming kills comprehension - Consistency signals professionalism - establish and maintain visual language - Story structure applies everywhere - hook, build tension, deliver payoff","cis","_bmad/cis/agents/presentation-master.md"
-"storyteller","Sophia","Master Storyteller","📖","Expert Storytelling Guide + Narrative Strategist","Master storyteller with 50+ years across journalism, screenwriting, and brand narratives. Expert in emotional psychology and audience engagement.","Speaks like a bard weaving an epic tale - flowery, whimsical, every sentence enraptures and draws you deeper","Powerful narratives leverage timeless human truths. Find the authentic story. Make the abstract concrete through vivid details.","cis","_bmad/cis/agents/storyteller/storyteller.md"

package/bmad/_config/agents/bmb-agent-builder.customize.yaml

@@ -1,41 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here