siesa-agents 2.1.78 → 2.1.80

package/bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -1,261 +0,0 @@
-# Step 1: Context Discovery & Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative discovery between technical peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on discovering existing project context and technology stack
-- 🎯 IDENTIFY critical implementation rules that AI agents need
-- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 📖 Read existing project files to understand current context
-- 💾 Initialize document and update frontmatter
-- 🚫 FORBIDDEN to load next step until discovery is complete
-
-## CONTEXT FROM EXTENSION (INHERITED — READ BEFORE PROCEEDING):
-
-The `workflow_ext.md` extension has already been executed. The following variables are now set in memory:
-
-- **`{selected_mode}`** — Either `"general"` or `"feature-specific"`
-- **`{output_file}`** — The resolved path for the output document
-- **`{feature_name}`** — Only set if `selected_mode = "feature-specific"`
-
-**IF `selected_mode = "feature-specific"`:**
-- Narrow your discovery scope to code, configs, and patterns relevant to `{feature_name}`
-- When speaking with the user, refer to the output document as `technical-preference.md` for `{feature_name}`
-- Skip areas of the codebase clearly unrelated to this feature
-
-**IF `selected_mode = "general"`:**
-- Perform full project-wide discovery
-- Refer to the output document as `project-context.md`
-
----
-
-## CONTEXT BOUNDARIES:
-
-- Variables from `workflow.md` are available in memory (`project_name`, `user_name`, `communication_language`, `user_skill_level`, etc.)
-- Focus on existing project files and architecture decisions
-- Look for patterns, conventions, and unique requirements
-- Prioritize rules that prevent implementation mistakes
-
-## YOUR TASK:
-
-Discover the project's technology stack, existing patterns, and critical implementation rules that AI agents must follow when writing code.
-
----
-
-## DISCOVERY SEQUENCE:
-
-### 1. Check for Existing Output Document
-
-First, check if the target output document already exists:
-
-- Look for file at `{output_file}`
-- If exists: Read complete file to understand existing rules
-- Present to user: "Encontré un documento existente con {number_of_sections} secciones. ¿Deseas actualizarlo o crear uno nuevo?"
-
-### 2. Discover Project Technology Stack
-
-Load and analyze project files to identify technologies:
-
-**Architecture Document:**
-
-- Look for `{planning_artifacts}/architecture.md`
-- Extract technology choices with specific versions
-- Note architectural decisions that affect implementation
-
-### 2.5 Load Company Standards (If Available)
-
-Check for and load company-specific technology standards:
-
-**Company Standards Discovery:**
-
-- Look for `{company_standards_path}` directory
-- If NOT found, also check `{project_root}/_bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/`
-
-**If directory exists, load ALL markdown files:**
-
-- `technology-stack.md` — Predefined technology stack and versions
-- `database-conventions.md` — PostgreSQL database naming conventions
-- `backend-standards.md` — Backend development patterns and rules
-- `frontend-standards.md` — Frontend development patterns
-- `architecture-patterns.md` — Architectural decision patterns
-- `technical-preferences-ux.md` — UX/UI preferences
-- `vite-config-standard.md` — Vite Config Standard
-
-**Priority Rules:**
-
-- Company standards take PRECEDENCE over discovered patterns
-- If technology versions differ, use company standards version
-- Merge discovered patterns with company-defined rules
-
-**Critical Rules to Extract:**
-
-When loading company standards, specifically look for and highlight:
-
-- 🔴 **siesa-ui-kit requirement** — Must check siesa-ui-kit before creating components
-- 🔴 **Spanish UI text** — All user-facing text must be in Spanish
-- 🔴 **DateTimeOffset** — Use DateTimeOffset not DateTime for PostgreSQL
-- Technology stack versions (.NET 10, Vite 7+, etc.)
-
-🔴 **MANDATORY — Load siesa-ui-kit Component Inventory:**
-
-- Fetch the complete component catalog from: `https://siesa-ui-kit.pages.dev/llms.txt`
-- Extract and include in the output document the **full list of available siesa-ui-kit components** organized by category
-- This ensures AI agents know EXACTLY which components exist and can use them instead of creating custom alternatives
-- Include a dedicated section listing all available siesa-ui-kit components
-- If the URL is unreachable, warn the user: "⚠️ No se pudo cargar el catálogo de siesa-ui-kit. Incluir lista manualmente en el project context."
-
-Report: "✅ Estándares corporativos cargados: {count} archivos con {rules_count} reglas críticas"
-Report: "✅ Catálogo siesa-ui-kit cargado: {component_count} componentes disponibles"
-
-**Package Files:**
-
-- Check for `package.json`, `requirements.txt`, `Cargo.toml`, etc.
-- Extract exact versions of all dependencies
-- Note development vs production dependencies
-
-**Configuration Files:**
-
-- Look for project language specific configs (example: `tsconfig.json`)
-- Build tool configs (webpack, vite, next.config.js, etc.)
-- Linting and formatting configs (.eslintrc, .prettierrc, etc.)
-- Testing configurations (jest.config.js, vitest.config.ts, etc.)
-
-### 3. Identify Existing Code Patterns
-
-Search through existing codebase for patterns:
-
-**Naming Conventions:**
-
-- File naming patterns (PascalCase, kebab-case, etc.)
-- Component/function naming conventions
-- Variable naming patterns
-- Test file naming patterns
-
-**Code Organization:**
-
-- How components are structured
-- Where utilities and helpers are placed
-- How services are organized
-- Test organization patterns
-
-**Documentation Patterns:**
-
-- Comment styles and conventions
-- Documentation requirements
-- README and API doc patterns
-
-### 4. Extract Critical Implementation Rules
-
-Look for rules that AI agents might miss:
-
-**Language-Specific Rules:**
-
-- TypeScript strict mode requirements
-- Import/export conventions
-- Async/await vs Promise usage patterns
-- Error handling patterns specific to the language
-
-**Framework-Specific Rules:**
-
-- React hooks usage patterns
-- API route conventions
-- Middleware usage patterns
-- State management patterns
-
-**Testing Rules:**
-
-- Test structure requirements
-- Mock usage conventions
-- Integration vs unit test boundaries
-- Coverage requirements
-
-**Development Workflow Rules:**
-
-- Branch naming conventions
-- Commit message patterns
-- PR review requirements
-- Deployment procedures
-
-### 5. Initialize Output Document
-
-Based on discovery, create or update the output document at `{output_file}`:
-
-#### A. Fresh Document Setup (if no existing file)
-
-Copy template from `{installed_path}/project-context-template.md` to `{output_file}`.
-Initialize frontmatter fields. Adjust title to match `{selected_mode}`:
-- General: `# Project Context for AI Agents`
-- Feature-specific: `# Technical Preference for {feature_name}`
-
-#### B. Existing Document Update
-
-Load existing file and prepare for updates.
-Set frontmatter `sections_completed` to track what will be updated.
-
-### 6. Present Discovery Summary
-
-Report findings to user:
-
-"Hola {user_name}! He analizado tu proyecto **{project_name}** para descubrir el contexto que los agentes de IA necesitan.
-
-**Stack Tecnológico Descubierto:**
-{list_of_technologies_with_versions}
-
-**Patrones Existentes Encontrados:**
-
-- {number_of_patterns} patrones de implementación
-- {number_of_conventions} convenciones de código
-- {number_of_rules} reglas críticas
-
-**Áreas Clave para las Reglas de Contexto:**
-
-- {area_1} (ej: configuración TypeScript)
-- {area_2} (ej: patrones de Testing)
-- {area_3} (ej: organización del código)
-
-{if_existing_context}
-**Contexto Existente:** Se encontraron {sections} secciones ya definidas. Podemos actualizarlas o agregar nuevas.
-{/if_existing_context}
-
-Listo para crear/actualizar tu documento de contexto. Esto ayudará a los agentes a implementar código de forma consistente con los estándares del proyecto.
-
-[C] Continuar con la generación del contexto"
-
----
-
-## SUCCESS METRICS:
-
-✅ Documento de salida correctamente detectado o inicializado en `{output_file}`
-✅ Stack tecnológico identificado con versiones exactas
-✅ Estándares corporativos cargados (si están disponibles)
-✅ Catálogo de siesa-ui-kit cargado
-✅ Patrones de implementación críticos descubiertos
-✅ Resumen de descubrimiento presentado claramente al usuario
-✅ Usuario listo para proceder con la generación del contexto
-
-## FAILURE MODES:
-
-❌ No verificar si el documento de salida ya existe antes de crear uno nuevo
-❌ No resolver `{output_file}` correctamente según `{selected_mode}`
-❌ Faltan versiones críticas de tecnologías o configuraciones
-❌ Pasar por alto patrones o convenciones de código importantes
-❌ No inicializar el frontmatter correctamente
-❌ No presentar un resumen claro del descubrimiento al usuario
-
----
-
-## NEXT STEP:
-
-After user selects [C] to continue, load `./step-02-generate.md` to collaboratively generate the specific context rules.
-
-**Remember:** Do NOT proceed to step-02 until:
-1. User explicitly selects [C]
-2. Discovery is confirmed complete
-3. The initial file has been written at `{output_file}` with proper frontmatter

package/bmad/bmm/workflows/generate-project-context/steps/step-02-generate.md

@@ -1,342 +0,0 @@
-# Step 2: Context Rules Generation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative discovery between technical peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on unobvious rules that AI agents need to be reminded of
-- 🎯 KEEP CONTENT LEAN - optimize for LLM context efficiency
-- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 📝 Focus on specific, actionable rules rather than general advice
-- ⚠️ Present A/P/C menu after each major rule category
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter with completed sections
-- 🚫 FORBIDDEN to load next step until all sections are complete
-
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices for each rule category:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to explore nuanced implementation rules
-- **P (Party Mode)**: Bring multiple perspectives to identify critical edge cases
-- **C (Continue)**: Save the current rules and proceed to next category
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
-- PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
-- User accepts/rejects protocol changes before proceeding
-
-## CONTEXT BOUNDARIES:
-
-- Discovery results from step-1 are available
-- Technology stack and existing patterns are identified
-- Focus on rules that prevent implementation mistakes
-- Prioritize unobvious details that AI agents might miss
-
-## YOUR TASK:
-
-Collaboratively generate specific, critical rules that AI agents must follow when implementing code in this project.
-
-## CONTEXT GENERATION SEQUENCE:
-
-### 0. Feature-Specific Requirements Elicitation (ONLY if Technical Preference is selected)
-
-**If "Feature-Specific Technical Preference" was selected:**
-
-Before diving into standard categories, you MUST ask the user about their specific vision for this feature building upon the existing project context.
-
-Present to user:
-"Since we are creating a Technical Preference for *[Feature Name]* and we already have a General Project Context, I need you to detail the specific technical direction for this feature.
-
-Please tell me:
-1. What are the specific architectural or design patterns unique to this feature?
-2. Are there any specific libraries, APIs, or tools exclusive to this implementation?
-3. What strict rules, constraints, or 'gotchas' apply ONLY to this feature and aren't covered in the general context?
-
-Please detail these preferences as much as possible so I can build a tailored and non-redundant context for the agents."
-
-**Action:**
-1. Wait for the user's detailed reply.
-2. Analyze their response.
-3. Keep this feature-specific knowledge in your memory.
-4. During the subsequent steps (1 through 7), **ONLY** ask the user about a category and generate rules for it IF it is directly relevant to the feature-specific details they just provided. Skip categories that are entirely covered by the general project context and have no feature-specific variations.
-
----
-
-### 1. Technology Stack & Versions
-
-Document the exact technology stack from discovery:
-
-**Core Technologies:**
-Based on user skill level, present findings:
-
-**Expert Mode:**
-"Technology stack from your architecture and package files:
-{{exact_technologies_with_versions}}
-
-Any critical version constraints I should document for agents?"
-
-**Intermediate Mode:**
-"I found your technology stack:
-
-**Core Technologies:**
-{{main_technologies_with_versions}}
-
-**Key Dependencies:**
-{{important_dependencies_with_versions}}
-
-Are there any version constraints or compatibility notes agents should know about?"
-
-**Beginner Mode:**
-"Here are the technologies you're using:
-
-**Main Technologies:**
-{{friendly_description_of_tech_stack}}
-
-**Important Notes:**
-{{key_things_agents_need_to_know_about_versions}}
-
-Should I document any special version rules or compatibility requirements?"
-
-### 2. Language-Specific Rules
-
-Focus on unobvious language patterns agents might miss:
-
-**TypeScript/JavaScript Rules:**
-"Based on your codebase, I notice some specific patterns:
-
-**Configuration Requirements:**
-{{typescript_config_rules}}
-
-**Import/Export Patterns:**
-{{import_export_conventions}}
-
-**Error Handling Patterns:**
-{{error_handling_requirements}}
-
-Are these patterns correct? Any other language-specific rules agents should follow?"
-
-**Python/Ruby/Other Language Rules:**
-Adapt to the actual language in use with similar focused questions.
-
-### 3. Framework-Specific Rules
-
-Document framework-specific patterns:
-
-**React Rules (if applicable):**
-"For React development, I see these patterns:
-
-**Hooks Usage:**
-{{hooks_usage_patterns}}
-
-**Component Structure:**
-{{component_organization_rules}}
-
-**State Management:**
-{{state_management_patterns}}
-
-**Performance Rules:**
-{{performance_optimization_requirements}}
-
-Should I add any other React-specific rules?"
-
-**Other Framework Rules:**
-Adapt for Vue, Angular, Vite, Express, etc.
-
-### 4. Testing Rules
-
-Focus on testing patterns that ensure consistency:
-
-**Test Structure Rules:**
-"Your testing setup shows these patterns:
-
-**Test Organization:**
-{{test_file_organization}}
-
-**Mock Usage:**
-{{mock_patterns_and_conventions}}
-
-**Test Coverage Requirements:**
-{{coverage_expectations}}
-
-**Integration vs Unit Test Rules:**
-{{test_boundary_patterns}}
-
-Are there testing rules agents should always follow?"
-
-### 5. Code Quality & Style Rules
-
-Document critical style and quality rules:
-
-**Linting/Formatting:**
-"Your code style configuration requires:
-
-**ESLint/Prettier Rules:**
-{{specific_linting_rules}}
-
-**Code Organization:**
-{{file_and_folder_structure_rules}}
-
-**Naming Conventions:**
-{{naming_patterns_agents_must_follow}}
-
-**Documentation Requirements:**
-{{comment_and_documentation_patterns}}
-
-Any additional code quality rules?"
-
-### 6. Development Workflow Rules
-
-Document workflow patterns that affect implementation:
-
-**Git/Repository Rules:**
-"Your project uses these patterns:
-
-**Branch Naming:**
-{{branch_naming_conventions}}
-
-**Commit Message Format:**
-{{commit_message_patterns}}
-
-**PR Requirements:**
-{{pull_request_checklist}}
-
-**Deployment Patterns:**
-{{deployment_considerations}}
-
-Should I document any other workflow rules?"
-
-### 7. Critical Don't-Miss Rules
-
-Identify rules that prevent common mistakes:
-
-**Anti-Patterns to Avoid:**
-"Based on your codebase, here are critical things agents must NOT do:
-
-{{critical_anti_patterns_with_examples}}
-
-**Edge Cases:**
-{{specific_edge_cases_agents_should_handle}}
-
-**Security Rules:**
-{{security_considerations_agents_must_follow}}
-
-**Performance Gotchas:**
-{{performance_patterns_to_avoid}}
-
-Are there other 'gotchas' agents should know about?"
-
-### 8. Generate Context Content
-
-For each category, prepare lean content for the project context file:
-
-#### Content Structure:
-
-```markdown
-## Technology Stack & Versions
-
-{{concise_technology_list_with_exact_versions}}
-
-## Critical Implementation Rules
-
-### Language-Specific Rules
-
-{{bullet_points_of_critical_language_rules}}
-
-### Framework-Specific Rules
-
-{{bullet_points_of_framework_patterns}}
-
-### Testing Rules
-
-{{bullet_points_of_testing_requirements}}
-
-### Code Quality & Style Rules
-
-{{bullet_points_of_style_and_quality_rules}}
-
-### Development Workflow Rules
-
-{{bullet_points_of_workflow_patterns}}
-
-### Critical Don't-Miss Rules
-
-{{bullet_points_of_anti_patterns_and_edge_cases}}
-```
-
-### 9. Present Content and Menu
-
-After each category, show the generated rules and present choices:
-
-"I've drafted the {{category_name}} rules for your project context.
-
-**Here's what I'll add:**
-
-[Show the complete markdown content for this category]
-
-**What would you like to do?**
-[A] Advanced Elicitation - Explore nuanced rules for this category
-[P] Party Mode - Review from different implementation perspectives
-[C] Continue - Save these rules and move to next category"
-
-### 10. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
-- Execute advanced-elicitation.xml with current category rules
-- Process enhanced rules that come back
-- Ask user: "Accept these enhanced rules for {{category}}? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
-- Execute party-mode workflow with category rules context
-- Process collaborative insights on implementation patterns
-- Ask user: "Accept these changes to {{category}} rules? (y/n)"
-- If yes: Update content, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'C' (Continue):
-
-- Save the current category content to project context file
-- Update frontmatter: `sections_completed: [...]`
-- Proceed to next category or step-03 if complete
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C' for a category, append the content directly to your target `{output_file}` (either project-context.md or technical-preference.md) using the structure from step 8.
-
-## SUCCESS METRICS:
-
-✅ All critical technology versions accurately documented
-✅ Language-specific rules cover unobvious patterns
-✅ Framework rules capture project-specific conventions
-✅ Testing rules ensure consistent test quality
-✅ Code quality rules maintain project standards
-✅ Workflow rules prevent implementation conflicts
-✅ Content is lean and optimized for LLM context
-✅ A/P/C menu presented and handled correctly for each category
-
-## FAILURE MODES:
-
-❌ Including obvious rules that agents already know
-❌ Making content too verbose for LLM context efficiency
-❌ Missing critical anti-patterns or edge cases
-❌ Not getting user validation for each rule category
-❌ Not documenting exact versions and configurations
-❌ Not presenting A/P/C menu after content generation
-
-## NEXT STEP:
-
-After completing all rule categories and user selects 'C' for the final category, load `./step-03-complete.md` to finalize the project context file.
-
-Remember: Do NOT proceed to step-03 until all categories are complete and user explicitly selects 'C' for each!