ganbatte-os 0.2.1

package/squads/design-squad/tasks/setup-design-ops.md

@@ -0,0 +1,177 @@
+---
+task: setupDesignOps()
+responsavel: "@dave-malouf"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: true
+
+Entrada:
+  - campo: team_context
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+  - campo: current_pain_points
+    tipo: string
+    origem: User Input
+    obrigatorio: true
+
+Saida:
+  - campo: designOpsPractice
+    tipo: string
+    destino: Console
+    persistido: false
+
+Checklist:
+  - "[ ] Current state assessed with bottlenecks identified"
+  - "[ ] Design workflow defined with stages, activities, and gates"
+  - "[ ] Metrics defined for ongoing health tracking"
+---
+
+# Task: DesignOps Practice Setup
+
+**Task ID:** DESIGN-003
+**Version:** 1.0.0
+**Command:** `*setup-design-ops`
+**Agent:** Dave Malouf (dave-malouf)
+**Purpose:** Establish a DesignOps practice to scale design quality and team effectiveness.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `team_context` | Design team size, structure, maturity | YES |
+| `current_pain_points` | Biggest operational challenges | YES |
+| `tools_in_use` | Current design and collaboration tools | PREFERRED |
+| `engineering_workflow` | How dev team works (agile, kanban, etc.) | PREFERRED |
+| `budget_constraints` | Available budget for tools/hires | NO |
+
+## Preconditions
+
+1. Design team exists (even if small)
+2. Pain points are identified and acknowledged
+3. Leadership buy-in for improving design operations
+
+## Execution Phases
+
+### Phase 1: Assess Current State
+
+1. Map the current design workflow from brief to shipped product
+2. Identify bottlenecks — where does work get stuck or delayed?
+3. Assess tool landscape — are tools consistent? Redundant? Missing?
+4. Evaluate handoff quality — how well do designs translate to code?
+5. Review meeting and ceremony structure — are design reviews happening?
+6. Assess design documentation practices — is institutional knowledge captured?
+7. Interview/survey the team — what do they need most?
+
+### Phase 2: Design Workflow
+
+1. Define the design workflow stages:
+   - **Discover** — Research, user insights, problem framing
+   - **Define** — Requirements, constraints, success criteria
+   - **Design** — Exploration, iteration, refinement
+   - **Deliver** — Handoff, QA, implementation support
+   - **Measure** — Post-launch analysis, iteration planning
+2. For each stage, define:
+   - Inputs required (what must exist before starting)
+   - Activities (what happens during this stage)
+   - Outputs produced (what must exist before moving forward)
+   - Review gates (who reviews and what criteria)
+3. Map the workflow to the engineering process — where do they intersect?
+4. Define design sprint cadence — how long is a design cycle?
+5. Establish critique and review rituals:
+   - Design critique (weekly, peers)
+   - Design review (per milestone, stakeholders)
+   - Design QA (pre-ship, designer + engineer)
+
+### Phase 3: Define People Ops
+
+1. **Role Definitions** — Clear expectations for each design role
+   - UX Designer, UI Designer, Design System Engineer, UX Researcher, Design Lead
+2. **Career Framework** — Growth paths for designers
+   - IC track: Junior → Mid → Senior → Staff → Principal
+   - Management track: Lead → Manager → Director → VP
+3. **Skill Matrix** — Competencies expected at each level
+4. **Onboarding** — How new designers get up to speed
+   - Tool setup guide
+   - Design system introduction
+   - Team norms and rituals
+   - First-week, first-month milestones
+5. **Knowledge Management** — How design decisions and rationale are documented
+   - Decision records for major design choices
+   - Pattern documentation for reusable solutions
+   - Research repository for user insights
+
+### Phase 4: Implement Tools & Infrastructure
+
+1. **Design Tools** — Standardize on a primary design tool (Figma recommended)
+   - File organization and naming conventions
+   - Library structure for shared components
+   - Version control practices
+2. **Collaboration Tools** — How design shares work with engineering and product
+   - Design specs and handoff tool
+   - Component documentation platform
+   - Feedback and annotation tools
+3. **Research Tools** — User testing, analytics, feedback collection
+4. **Asset Management** — Icon library, illustration system, brand assets
+5. **Metrics Dashboard** — Track design ops health:
+   - Cycle time (brief to shipped)
+   - Rework rate (how often designs change after handoff)
+   - Design system adoption rate
+   - Team satisfaction scores
+   - Accessibility compliance rate
+
+## Output Format
+
+```yaml
+design_ops:
+  architect: "dave-malouf"
+  team_size: 0
+  maturity_level: "Ad Hoc | Emerging | Defined | Managed | Optimized"
+  workflow:
+    stages: [discover, define, design, deliver, measure]
+    sprint_cadence: "{duration}"
+    rituals:
+      - name: "{ritual}"
+        frequency: "{cadence}"
+        participants: ["{roles}"]
+  people_ops:
+    roles_defined: ["{role list}"]
+    career_framework: true
+    onboarding_plan: true
+    knowledge_management: "{approach}"
+  tools:
+    design: "{primary tool}"
+    collaboration: "{tool}"
+    research: "{tool}"
+    asset_management: "{tool}"
+  metrics:
+    cycle_time: "{target}"
+    rework_rate: "{target}"
+    system_adoption: "{target}"
+    team_satisfaction: "{target}"
+  implementation_plan:
+    week_1_2: ["{immediate setup}"]
+    month_1: ["{foundation}"]
+    month_3: ["{optimization}"]
+```
+
+## Veto Conditions
+
+- **NEVER** introduce tools without defining the workflow first — tools serve process, not the reverse
+- **NEVER** skip people ops — design ops fails without clear roles and career paths
+- **NEVER** copy another company's design ops wholesale — adapt to your team's maturity
+- **NEVER** implement everything at once — phase it or the team will be overwhelmed
+- **NEVER** build design ops in isolation from engineering — it must integrate
+
+## Completion Criteria
+
+- [ ] Current state assessed with bottlenecks identified
+- [ ] Design workflow defined with stages, activities, and gates
+- [ ] Workflow mapped to engineering process
+- [ ] Critique and review rituals established
+- [ ] Role definitions and career framework created
+- [ ] Onboarding plan documented
+- [ ] Tool stack standardized with conventions
+- [ ] Metrics defined for ongoing health tracking

package/squads/design-squad/workflows/wf-design-system-creation.yaml

@@ -0,0 +1,131 @@
+# Design System Creation Workflow
+# From audit through methodology to launch
+
+workflow:
+  id: wf-design-system-creation
+  name: "Criação de Design System"
+  trigger: "*design-system-creation"
+  entry_agent: design-chief
+  estimated_duration: "4-8 hours"
+  description: |
+    Workflow completo de criação de design system, desde a auditoria inicial até
+    seleção de metodologia, definição de tokens, construção de componentes,
+    estabelecimento de governança e lançamento. Segue a metodologia atomic design.
+
+  type: sequential
+  sequence:
+    - agent: brad-frost
+      action: create-design-system
+      creates: methodology
+    - agent: design-system-architect
+      action: create-component-spec
+      creates: components
+    - agent: dan-mall
+      action: create-design-system
+      creates: governance
+    - agent: design-chief
+      action: review
+      creates: final_system
+
+phases:
+  - id: phase_1_audit
+    name: "Interface Audit"
+    agent: brad-frost
+    task: create-design-system.md
+    depends_on: []
+    description: "Inventory all existing UI elements, identify inconsistencies and patterns"
+    checkpoint:
+      gate: "Complete component inventory with inconsistencies documented"
+      veto: "HALT if no access to existing interface — cannot audit what you cannot see"
+    outputs:
+      - component_inventory
+      - inconsistency_report
+      - priority_components
+
+  - id: phase_2_methodology
+    name: "Methodology & Token Architecture"
+    agent: brad-frost
+    task: create-design-system.md
+    depends_on: [phase_1_audit]
+    support_agents: [design-system-architect]
+    description: "Define atomic design methodology, establish token architecture (global → alias → component)"
+    checkpoint:
+      gate: "Token naming convention defined, hierarchy established, initial tokens created"
+      veto: "HALT if token naming convention is ambiguous or inconsistent"
+    outputs:
+      - token_architecture
+      - naming_conventions
+      - color_tokens
+      - typography_tokens
+      - spacing_tokens
+
+  - id: phase_3_tokens
+    name: "Token Implementation"
+    agent: design-system-architect
+    task: create-component-spec.md
+    depends_on: [phase_2_methodology]
+    description: "Implement all design tokens in code with theme support"
+    checkpoint:
+      gate: "All tokens implemented with light/dark mode and WCAG contrast verified"
+      veto: "HALT if contrast ratios fail WCAG AA requirements"
+    outputs:
+      - token_files
+      - theme_configuration
+      - contrast_verification
+
+  - id: phase_4_components
+    name: "Component Building"
+    agent: brad-frost
+    task: create-component-spec.md
+    depends_on: [phase_3_tokens]
+    support_agents: [design-system-architect, ui-engineer]
+    description: "Build atoms, molecules, and organisms following the priority list from audit"
+    checkpoint:
+      gate: "Core components built with all variants, states, and accessibility requirements"
+      veto: "HALT if components use hardcoded values instead of tokens"
+    outputs:
+      - atom_components
+      - molecule_components
+      - organism_components
+      - component_specs
+
+  - id: phase_5_governance
+    name: "Governance & Documentation"
+    agent: dan-mall
+    task: create-design-system.md
+    depends_on: [phase_4_components]
+    support_agents: [dave-malouf]
+    description: "Establish governance model, contribution guide, and complete documentation"
+    checkpoint:
+      gate: "Governance model defined, documentation complete, contribution process clear"
+      veto: "HALT if no clear ownership or approval process for component changes"
+    outputs:
+      - governance_model
+      - contribution_guide
+      - component_documentation
+      - getting_started_guide
+
+  - id: phase_6_launch
+    name: "Launch & Adoption"
+    agent: dan-mall
+    task: create-design-system.md
+    depends_on: [phase_5_governance]
+    support_agents: [dave-malouf, design-chief]
+    description: "Plan adoption strategy, train teams, launch the design system"
+    checkpoint:
+      gate: "Design system published, teams trained, adoption metrics established"
+      veto: "HALT if no adoption plan exists — a design system nobody uses has no value"
+    outputs:
+      - published_system
+      - training_materials
+      - adoption_metrics
+      - feedback_channels
+
+completion_criteria:
+  - "Interface audit completed with priority components identified"
+  - "Token architecture defined with naming conventions"
+  - "All tokens implemented with theme and contrast verification"
+  - "Core components built with variants, states, and accessibility"
+  - "Governance model established with clear ownership"
+  - "Documentation complete and accessible"
+  - "Teams trained and adoption metrics tracking"

package/squads/design-squad/workflows/wf-feature-design.yaml

@@ -0,0 +1,114 @@
+# Feature Design Workflow
+# From research through wireframes to implementation
+
+workflow:
+  id: wf-feature-design
+  name: "Design de Funcionalidade"
+  trigger: "*feature-design"
+  entry_agent: design-chief
+  estimated_duration: "2-4 hours"
+  description: |
+    Workflow completo de design de funcionalidade, desde pesquisa de usuário até wireframing,
+    design visual, especificação de implementação e integração com design system.
+
+  type: sequential
+  sequence:
+    - agent: ux-designer
+      action: design-ux-flow
+      creates: wireframes
+    - agent: visual-generator
+      action: create-component-spec
+      creates: visuals
+    - agent: ui-engineer
+      action: generate-handoff
+      creates: handoff
+    - agent: brad-frost
+      action: create-design-system
+      creates: integration
+
+phases:
+  - id: phase_1_research
+    name: "User Research & Discovery"
+    agent: ux-designer
+    task: design-ux-flow.md
+    depends_on: []
+    description: "Conduct user research, create personas, map user journeys"
+    checkpoint:
+      gate: "Research insights documented, personas created, user needs validated"
+      veto: "HALT if no user research is conducted — designing without research is guessing"
+    outputs:
+      - research_insights
+      - personas
+      - journey_map
+      - design_requirements
+
+  - id: phase_2_wireframe
+    name: "Information Architecture & Wireframes"
+    agent: ux-designer
+    task: design-ux-flow.md
+    depends_on: [phase_1_research]
+    description: "Define information architecture, create wireframes, design user flows"
+    checkpoint:
+      gate: "Wireframes cover all key screens, flows include happy and error paths"
+      veto: "HALT if wireframes only cover the happy path — error states must be designed"
+    outputs:
+      - information_architecture
+      - wireframes
+      - user_flows
+      - interaction_specs
+
+  - id: phase_3_visual
+    name: "Visual Design & Component Spec"
+    agent: visual-generator
+    task: create-component-spec.md
+    depends_on: [phase_2_wireframe]
+    support_agents: [brad-frost]
+    description: "Apply visual design, specify components, ensure design system alignment"
+    checkpoint:
+      gate: "Visual designs complete with all tokens mapped and WCAG compliance verified"
+      veto: "HALT if visual design introduces components that bypass the design system"
+    outputs:
+      - visual_designs
+      - component_specifications
+      - token_mapping
+      - accessibility_verification
+
+  - id: phase_4_implement
+    name: "Implementation Handoff"
+    agent: ui-engineer
+    task: generate-handoff.md
+    depends_on: [phase_3_visual]
+    support_agents: [dan-mall]
+    description: "Generate developer handoff documentation with tokens, interactions, and responsive specs"
+    checkpoint:
+      gate: "Handoff documentation complete with dev review conducted"
+      veto: "HALT if handoff lacks interaction specifications or responsive behavior"
+    outputs:
+      - handoff_documentation
+      - token_map
+      - interaction_specs
+      - asset_exports
+
+  - id: phase_5_integrate
+    name: "Design System Integration"
+    agent: brad-frost
+    task: create-design-system.md
+    depends_on: [phase_4_implement]
+    support_agents: [design-system-architect]
+    description: "Add new components to design system, update documentation, verify consistency"
+    checkpoint:
+      gate: "New components integrated into design system with documentation updated"
+      veto: "HALT if new components break existing system patterns"
+    outputs:
+      - updated_design_system
+      - new_component_docs
+      - regression_check
+
+completion_criteria:
+  - "User research conducted with insights documented"
+  - "Personas and journey maps created"
+  - "Wireframes cover all screens, flows, and states"
+  - "Visual design applied with design system alignment"
+  - "Accessibility verified (WCAG AA minimum)"
+  - "Developer handoff complete with all specifications"
+  - "New components integrated into design system"

package/squads/git-operations/README.md

@@ -0,0 +1,30 @@
+# Git Operations Squad
+
+Squad para operacoes git seguras com validacao de identidade SSH e quality gate pre-commit.
+
+## Agentes
+
+| Agente | Papel |
+|--------|-------|
+| devops | SSH setup, validacao de remote, push seguro |
+| dev | Quality gate (tsc + testes), staging, commit |
+
+## Workflows
+
+| Workflow | Fases |
+|----------|-------|
+| wf-ssh-setup | detect → key-check → configure → validate → identity |
+| wf-safe-commit | validate → pre-check → stage → commit → safe-push |
+
+## Triggers
+
+- "configurar ssh" → devops (wf-ssh-setup)
+- "commit e push" → dev (wf-safe-commit)
+- "validar ssh" → devops
+
+## Dependencias
+
+- Skill: `git-ssh-setup` (configuracao SSH)
+- Skill: `commit-dev` (commit com Conventional Commits)
+- Script: `scripts/hooks/pre-commit-validate.js` (quality gate)
+- Config local: `.gos-local/ssh-identity.json` ou `.a8z/local/ssh-identity.json`

package/squads/git-operations/squad.yaml

@@ -0,0 +1,27 @@
+name: git-operations
+version: "1.0.0"
+short-title: "Git Operations Squad"
+description: "Gerencia operacoes git seguras com validacao de identidade SSH, quality gate pre-commit (tsc + testes) e commits padronizados."
+slashPrefix: "git-ops"
+
+components:
+  agents:
+    - devops.md
+    - dev.md
+  workflows:
+    - wf-ssh-setup.yaml
+    - wf-safe-commit.yaml
+
+routing_matrix:
+  ssh_setup:
+    primary: devops
+    triggers: ["ssh setup", "configurar ssh", "identidade ssh", "trocar conta github"]
+  safe_commit:
+    primary: dev
+    triggers: ["commit", "push", "commit e push", "safe commit", "commitar"]
+  ssh_validation:
+    primary: devops
+    triggers: ["validar ssh", "verificar remote", "remote url"]
+  pre_commit:
+    primary: dev
+    triggers: ["validar antes do commit", "rodar testes", "tsc", "quality gate"]

package/squads/git-operations/workflows/wf-safe-commit.yaml

@@ -0,0 +1,27 @@
+workflow:
+  id: wf-safe-commit
+  name: "Safe Commit Pipeline"
+  entry_agent: dev
+  type: sequential
+
+phases:
+  - id: validate
+    name: "Pre-Commit Quality Gate"
+    owner: dev
+    goal: "Rodar node scripts/hooks/pre-commit-validate.js --json. Se falhar, corrigir erros e re-validar (max 2 tentativas)."
+  - id: pre-check
+    name: "SSH Identity Check"
+    owner: dev
+    goal: "Carregar ssh-identity.json, validar que o remote URL usa o alias SSH correto."
+  - id: stage
+    name: "Stage Changes"
+    owner: dev
+    goal: "Adicionar mudancas relevantes ao staging area com git add."
+  - id: commit
+    name: "Create Commit"
+    owner: dev
+    goal: "Criar commit com Conventional Commits. Alias SSH nao pode aparecer na mensagem."
+  - id: safe-push
+    name: "Safe Push"
+    owner: devops
+    goal: "Validar remote URL contra ssh-identity.json, corrigir se necessario, executar git push."

package/squads/git-operations/workflows/wf-ssh-setup.yaml

@@ -0,0 +1,27 @@
+workflow:
+  id: wf-ssh-setup
+  name: "SSH Identity Setup"
+  entry_agent: devops
+  type: sequential
+
+phases:
+  - id: detect
+    name: "Detect SSH Config"
+    owner: devops
+    goal: "Verificar se ssh-identity.json existe e se o remote URL ja usa um alias SSH."
+  - id: key-check
+    name: "Key Availability Check"
+    owner: devops
+    goal: "Testar conexao SSH com o alias detectado ou solicitado via ssh -T."
+  - id: configure
+    name: "Configure Workspace"
+    owner: devops
+    goal: "Gravar ssh-identity.json no diretorio local gitignored (.gos-local/ ou .a8z/local/)."
+  - id: validate
+    name: "Validate Connection"
+    owner: devops
+    goal: "Confirmar que git fetch funciona com a identidade configurada."
+  - id: identity
+    name: "Set Git Identity"
+    owner: devops
+    goal: "Configurar git user.name e user.email localmente no repositorio."

package/squads/sprint-planning/agents/sprint-chief.md

@@ -0,0 +1,47 @@
+# sprint-chief
+
+```yaml
+agent:
+  name: Sprint Chief
+  id: sprint-chief
+  title: Sprint Planning Orchestrator
+  icon: "\U0001F3AF"
+  tier: 0
+  whenToUse: >
+    Orquestrar o ciclo completo de sprint: coordenar planner, importer e tracker.
+    Decidir fluxo, gerenciar handoffs entre agents, escalar problemas.
+
+persona:
+  role: Sprint Orchestrator
+  identity: Coordenador de sprint que garante que todas as fases fluem corretamente
+  core_principles:
+    - Validar prerequisites antes de iniciar qualquer fase
+    - Coordenar handoffs entre agents com contexto completo
+    - Garantir que sprint registry esta atualizado
+    - Notificar Slack em marcos importantes
+
+commands:
+  - name: sprint-create
+    description: "Orquestrar criacao completa de sprint (plan -> create -> import -> track)"
+  - name: sprint-close
+    description: "Fechar sprint, mover tasks incompletas, gerar retrospective"
+  - name: sprint-review
+    description: "Gerar review da sprint com metricas e status"
+
+dependencies:
+  tools:
+    - clickup
+    - slack-notify
+  agents:
+    - sprint-planner-agent
+    - sprint-tracker
+    - task-importer
+```
+
+## Responsabilidades
+
+1. **Pre-flight check:** Verificar env vars, space ID, permissoes
+2. **Orchestration:** Coordenar fluxo create -> import -> track
+3. **Handoffs:** Passar contexto entre agents (folder IDs, task maps)
+4. **Sprint Close:** Detectar tasks abertas, oferecer spillover para proxima sprint
+5. **Notifications:** Enviar resumos formatados no Slack nos marcos

package/squads/sprint-planning/agents/sprint-planner-agent.md

@@ -0,0 +1,43 @@
+# sprint-planner-agent
+
+```yaml
+agent:
+  name: Sprint Planner
+  id: sprint-planner-agent
+  title: Sprint Planning Specialist
+  icon: "\U0001F4CB"
+  tier: 1
+  whenToUse: >
+    Validar sprint plans, verificar schema, criar sprint no ClickUp (folder + lists).
+
+persona:
+  role: Sprint Planner
+  identity: Especialista em estruturar e validar sprints antes da criacao no ClickUp
+  core_principles:
+    - Validar sprint JSON contra schema antes de criar
+    - Verificar que todas tasks tem IDs unicos e prioridades
+    - Detectar dependencias circulares
+    - Criar folder e lists seguindo naming convention
+
+commands:
+  - name: validate-plan
+    description: "Validar sprint plan JSON contra schema"
+  - name: create-sprint
+    description: "Criar sprint (folder + lists) no ClickUp"
+
+dependencies:
+  tools:
+    - clickup
+  schemas:
+    - data/schemas/sprint-clickup.schema.json
+  templates:
+    - templates/sprint-clickup.template.md
+```
+
+## Workflow
+
+1. Receber sprint plan (JSON ou markdown)
+2. Validar contra `data/schemas/sprint-clickup.schema.json`
+3. Verificar IDs unicos, prioridades, dependencias
+4. Executar `clickup.js sprint create` com parametros
+5. Retornar folder_id e list_ids para handoff ao task-importer

package/squads/sprint-planning/agents/sprint-tracker.md

@@ -0,0 +1,43 @@
+# sprint-tracker
+
+```yaml
+agent:
+  name: Sprint Tracker
+  id: sprint-tracker
+  title: Sprint Tracking & Status Specialist
+  icon: "\U0001F4CA"
+  tier: 1
+  whenToUse: >
+    Consultar status da sprint no ClickUp, calcular metricas,
+    gerar reports e notificar Slack com resumos.
+
+persona:
+  role: Sprint Tracker
+  identity: Analista de progresso que transforma dados ClickUp em insights acionaveis
+  core_principles:
+    - Agregar metricas de todas as lists da sprint
+    - Calcular completion %, velocity, blocked tasks
+    - Gerar resumos formatados para Slack (Block Kit)
+    - Detectar tasks bloqueadas e alertar
+
+commands:
+  - name: sprint-status
+    description: "Consultar status da sprint ativa"
+  - name: sprint-report
+    description: "Gerar report detalhado com metricas"
+  - name: notify-status
+    description: "Enviar resumo de status no Slack"
+
+dependencies:
+  tools:
+    - clickup
+    - slack-notify
+```
+
+## Workflow
+
+1. Executar `clickup.js sprint status --folder-id X`
+2. Processar resultado: total, done, in-progress, blocked, completion %
+3. Gerar JSON de status para Slack
+4. Executar `slack-notify.js sprint-summary --file status.json`
+5. Alertar se tasks bloqueadas > 0