sinapse-ai 7.7.11 → 8.0.1

package/squads/squad-paidmedia/README.md

@@ -0,0 +1,96 @@
+# Squad Paid Media
+
+> Squad de elite para gestao de midia paga cross-channel. Cobre Meta Ads (Facebook/Instagram), Google Ads (Search/Display/Shopping/Pmax), CRO, creative strategy, analytics de performance, YouTube Ads e creative performance analysis.
+
+## Visao Geral
+
+| Metrica | Quantidade |
+|---------|-----------|
+| Agentes | 9 |
+| Tasks | 82 |
+| Workflows | 5 |
+| Knowledge Bases | 14 |
+
+## Agentes
+
+| Agente | Papel |
+|--------|-------|
+| Apex (paidmedia-orqx) | Orquestrador — coordena pipeline de campanhas e budget cross-channel |
+| Signal (meta-ads-specialist) | Meta Ads — Facebook/Instagram campaigns, audiences, pixel/CAPI |
+| Query (google-ads-specialist) | Google Ads — Search, Display, Shopping, Pmax, bidding |
+| Pulse (campaign-analyst) | Performance — reporting, attribution, anomaly detection |
+| Canvas (creative-strategist) | Criativos — briefs, video scripts, creative testing |
+| Convert (cro-specialist) | CRO — form optimization, landing pages, A/B testing |
+| Lighthouse (performance-engineer) | Performance — Core Web Vitals, PageSpeed, tracking health |
+| Tube (pm-youtube-ads-specialist) | YouTube Ads — video ad formats, audience targeting |
+| Lens (pm-creative-performance-analyst) | Creative Performance — pattern identification, fatigue detection |
+
+## Ativacao
+
+```bash
+# Via orquestrador (recomendado)
+@paidmedia-orqx
+
+# Via agente especifico
+@meta-ads-specialist
+@google-ads-specialist
+@creative-strategist
+```
+
+## Tasks Principais
+
+**Meta Ads**
+- audit-meta-ads-account, build-audience-architecture, design-campaign-structure
+- run-creative-test, detect-creative-fatigue, manage-pixel-capi-health
+
+**Google Ads**
+- audit-google-ads-account, optimize-ad-group-structure, audit-search-terms
+- assess-smart-bidding-readiness, diagnose-conversion-tracking
+
+**Campaign Analytics**
+- analyze-traffic-sources, analyze-conversion-funnel, generate-weekly-summary
+
+**Creative Strategy**
+- generate-creative-brief, write-video-ad-script, research-competitor-facebook-ads
+- design-creative-testing-framework, analyze-creative-performance
+
+**CRO**
+- optimize-form-conversion, optimize-page-conversion, run-ab-test
+- calculate-sample-size, design-progressive-profiling
+
+**Performance**
+- audit-core-web-vitals, run-full-lighthouse-audit, audit-tracking-implementation
+
+## Workflows
+
+- **campaign-launch-cycle** — Strategy a Structure a Creative a CRO a Launch a Review
+- **account-audit-cycle** — Tracking a Structure a Performance a Creative a Recommendations
+- **scaling-sprint** — Readiness a Creative velocity a Budget progression a Monitoring
+- **creative-testing-cycle** — Hypothesis a Test design a Execution a Analysis
+- **cro-optimization-cycle** — Audit a Hypothesis a Test design a Execution a Analysis
+
+## Knowledge Bases
+
+- meta-ads-campaign-architecture
+- meta-ads-optimization-playbook
+- meta-ads-scaling-framework
+- google-ads-account-architecture
+- google-ads-optimization-playbook
+- creative-testing-framework
+- video-ad-production-guide
+- cro-conversion-optimization
+- analytics-reporting-frameworks
+- local-seo-gmb-playbook
+- competitive-ad-intelligence
+- paid-media-metrics-reference
+
+## Integracao com Core Agents
+
+Este squad trabalha com o framework SINAPSE core:
+- @architect (Aria) para decisoes tecnicas
+- @developer (Dex) para implementacao
+- @quality-gate (Quinn) para validacao de qualidade
+
+---
+
+*Parte do ecossistema SINAPSE-AI — 18 squads, 186 agentes*

package/squads/squad-product/README.md

@@ -0,0 +1,93 @@
+# Squad Product
+
+> Squad de Product Systems — orquestra discovery, delivery, analytics e product operations para agencias que constroem produtos digitais. Cada feature e validada antes de ser construida, cada lancamento e instrumentado, cada handoff e completo.
+
+## Visao Geral
+
+| Metrica | Quantidade |
+|---------|-----------|
+| Agentes | 7 |
+| Tasks | 75 |
+| Workflows | 6 |
+| Knowledge Bases | 11 |
+
+## Agentes
+
+| Agente | Papel |
+|--------|-------|
+| Vector (product-orqx) | Orquestrador — Product Operations Orchestrator |
+| Charter (ps-product-strategist) | Product Strategy & Vision Lead |
+| Quorum (ps-discovery-lead) | Product Discovery & Validation Lead |
+| Delta (ps-product-analyst) | Product Analytics & Metrics Specialist |
+| Tempo (ps-delivery-manager) | Delivery & Sprint Operations Manager |
+| Proxy (ps-client-product-manager) | Client-Facing Product Manager |
+| Mosaic (ps-product-ops-specialist) | Product Operations & Systems Specialist |
+
+## Ativacao
+
+```bash
+# Via orquestrador (recomendado)
+@product-orqx
+
+# Via agente especifico
+@ps-product-strategist
+@ps-discovery-lead
+@ps-product-analyst
+```
+
+## Tasks Principais
+
+**Product Strategy**
+- define-product-vision, create-strategy-canvas, set-product-okrs
+- evaluate-market-positioning, design-competitive-moat
+
+**Product Discovery**
+- validate-problem, run-assumption-test, conduct-opportunity-mapping
+- create-experiment-plan, map-jobs-to-be-done
+
+**Product Analytics**
+- measure-feature-adoption, track-activation-rate, calculate-retention-cohorts
+- build-product-health-dashboard, analyze-user-behavior
+
+**Delivery Management**
+- plan-sprint, manage-backlog-health, track-delivery-velocity
+- create-launch-plan, design-rollback-strategy
+
+**Client Product Management**
+- manage-client-roadmap, negotiate-scope, run-qbr
+- intake-client-request, manage-feature-expectations
+
+**Product Operations**
+- setup-product-tooling, create-process-playbook, manage-documentation
+
+## Workflows
+
+- **product-discovery-cycle** — Do problema validado ao opportunity map
+- **story-development-delivery-cycle** — Shaping, sprint planning, delivery e lancamento
+- **client-roadmap-alignment-cycle** — Alinhamento trimestral de roadmap
+- **product-launch-cycle** — Feature com tiers, flags e monitoramento
+- **product-handoff-cycle** — Handoff completo agencia a equipe do cliente
+- **product-strategy-definition-cycle** — Visao, strategy canvas e OKRs
+
+## Knowledge Bases
+
+- pm-frameworks-reference (RICE, ICE, MoSCoW, Kano)
+- product-analytics-formulas (AARRR, DAU/MAU, Activation, Retention)
+- discovery-methodology-playbook (Continuous Discovery, JTBD)
+- agile-lean-ceremonies-guide (Scrum, Kanban, Shape Up)
+- agency-product-management-patterns
+- product-led-growth-reference
+- client-stakeholder-management-protocols
+- product-tool-stack-guide
+- technical-debt-management-framework
+
+## Integracao com Core Agents
+
+Este squad trabalha com o framework SINAPSE core:
+- @architect (Aria) para decisoes tecnicas
+- @developer (Dex) para implementacao
+- @quality-gate (Quinn) para validacao de qualidade
+
+---
+
+*Parte do ecossistema SINAPSE-AI — 18 squads, 186 agentes*

package/squads/squad-research/README.md

@@ -0,0 +1,97 @@
+# Squad Research
+
+> Squad de classe mundial para pesquisa e inteligencia estrategica. 7 agentes cobrindo 100% do ciclo de investigacao: deep research, inteligencia de audiencia, analise competitiva, sizing de mercado, sintese de dados e forecasting de tendencias.
+
+## Visao Geral
+
+| Metrica | Quantidade |
+|---------|-----------|
+| Agentes | 7 |
+| Tasks | 72 |
+| Workflows | 6 |
+| Knowledge Bases | 13 |
+
+## Agentes
+
+| Agente | Papel |
+|--------|-------|
+| Prism (research-orqx) | Orquestrador — Research Operations Conductor |
+| Sage (deep-researcher) | Deep Research Scholar — pesquisa multi-fonte |
+| Pulse (audience-intelligence) | Audience Intelligence Empath — personas, JTBD |
+| Hawk (competitive-intelligence) | Competitive Intelligence Sentinel — analise competitiva |
+| Scope (market-analyst) | Market Analysis Strategist — TAM/SAM/SOM, tendencias |
+| Loom (data-synthesizer) | Data Synthesis Weaver — sintese e narrativa de dados |
+| Horizon (trend-forecaster) | Trend Forecasting Oracle — cenarios e sinais fracos |
+
+## Ativacao
+
+```bash
+# Via orquestrador (recomendado)
+@research-orqx
+
+# Via agente especifico
+@deep-researcher
+@competitive-intelligence
+@audience-intelligence
+```
+
+## Tasks Principais
+
+**Deep Research**
+- conduct-deep-research, conduct-rapid-scan, synthesize-multi-source
+- validate-research-sources, create-research-dossier, generate-hypothesis
+
+**Audience Intelligence**
+- build-audience-persona, map-audience-journey, analyze-audience-psychographics
+- conduct-jobs-to-be-done, map-pain-gain-matrix, design-survey
+
+**Competitive Intelligence**
+- map-competitive-landscape, analyze-competitor-positioning, monitor-competitor-movements
+- create-battle-card, run-porter-five-forces
+
+**Market Analysis**
+- size-market-tam-sam-som, analyze-industry-trends, map-market-opportunity
+- evaluate-market-entry, forecast-market-growth
+
+**Data Synthesis**
+- synthesize-research-report, create-executive-briefing, build-data-narrative
+- create-swot-analysis, generate-actionable-recommendations
+
+**Trend Forecasting**
+- forecast-industry-trends, detect-weak-signals, run-scenario-planning
+- identify-inflection-points, track-emerging-technologies
+
+## Workflows
+
+- **deep-research-cycle** — Brief a pesquisa a sintese a entrega
+- **audience-intelligence-cycle** — Inteligencia de audiencia completa
+- **competitive-intelligence-cycle** — Analise competitiva completa
+- **market-analysis-cycle** — Sizing de mercado e oportunidade
+- **trend-forecasting-cycle** — Deteccao de tendencias e cenarios
+- **onboarding-research-cycle** — Setup de pesquisa para novo cliente
+
+## Knowledge Bases
+
+- research-depth-pyramid (4 niveis de profundidade)
+- insight-crystallization-engine (FINDING + IMPLICATION + RECOMMENDATION)
+- source-credibility-matrix (5 tiers)
+- research-frameworks-encyclopedia (SWOT, PESTEL, Porter, BCG)
+- audience-research-methods
+- competitive-analysis-frameworks
+- market-sizing-methods (TAM/SAM/SOM)
+- cognitive-bias-awareness
+- data-visualization-principles
+- scenario-planning-methods
+- survey-design-principles
+- cross-squad-integration-protocol
+
+## Integracao com Core Agents
+
+Este squad trabalha com o framework SINAPSE core:
+- @architect (Aria) para decisoes tecnicas
+- @developer (Dex) para implementacao
+- @quality-gate (Quinn) para validacao de qualidade
+
+---
+
+*Parte do ecossistema SINAPSE-AI — 18 squads, 186 agentes*

package/squads/squad-storytelling/README.md

@@ -0,0 +1,96 @@
+# Squad Storytelling
+
+> Squad de 10 mestres da narrativa. Mitologia, screenwriting, pitch, apresentacoes, storytelling pessoal, business storytelling, improviso e movimentos sociais. Frameworks de Campbell, Harmon, Snyder, Klaff, Duarte, Hall, Howell, Johnstone e Ganz reunidos sob um unico orquestrador.
+
+## Visao Geral
+
+| Metrica | Quantidade |
+|---------|-----------|
+| Agentes | 10 |
+| Tasks | 47 |
+| Workflows | 2 |
+| Knowledge Bases | 3 |
+
+## Agentes
+
+| Agente | Papel |
+|--------|-------|
+| Arc (storytelling-orqx) | Orquestrador — routing e diagnostico narrativo |
+| Joseph Campbell | Monomyth & Mythology — Hero's Journey, 17 stages, archetypes |
+| Dan Harmon | Story Circle & TV Writing — 8 steps, fractal narrative |
+| Blake Snyder | Save the Cat & Screenwriting — 15 beats, 10 genres |
+| Oren Klaff | Pitch Anything & Frame Control — STRONG method, neurofinance |
+| Nancy Duarte | Sparkline & Presentations — STAR moment, audience as hero |
+| Kindra Hall | Stories That Stick & Business — 4 story types, Story Gap |
+| Park Howell | ABT & Brand Storytelling — Story Cycle System |
+| Keith Johnstone | Impro & Status — status transactions, Theatresports |
+| Marshall Ganz | Public Narrative & Movements — Story of Self/Us/Now |
+
+## Ativacao
+
+```bash
+# Via orquestrador (recomendado)
+@storytelling-orqx
+
+# Via agente especifico
+@joseph-campbell
+@oren-klaff
+@nancy-duarte
+```
+
+## Tasks Principais
+
+**Orquestracao**
+- diagnose-narrative, review-narrative-output
+
+**Mythology e Hero's Journey (Campbell)**
+- map-heros-journey, identify-archetypes, brand-origin-story
+- customer-journey-narrative, transformation-arc-design
+
+**Story Circle (Harmon)**
+- build-story-circle, structure-episode, content-series-story-circle
+- product-launch-narrative, community-narrative-design
+
+**Screenwriting (Snyder)**
+- create-beat-sheet, craft-logline, video-script-beat-sheet
+- case-study-beat-structure, landing-page-story-beats
+
+**Pitch e Frame Control (Klaff)**
+- create-pitch, design-frame-control, investor-pitch-deck
+- sales-presentation-frames, partnership-pitch-narrative
+
+**Apresentacoes (Duarte)**
+- create-presentation, design-datastory, keynote-presentation-design
+- data-storytelling-presentation, internal-change-presentation
+
+**Business Storytelling (Hall, Howell)**
+- build-business-stories, close-story-gap, brand-storytelling-strategy
+- build-brand-narrative, email-sequence-storytelling
+
+**Impro e Status (Johnstone)**
+- unblock-creative, improvised-content-creation, status-dynamics-negotiation
+
+**Movimentos Sociais (Ganz)**
+- write-manifesto, movement-building-narrative, advocacy-campaign-story
+
+## Workflows
+
+- **story-development-cycle** — Ciclo completo de desenvolvimento narrativo
+- **pitch-narrative-workflow** — Construcao de pitch com frame control
+
+## Knowledge Bases
+
+- routing-catalog
+- narrative-frameworks-catalog
+- story-structure-reference
+
+## Integracao com Core Agents
+
+Este squad trabalha com o framework SINAPSE core:
+- @architect (Aria) para decisoes tecnicas
+- @developer (Dex) para implementacao
+- @quality-gate (Quinn) para validacao de qualidade
+
+---
+
+*Parte do ecossistema SINAPSE-AI — 18 squads, 186 agentes*

package/docs/FEATURE_PROCESS.md

@@ -1,93 +0,0 @@
-# Feature Request Process
-
-> 🌐 **EN** | [PT](./pt/FEATURE_PROCESS.md) | [ES](./es/FEATURE_PROCESS.md)
-
----
-
-This document explains how to propose new features for SINAPSE.
-
-## Quick Ideas
-
-For quick ideas or small improvements:
-
-1. Open a Discussion in the "Ideas" category
-2. Describe the problem and proposed solution
-3. Community and maintainers will discuss
-4. If there's interest, it may be promoted to RFC
-
-## RFC Process (For Significant Features)
-
-For larger features that require design decisions:
-
-### When to Write an RFC
-
-- New major features
-- Breaking changes
-- Significant architectural changes
-- Changes affecting many users
-
-### RFC Lifecycle
-
-1. **Draft**: Author writes RFC using our [RFC Template](../.github/RFC_TEMPLATE.md)
-2. **Under Review**: 2-week comment period
-3. **Decision**: Maintainers accept/reject
-4. **Implementation**: If accepted, implementation begins
-
-### Criteria for Acceptance
-
-- Aligns with project vision
-- Technically feasible
-- Has clear implementation path
-- Community demand demonstrated
-- Maintainable long-term
-
-## Voting
-
-- Use :+1: reactions to show support
-- Top-voted ideas are prioritized
-- Maintainers have final decision
-
-## Timeline
-
-- Ideas: No fixed timeline
-- RFCs: 2-week minimum review period
-- Implementation: Based on roadmap capacity
-
-## From Idea to Implementation
-
-```text
-Community Idea (Discussion)
-        │
-        │ [Approved by maintainers]
-        ▼
-Internal Backlog Item
-        │
-        │ [Prioritized by Product Owner]
-        ▼
-Sprint Planning
-        │
-        │ [Implemented by Development Team]
-        ▼
-Release (credited in CHANGELOG.md)
-```
-
-### Who Can Add to Backlog?
-
-The Product Owner (@product-lead) is the sole authority for adding items to the internal backlog.
-This ensures proper prioritization and alignment with project goals.
-
-### Contributor Credit
-
-Contributors whose ideas are implemented will be credited in:
-
-- The CHANGELOG.md release notes
-- The PR that implements the feature
-- Our contributors page (if applicable)
-
-## Questions?
-
-Ask in GitHub Discussions or Discord.
-
----
-
-_See also: [Community Handbook](../COMMUNITY.md) | [Contributing Guide](../CONTRIBUTING.md)_

package/docs/GUIDING-PRINCIPLES.md

@@ -1,95 +0,0 @@
-# SINAPSE Method Guiding Principles
-
-> 🌐 **EN** | [PT](./pt/GUIDING-PRINCIPLES.md) | [ES](./es/GUIDING-PRINCIPLES.md)
-
----
-
-The SINAPSE Method is a natural language framework for AI-assisted software development. These principles ensure contributions maintain the method's effectiveness.
-
-## Core Principles
-
-### 1. Dev Agents Must Be Lean
-
-- **Minimize dev agent dependencies**: Development agents that work in IDEs must have minimal context overhead
-- **Save context for code**: Every line counts - dev agents should focus on coding, not documentation
-- **Web agents can be larger**: Planning agents (PRD Writer, Architect) used in web UI can have more complex tasks and dependencies
-- **Small files, loaded on demand**: Multiple small, focused files are better than large files with many branches
-
-### 2. Natural Language First
-
-- **Everything is markdown**: Agents, tasks, templates - all written in plain English
-- **No code in core**: The framework itself contains no programming code, only natural language instructions
-- **Self-contained templates**: Templates are defined as YAML files with structured sections that include metadata, workflow configuration, and detailed instructions for content generation
-
-### 3. Agent and Task Design
-
-- **Agents define roles**: Each agent is a persona with specific expertise (e.g., Frontend Developer, API Developer)
-- **Tasks are procedures**: Step-by-step instructions an agent follows to complete work
-- **Templates are outputs**: Structured documents with embedded instructions for generation
-- **Dependencies matter**: Explicitly declare only what's needed
-
-## Practical Guidelines
-
-### When to Add to Core
-
-- Universal software development needs only
-- Doesn't bloat dev agent contexts
-- Follows existing agent/task/template patterns
-
-### When to Create Squads
-
-- Domain-specific needs beyond software development
-- Non-technical domains (business, wellness, education, creative)
-- Specialized technical domains (games, infrastructure, mobile)
-- Heavy documentation or knowledge bases
-- Anything that would bloat core agents
-
-See [Squads Overview](./guides/squads-overview.md) for detailed examples and ideas.
-
-### Agent Design Rules
-
-1. **Web/Planning Agents**: Can have richer context, multiple tasks, extensive templates
-2. **Dev Agents**: Minimal dependencies, focused on code generation, lean task sets
-3. **All Agents**: Clear persona, specific expertise, well-defined capabilities
-
-### Task Writing Rules
-
-1. Write clear step-by-step procedures
-2. Use markdown formatting for readability
-3. Keep dev agent tasks focused and concise
-4. Planning tasks can be more elaborate
-5. **Prefer multiple small tasks over one large branching task**
-   - Instead of one task with many conditional paths
-   - Create multiple focused tasks the agent can choose from
-   - This keeps context overhead minimal
-6. **Reuse common tasks** - Don't create new document creation tasks
-   - Use the existing `create-doc` task
-   - Pass the appropriate YAML template with structured sections
-   - This maintains consistency and reduces duplication
-
-### Template Rules
-
-Templates follow the [SINAPSE Document Template](../common/utils/sinapse-doc-template.md) specification using YAML format:
-
-1. **Structure**: Templates are defined in YAML with clear metadata, workflow configuration, and section hierarchy
-2. **Separation of Concerns**: Instructions for LLMs are in `instruction` fields, separate from content
-3. **Reusability**: Templates are agent-agnostic and can be used across different agents
-4. **Key Components**:
-   - `template` block for metadata (id, name, version, output settings)
-   - `workflow` block for interaction mode configuration
-   - `sections` array defining document structure with nested subsections
-   - Each section has `id`, `title`, and `instruction` fields
-5. **Advanced Features**:
-   - Variable substitution using `{{variable_name}}` syntax
-   - Conditional sections with `condition` field
-   - Repeatable sections with `repeatable: true`
-   - Agent permissions with `owner` and `editors` fields
-   - Examples arrays for guidance (never included in output)
-6. **Clean Output**: YAML structure ensures all processing logic stays separate from generated content
-
-## Remember
-
-- The power is in natural language orchestration, not code
-- Dev agents code, planning agents plan
-- Keep dev agents lean for maximum coding efficiency
-- Starter squads handle specialized domains