@onion-ai/cli 1.0.0-beta.1

package/framework/commands/docs/build-business-docs.md

@@ -0,0 +1,299 @@
+---
+name: build-business-docs
+description: Generate business context and strategy documentation.
+model: sonnet
+category: docs
+tags: [business, strategy, documentation]
+version: '3.0.0'
+updated: '2025-11-24'
+---
+
+# Business Context Generator
+
+You are a business analyst and product strategist specialized in creating comprehensive, AI-optimized business intelligence. Your mission is to analyze a project/product and generate a complete business context architecture using the multi-file approach that enables AI systems to understand customers, market dynamics, and business strategy.
+
+## Primary Objective
+
+Generate a complete business context architecture following the template in `.claude/commands/common/templates/business_context_template.md`. Create a modular, multi-file documentation structure that enables AI systems to provide contextually appropriate customer support, sales assistance, and strategic business insights.
+
+## Input Parameters
+
+**Required Arguments:**
+You must receive links to files, repositories, and other source materials to generate the business documentation. These will be placed in your arguments. If you have not received arguments, you must request them before proceeding.
+
+<arguments>
+#$ARGUMENTS
+</arguments>
+
+## Analysis Framework
+
+### Phase 1: Product Discovery
+
+1. **Product Understanding**
+   - Analyze README, product descriptions, and marketing materials
+   - Extract value proposition from landing pages, documentation, and positioning
+   - Identify target market from feature set and messaging
+   - Understand business model from pricing pages, monetization strategy, and revenue streams
+
+2. **Market Research**
+   - Research competitive landscape through web searches and analysis (use Perplexity or other web search tools)
+   - Identify industry trends and market dynamics
+   - Analyze customer segments and use cases
+   - Study regulatory environment and compliance requirements
+
+3. **Customer Intelligence Gathering**
+   - Analyze customer feedback from GitHub issues, support tickets, reviews
+   - Extract customer personas from user behavior and feature usage
+   - Map customer journey from onboarding flows and user experience
+   - Identify communication patterns and preferences from support interactions
+
+### Phase 2: User Discussion
+
+After building a solid understanding of the project, you will ask the human a series of questions to clarify doubts or missing information. Plan to ask at least 10 questions that cover most strategic areas in the documentation. Be selective about the questions you ask, and try to avoid questions that are not relevant to the project.
+
+- Identify the product vision
+- Identify key user personas
+- Identify main competitors and why this is different
+- Who are the key stakeholders
+- What are the main features
+- What are the main workflows
+- What are the key metrics
+- What are the main challenges
+- What are the main opportunities
+- What are the main risks
+- What are the main dependencies
+- What are the main constraints
+
+Conduct multiple rounds of questions and answers if you feel you still need to gather more information.
+When ready, give the human a summary of the most important points detected and ask for approval to proceed to Phase 3.
+
+### Phase 3: Business Context Generation
+
+Follow the multi-file structure from the business template:
+
+#### Create Index File (`index.md`)
+
+```markdown
+## Business Context Profile
+
+[Company foundation, product information, scale and metrics]
+
+## Layer 1: Customer Context Architecture
+
+- [Customer Personas](CUSTOMER_PERSONAS.md)
+- [Customer Journey](CUSTOMER_JOURNEY.md)
+- [Voice of Customer](VOICE_OF_CUSTOMER.md)
+
+## Layer 2: Product Context Architecture
+
+- [Product Strategy](PRODUCT_STRATEGY.md)
+- [Feature Catalog](features/)
+- [Product Metrics](PRODUCT_METRICS.md)
+
+## Layer 3: Market and Competitive Context
+
+- [Competitive Landscape](COMPETITIVE_LANDSCAPE.md)
+- [Industry Trends](INDUSTRY_TRENDS.md)
+
+## Layer 4: Operational Business Context
+
+- [Sales Process](SALES_PROCESS.md)
+- [Messaging Framework](MESSAGING_FRAMEWORK.md)
+- [Customer Communication Guidelines](CUSTOMER_COMMUNICATION.md)
+```
+
+#### Generate Individual Files
+
+**1. `CUSTOMER_PERSONAS.md`**
+
+- Research and define primary customer personas based on:
+  - User feedback analysis from GitHub issues, reviews, testimonials
+  - Feature usage patterns and technical requirements
+  - Industry context and typical user profiles
+  - Communication patterns in support channels
+- Include demographics, goals, pain points, technology context, and AI interaction notes
+- Create both primary user personas and decision-maker personas when applicable
+
+**2. `CUSTOMER_JOURNEY.md`**
+
+- Map the complete customer lifecycle from:
+  - Onboarding flows and getting-started guides
+  - Feature adoption patterns and user progression
+  - Support ticket patterns and common confusion points
+  - Community feedback and advocacy indicators
+- Include awareness, evaluation, adoption, growth, and advocacy/churn patterns
+- Document trigger events, decision criteria, and success milestones
+
+**3. `VOICE_OF_CUSTOMER.md`**
+
+- Extract customer feedback patterns from:
+  - GitHub issues, discussions, and community forums
+  - Product reviews and testimonials
+  - Support ticket analysis and common requests
+  - Social media mentions and community discussions
+- Document praise themes, frequent requests, competitive comparisons
+- Identify customer language, terminology preferences, and communication patterns
+
+**4. `PRODUCT_STRATEGY.md`**
+
+- Synthesize product strategy from:
+  - Mission statements, vision documents, and strategic materials
+  - Roadmap analysis and development priorities
+  - Competitive positioning and differentiation
+  - Market opportunity and strategic focus areas
+- Include vision/mission, market position, strategic priorities, and product principles
+- Document trade-off frameworks and quality standards
+
+**5. `features/` Directory**
+
+- Create individual feature files for each product feature with:
+  - Purpose analysis and user benefit
+  - Usage pattern identification from documentation and user feedback
+  - Success metrics and performance indicators
+  - Common issues and limitations from support data
+  - AI interaction guidance for each feature
+- Organize by core features, advanced features, and integration capabilities
+- Name files descriptively (e.g., `user-authentication.md`, `data-export.md`, `api-integration.md`)
+
+**6. `PRODUCT_METRICS.md`**
+
+- Document key performance indicators:
+  - Adoption metrics (downloads, stars, usage statistics)
+  - Quality metrics (test coverage, performance benchmarks, issue resolution)
+  - Feature performance (high-performing vs underperforming features)
+  - Usage correlation patterns and success indicators
+- Focus on metrics that indicate product health and market success
+
+**7. `COMPETITIVE_LANDSCAPE.md`**
+
+- Research and analyze direct competitors:
+  - Competitive strengths, weaknesses, and positioning
+  - Pricing strategies and business models
+  - Customer overlap and differentiation strategies
+  - Win/loss scenarios and competitive messaging
+- Include competitive positioning framework and objection handling
+
+**8. `INDUSTRY_TRENDS.md`**
+
+- Analyze market evolution and trends:
+  - Industry landscape and evolution patterns
+  - Technology trends affecting the market
+  - Regulatory environment and compliance requirements
+  - Future predictions and strategic implications
+- Focus on trends that affect product strategy and customer needs
+
+**9. `SALES_PROCESS.md`**
+(if relevant)
+
+- Document customer acquisition strategy:
+  - For B2B products: Sales methodology, qualification criteria, common objections
+  - For Open Source: Community building, contribution workflows, monetization strategy
+  - For B2C: User acquisition, conversion funnels, retention strategies
+- Include customer success patterns and expansion opportunities
+
+**10. `MESSAGING_FRAMEWORK.md`**
+
+- Define brand voice and messaging:
+  - Brand personality and tone guidelines
+  - Core messaging and value propositions
+  - Audience-specific messaging strategies
+  - Content guidelines and communication style
+- Ensure messaging aligns with customer preferences and market positioning
+
+**11. `CUSTOMER_COMMUNICATION.md`**
+
+- Create AI interaction guidelines:
+  - Communication principles and objectives
+  - Response guidelines for different scenarios
+  - Escalation triggers and privacy considerations
+  - Personalization strategies and relationship building approaches
+- Tailor guidelines to the specific customer base and communication channels
+
+## Sources and Research Methods
+
+### Primary Sources
+
+- **Product Documentation**: README files, official documentation, API docs
+- **Customer Feedback**: GitHub issues, reviews, testimonials, support tickets
+- **Marketing Materials**: Website copy, landing pages, blog posts, case studies
+- **Community Channels**: Forums, Discord, Slack communities, social media
+- **Competitive Intelligence**: Competitor websites, documentation, user feedback
+
+### Research Techniques
+
+- **Web Search Analysis**: Research competitors, market trends, and industry insights
+- **Content Analysis**: Extract insights from existing documentation and communications
+- **Pattern Recognition**: Identify trends in customer feedback and behavior
+- **Competitive Research**: Analyze competitor positioning and customer reception
+- **Market Intelligence**: Gather industry trends and regulatory information
+
+## Quality Assurance
+
+### Content Accuracy
+
+- [ ] All customer insights are based on actual feedback and data
+- [ ] Competitive analysis includes current, verifiable information
+- [ ] Product features and capabilities are accurately represented
+- [ ] Market trends are supported by research and evidence
+- [ ] Business model and strategy align with actual company direction
+
+### AI Optimization
+
+- [ ] Content enables AI to provide contextually appropriate customer support
+- [ ] Customer personas include specific AI interaction guidelines
+- [ ] Communication guidelines are actionable for AI systems
+- [ ] Business context is structured for AI decision-making support
+- [ ] Cross-references create comprehensive business intelligence
+
+### Completeness Validation
+
+- [ ] All business context layers are thoroughly addressed
+- [ ] Customer journey covers full lifecycle from awareness to advocacy
+- [ ] Competitive landscape includes direct and indirect competitors
+- [ ] Product strategy aligns with actual market positioning
+- [ ] Communication guidelines match customer preferences
+
+## Execution Strategy
+
+1. **Customer-First Research**: Start with deep customer understanding before strategy
+2. **Evidence-Based Insights**: Ground all business intelligence in real data and feedback
+3. **Multi-File Architecture**: Always create linked, focused files for each business area
+4. **AI-Optimized Structure**: Organize information for AI consumption and decision-support
+5. **Market-Informed Strategy**: Ensure all business context reflects current market realities
+6. **Cross-Functional Integration**: Connect business context with technical implementation
+
+## Output Success Criteria
+
+The generated business documentation should enable:
+
+- **AI-powered customer support** to provide contextually appropriate assistance
+- **Sales and marketing teams** to align messaging with customer needs and market position
+- **Product decisions** to be made with full customer and market context
+- **Strategic planning** to leverage comprehensive competitive and market intelligence
+- **Customer communication** to be consistent with brand voice and customer preferences
+
+## Adaptation Guidelines
+
+### For Different Business Models
+
+- **B2B SaaS**: Emphasize enterprise sales, customer success, and competitive differentiation
+- **Open Source**: Focus on community building, contributor engagement, and monetization strategy
+- **B2C Products**: Highlight user experience, conversion optimization, and retention strategies
+- **Developer Tools**: Prioritize technical accuracy, developer experience, and ecosystem integration
+
+### For Different Company Stages
+
+- **Early Stage**: Focus on customer discovery, market validation, and product-market fit
+- **Growth Stage**: Emphasize scaling strategies, competitive positioning, and market expansion
+- **Enterprise Stage**: Include comprehensive competitive analysis, compliance, and strategic partnerships
+
+## Error Handling and Gaps
+
+When information cannot be determined:
+
+- Mark sections as "RESEARCH NEEDED" with specific data requirements
+- Provide frameworks for gathering missing information
+- Create hypotheses based on available data with clear validation steps
+- Reference industry standards and best practices as interim guidance
+
+Remember: The goal is to create actionable business intelligence that enables AI systems to understand customers, market dynamics, and strategic context to provide superior business support and decision-making assistance.

package/framework/commands/docs/build-compliance-docs.md

@@ -0,0 +1,143 @@
+---
+name: build-compliance-docs
+description: |
+  Geração de documentação de compliance (ISO 27001, SOC2, etc).
+  Use para preparar auditorias, Due Diligence e certificações.
+model: sonnet
+
+parameters:
+  - name: frameworks
+    description: Frameworks (iso27001,soc2,iso22301,pmbok ou all)
+    required: false
+  - name: due_diligence
+    description: Caminho para checklist de DD
+    required: false
+
+category: docs
+tags:
+  - compliance
+  - security
+  - audit
+
+version: "3.0.0"
+updated: "2025-11-24"
+
+related_commands:
+  - /docs/build-tech-docs
+  - /docs/build-business-docs
+
+related_agents:
+  - security-information-master
+  - iso-27001-specialist
+  - soc2-specialist
+---
+
+# 📋 Gerador de Documentação de Compliance
+
+Criar documentação de conformidade para auditorias e certificações.
+
+## 🎯 Objetivo
+
+Gerar arquitetura completa de docs de compliance multi-framework.
+
+## 🔧 Modos de Execução
+
+```bash
+# Modo 1: Seletivo
+/docs/build-compliance-docs frameworks="iso27001,soc2"
+
+# Modo 2: Due Diligence
+/docs/build-compliance-docs due_diligence="path/to/checklist.md"
+
+# Modo 3: Auto (analisa projeto)
+/docs/build-compliance-docs
+
+# Modo 4: Completo
+/docs/build-compliance-docs frameworks="all"
+```
+
+## ⚡ Fluxo de Execução
+
+### Passo 1: Detectar Modo
+
+SE `{{frameworks}}` → Modo Seletivo
+SE `{{due_diligence}}` → Modo DD (analisar checklist)
+SENÃO → Modo Auto (analisar projeto)
+
+### Passo 2: Selecionar Frameworks
+
+| Framework | Foco | Quando Usar |
+|-----------|------|-------------|
+| ISO 27001 | Segurança da Info | Certificação, DD |
+| ISO 22301 | Continuidade | DR, BCP |
+| SOC2 | Trust Services | Clientes enterprise |
+| PMBOK | Governança | Projetos |
+
+### Passo 3: Delegar para Especialistas
+
+Para cada framework selecionado:
+
+```
+SE "iso27001" → @iso-27001-specialist
+SE "iso22301" → @iso-22301-specialist
+SE "soc2" → @soc2-specialist
+SE "pmbok" → @pmbok-specialist
+```
+
+Coordenação via @security-information-master
+
+### Passo 4: Gerar Documentação
+
+Estrutura de saída:
+```
+docs/compliance/
+├── index.md
+├── iso27001/
+│   ├── policy.md
+│   ├── risk-assessment.md
+│   └── controls.md
+├── soc2/
+│   ├── trust-services.md
+│   └── evidence.md
+└── reports/
+    └── summary.md
+```
+
+### Passo 5: Validar e Entregar
+
+## 📤 Output Esperado
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ DOCS DE COMPLIANCE GERADOS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+📊 Frameworks:
+∟ ISO 27001: ✅ 12 documentos
+∟ SOC2: ✅ 8 documentos
+
+📁 Estrutura:
+∟ docs/compliance/index.md
+∟ docs/compliance/iso27001/ (12)
+∟ docs/compliance/soc2/ (8)
+
+📋 Cobertura:
+∟ Políticas: 100%
+∟ Controles: 85%
+∟ Evidências: Template
+
+🚀 Próximo: Revisar e customizar
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+## 🔗 Referências
+
+- Orquestrador: @security-information-master
+- ISO 27001: @iso-27001-specialist
+- SOC2: @soc2-specialist
+
+## ⚠️ Notas
+
+- Docs gerados são templates base
+- Customizar para contexto específico
+- Revisar antes de auditorias

package/framework/commands/docs/build-index.md

@@ -0,0 +1,119 @@
+---
+name: build-index
+description: Gerenciar e atualizar índices de documentação.
+model: sonnet
+category: docs
+tags: [index, navigation, documentation]
+version: '3.0.0'
+updated: '2025-11-24'
+---
+
+Este comando gerencia os índices de documentação do {ProjectName}, mantendo a estrutura organizada e navegável.
+
+**Estrutura de Documentação do {ProjectName}**:
+
+```
+docs/
+├── INDEX.md                    # Índice principal (hub central)
+├── business-context/           # Contexto de negócio (15 arquivos)
+│   └── index.md
+├── technical-context/          # Contexto técnico (15 arquivos)
+│   └── index.md
+├── compliance/                 # Compliance e Governança (18 arquivos) ✨ NOVO
+│   ├── index.md
+│   ├── security/               # ISO 27001 (3 arquivos)
+│   ├── business-continuity/    # ISO 22301 (5 arquivos)
+│   ├── soc2/                   # SOC2 Type II (4 arquivos)
+│   ├── ai-governance/          # AI Governance (1 arquivo)
+│   ├── privacy/                # LGPD (1 arquivo)
+│   └── due-diligence/          # Due Diligence (4 arquivos)
+├── onion/                      # Sistema Onion (22 arquivos)
+├── guidelines/                 # Guidelines de desenvolvimento (4 arquivos)
+└── files/                      # Recursos diversos
+
+.claude/
+├── commands/                   # 59 comandos organizados por categoria
+│   ├── docs/                   # Comandos de documentação
+│   ├── engineer/               # Workflows de desenvolvimento
+│   ├── collect/                # Coleta de informações
+│   └── check/                  # Validações e compliance
+└── agents/                     # 27 agentes especializados de IA
+    ├── *.md                    # 12 agentes gerais
+    ├── development/            # 10 agentes especializados dev
+    └── compliance/             # 5 agentes compliance ✨ NOVO
+```
+
+## Usage
+
+### /docs/build-index
+
+**Sem argumentos**: Reconstrói o arquivo `INDEX.md` principal na pasta `@/docs/`.
+
+Este índice central fornece:
+
+- Visão geral do projeto {ProjectName}
+- Links para todas as seções de documentação
+- Descrição de cada seção
+- Estatísticas da documentação (80 arquivos, 59 comandos, 27 agentes)
+- Guias de navegação por perfil (dev, PM, vendas, arquitetos, CISO/Compliance)
+- Mapa de navegação rápida
+- Referência completa aos 27 agentes especializados em `.claude/agents/`
+- Métricas de maturidade de compliance (ISO 27001, ISO 22301, SOC2, LGPD)
+
+**Comportamento**:
+
+1. Escaneia todas as pastas em `@/docs/`
+2. Lê os arquivos `index.md` de cada seção
+3. Escaneia `.claude/commands/` e `.claude/agents/` para contar recursos
+4. Extrai informações relevantes (título, descrição, arquivos principais)
+5. Gera/atualiza `docs/INDEX.md` com estrutura completa
+6. Mantém estatísticas atualizadas:
+   - 80 arquivos markdown (+2 README.md landing pages)
+   - 59 comandos Cursor
+   - 27 agentes IA (12 gerais + 10 development + 5 compliance)
+   - 15 arquivos business-context
+   - 16 arquivos technical-context
+   - 19 arquivos compliance ✨ NOVO
+   - 22 arquivos onion
+   - 4 arquivos guidelines
+7. Gera métricas de maturidade de compliance:
+   - ISO 27001:2022 (84% implementado)
+   - ISO 22301:2019 (100% implementado)
+   - SOC2 Type II (93% readiness)
+   - LGPD (95% compliant)
+   - AI Governance (100% documentado)
+
+### /docs/build-index <section-name>
+
+**Com argumento**: Reconstrói o índice de uma seção específica da documentação.
+
+**Seções disponíveis**:
+
+- `business-context` - Documentação de negócio
+- `technical-context` - Documentação técnica
+- `compliance` - Compliance e Governança (ISO 27001, ISO 22301, SOC2, LGPD) ✨ NOVO
+- `onion` - Sistema Onion (comandos e agentes)
+- `guidelines` - Guidelines de desenvolvimento
+
+**Comportamento**:
+
+1. Percorre a estrutura de arquivos da seção especificada
+2. Identifica arquivos principais e subpastas
+3. Gera/atualiza o `index.md` da seção
+4. Mantém links relativos corretos
+5. Preserva estrutura e organização
+
+**Exemplo**:
+
+```bash
+/docs/build-index business-context
+# Reconstrói docs/business-context/index.md
+
+/docs/build-index technical-context
+# Reconstrói docs/technical-context/index.md
+
+/docs/build-index compliance
+# Reconstrói docs/compliance/index.md
+```
+
+Argumentos fornecidos: #$ARGUMENTS