ganbatte-os 0.2.1

package/squads/sprint-planning/agents/task-importer.md

@@ -0,0 +1,44 @@
+# task-importer
+
+```yaml
+agent:
+  name: Task Importer
+  id: task-importer
+  title: Task Import Specialist
+  icon: "\U0001F4E5"
+  tier: 1
+  whenToUse: >
+    Converter sprint plans (markdown/JSON) em tasks ClickUp.
+    Bulk import com subtasks, custom fields e tags.
+
+persona:
+  role: Task Importer
+  identity: Conversor que transforma planos locais em tasks ClickUp com fidelidade
+  core_principles:
+    - Mapear campos G-OS para ClickUp (ref, points, BR, AC)
+    - Respeitar rate limits no bulk import
+    - Atualizar sprint registry com IDs criados
+    - Reportar falhas sem interromper o batch
+
+commands:
+  - name: import-tasks
+    description: "Importar tasks de JSON para ClickUp"
+  - name: import-markdown
+    description: "Converter markdown sprint-track para JSON e importar"
+
+dependencies:
+  tools:
+    - clickup
+  data:
+    - data/sprints/registry.json
+    - squads/sprint-planning/data/clickup-field-mapping.yaml
+```
+
+## Workflow
+
+1. Receber folder_id e list_ids do sprint-planner-agent
+2. Ler sprint plan JSON (ou converter markdown para JSON)
+3. Executar `clickup.js sprint import --folder-id X --file plan.json`
+4. Processar resultado: created, failed
+5. Atualizar `data/sprints/registry.json` com task ID mapping
+6. Reportar resultado ao sprint-chief

package/squads/sprint-planning/checklists/sprint-readiness.md

@@ -0,0 +1,27 @@
+# Sprint Readiness Checklist
+
+Verificar antes de criar sprint no ClickUp.
+
+## Environment
+- [ ] `CLICKUP_API_KEY` definido e valido
+- [ ] `SLACK_WEBHOOK_URL` definido (opcional, para notificacoes)
+- [ ] ClickUp Space ID conhecido
+
+## Sprint Plan
+- [ ] Sprint plan JSON/markdown existe e esta completo
+- [ ] Todos tasks tem ID unico (T-NNN)
+- [ ] Todos tasks tem prioridade (P0/P1/P2)
+- [ ] Tasks atribuidos a tracks (backend/frontend/qa/devops)
+- [ ] Dependencias documentadas (sem circulares)
+- [ ] Acceptance criteria definidos por sprint
+- [ ] Business rules referenciadas
+
+## ClickUp Space
+- [ ] Space existe e esta acessivel
+- [ ] Custom fields criados (se necessario): gos_ref, sprint_points
+- [ ] Statuses configurados: to do, in progress, in review, complete, blocked
+
+## Team
+- [ ] Responsaveis definidos por track
+- [ ] Datas de inicio e fim da sprint definidas
+- [ ] Sprint anterior fechada (se aplicavel)

package/squads/sprint-planning/config/config.yaml

@@ -0,0 +1,65 @@
+squad: sprint-planning
+version: "1.0.0"
+
+tiers:
+  tier0:
+    role: orchestrator
+    agent: sprint-chief
+    model_tier: sonnet
+    description: "Coordena o fluxo entre agents, decide quando escalar"
+  tier1:
+    role: specialists
+    agents:
+      - sprint-planner-agent
+      - sprint-tracker
+      - task-importer
+    model_tier: sonnet
+    description: "Especialistas em planejamento, tracking e importacao"
+
+env_required:
+  - CLICKUP_API_KEY
+  - SLACK_WEBHOOK_URL
+
+env_optional:
+  - CLICKUP_SPACE_ID
+  - CLICKUP_SPRINT_FOLDER_ID
+
+tools:
+  clickup: scripts/tools/clickup.js
+  slack: scripts/tools/slack-notify.js
+
+defaults:
+  sprint_duration_days: 7
+  tracks: [backend, frontend]
+  status_mapping:
+    todo: "to do"
+    in_progress: "in progress"
+    review: "in review"
+    done: "complete"
+    blocked: "blocked"
+
+handoffs:
+  sprint_chief_to_planner:
+    from: sprint-chief
+    to: sprint-planner-agent
+    trigger: "sprint plan validated"
+    context: [sprint_plan, space_id]
+  planner_to_importer:
+    from: sprint-planner-agent
+    to: task-importer
+    trigger: "sprint created in ClickUp"
+    context: [folder_id, list_ids, tasks_json]
+  importer_to_tracker:
+    from: task-importer
+    to: sprint-tracker
+    trigger: "tasks imported"
+    context: [folder_id, task_map]
+
+cross_cutting:
+  notifications:
+    slack_on_sprint_create: true
+    slack_on_import_complete: true
+    slack_on_sprint_close: true
+  registry:
+    path: data/sprints/registry.json
+    auto_update: true

package/squads/sprint-planning/data/clickup-field-mapping.yaml

@@ -0,0 +1,94 @@
+# ClickUp Custom Field Mapping
+# Maps G-OS task fields to ClickUp custom fields
+# field_id values must be configured per workspace (discovered via `clickup.js field list`)
+
+version: "1.0"
+
+fields:
+  gos_ref:
+    description: "Reference code (M/F/B) from spec"
+    clickup_type: short_text
+    gos_source: ref
+    field_id: ""  # Set per workspace
+
+  sprint_points:
+    description: "Story points / sprint points"
+    clickup_type: number
+    gos_source: points
+    field_id: ""
+
+  business_rules:
+    description: "Business rules (BR-NNN)"
+    clickup_type: text
+    gos_source: businessRules
+    field_id: ""
+
+  track:
+    description: "Development track"
+    clickup_type: drop_down
+    gos_source: area
+    options: [backend, frontend, qa, devops, general]
+    field_id: ""
+
+  acceptance_criteria:
+    description: "Acceptance criteria"
+    clickup_type: text
+    gos_source: acceptanceCriteria
+    field_id: ""
+
+  depends_on:
+    description: "Task dependencies (T-NNN list)"
+    clickup_type: text
+    gos_source: dependencies
+    field_id: ""
+
+  context:
+    description: "Contexto de negócio — motivação da task para leitor não-técnico"
+    clickup_type: text
+    gos_source: context
+    mapped_to: description  # Integrado na descrição rica via buildTaskDescription()
+
+  steps:
+    description: "Passo a passo de implementação (3-7 steps acionáveis)"
+    clickup_type: checklist
+    gos_source: steps
+    mapped_to: "checklist:Implementation Steps"  # Vira checklist automaticamente
+
+  technical_notes:
+    description: "Notas técnicas, decisões de arquitetura, caveats"
+    clickup_type: text
+    gos_source: technicalNotes
+    mapped_to: description  # Integrado na descrição rica
+
+  estimated_hours:
+    description: "Estimativa em horas (0.5-16)"
+    clickup_type: number
+    gos_source: estimatedHours
+    mapped_to: time_estimate  # Convertido para milissegundos no import
+
+  dod:
+    description: "Definition of Done — como verificar que está pronto"
+    clickup_type: text
+    gos_source: dod
+    mapped_to: description  # Integrado na descrição rica
+
+tag_conventions:
+  sprint_id: "sprint:{SPRINT_ID}"          # e.g. sprint:S01
+  sprint_status: "sprint-status:{STATUS}"  # e.g. sprint-status:active
+  track: "track:{TRACK}"                   # e.g. track:backend
+  task_id: "{TASK_ID}"                     # e.g. T-001
+
+status_mapping:
+  gos_to_clickup:
+    todo: "to do"
+    in-progress: "in progress"
+    review: "in review"
+    done: "complete"
+    blocked: "blocked"
+  clickup_to_gos:
+    "to do": todo
+    "in progress": in-progress
+    "in review": review
+    "complete": done
+    "closed": done
+    "blocked": blocked

package/squads/sprint-planning/squad.yaml

@@ -0,0 +1,52 @@
+name: sprint-planning
+version: "1.0.0"
+short-title: "Sprint Planning Squad"
+description: "Orquestra o ciclo de vida de sprints no ClickUp: planejamento, criacao, importacao de tasks, tracking de status e fechamento. Usa Folders como containers de sprint e Lists como tracks (backend/frontend)."
+author: "Synkra AIOS"
+license: MIT
+slashPrefix: "sprint-squad"
+
+aios:
+  minVersion: "4.0.0"
+  type: squad
+
+tags:
+  - sprint
+  - clickup
+  - agile
+  - task-management
+  - scrum
+  - project-management
+
+components:
+  agents:
+    # Tier 0 — Orchestrator
+    - sprint-chief.md
+    # Tier 1 — Specialists
+    - sprint-planner-agent.md
+    - sprint-tracker.md
+    - task-importer.md
+  tasks:
+    - create-sprint.md
+    - import-tasks.md
+    - sync-status.md
+    - close-sprint.md
+  workflows:
+    - wf-sprint-creation.yaml
+    - wf-sprint-sync.yaml
+  checklists:
+    - sprint-readiness.md
+
+routing_matrix:
+  sprint_creation:
+    primary: sprint-planner-agent
+    triggers: ["create sprint", "new sprint", "plan sprint", "criar sprint"]
+  sprint_tracking:
+    primary: sprint-tracker
+    triggers: ["sprint status", "burndown", "track progress", "status da sprint"]
+  task_import:
+    primary: task-importer
+    triggers: ["import tasks", "sync to clickup", "push tasks", "importar tasks"]
+  sprint_close:
+    primary: sprint-chief
+    triggers: ["close sprint", "sprint review", "fechar sprint", "retrospective"]

package/squads/sprint-planning/tasks/close-sprint.md

@@ -0,0 +1,43 @@
+# Task: Close Sprint
+
+## Objetivo
+Fechar sprint, tratar tasks incompletas (spillover) e gerar retrospective.
+
+## Steps
+
+1. **Get final status**
+   ```bash
+   node scripts/tools/clickup.js sprint status --folder-id <FOLDER_ID>
+   ```
+
+2. **Identify incomplete tasks**
+   Filtrar tasks com status != done/complete.
+
+3. **Spillover decision**
+   Perguntar ao usuario:
+   - Mover tasks incompletas para proxima sprint?
+   - Cancelar tasks incompletas?
+   - Manter no folder atual?
+
+4. **Execute spillover** (se aplicavel)
+   Para cada task incompleta, mover para novo folder:
+   ```bash
+   node scripts/tools/clickup.js task update --task-id <ID> --status "to do"
+   # Nota: mover entre lists requer API de task move (PUT /task/{id} com list)
+   ```
+
+5. **Tag sprint as closed**
+   ```bash
+   node scripts/tools/clickup.js tag add --task-id <FOLDER_FIRST_TASK> --tag "sprint-closed"
+   ```
+
+6. **Notify Slack**
+   ```bash
+   node scripts/tools/slack-notify.js send \
+     --text "*:checkered_flag: Sprint <SPRINT_ID> encerrada!*\n>*Concluidas:* N/M (X%)\n>*Spillover:* N tasks para <NEXT_SPRINT>"
+   ```
+
+## Output
+- Sprint encerrada
+- Tasks spillover tratadas
+- Retrospective summary no Slack

package/squads/sprint-planning/tasks/create-sprint.md

@@ -0,0 +1,42 @@
+# Task: Create Sprint
+
+## Objetivo
+Criar sprint no ClickUp a partir de um plano validado.
+
+## Pre-requisitos
+- [ ] `CLICKUP_API_KEY` definido
+- [ ] Space ID conhecido
+- [ ] Sprint plan validado contra schema
+
+## Steps
+
+1. **Validate plan**
+   ```bash
+   # Verificar que JSON e valido
+   node -e "JSON.parse(require('fs').readFileSync('sprint-plan.json','utf-8')); console.log('OK')"
+   ```
+
+2. **Create sprint folder + lists**
+   ```bash
+   node scripts/tools/clickup.js sprint create \
+     --space-id <SPACE_ID> \
+     --name "<SPRINT_NAME>" \
+     --start <YYYY-MM-DD> \
+     --end <YYYY-MM-DD> \
+     --tracks backend,frontend \
+     --id <SPRINT_ID>
+   ```
+
+3. **Save folder ID to registry**
+   Atualizar `data/sprints/registry.json` com o folder_id e list_ids retornados.
+
+4. **Notify Slack**
+   ```bash
+   node scripts/tools/slack-notify.js send \
+     --text "*:rocket: Sprint <SPRINT_ID> criada!*\n>*Nome:* <SPRINT_NAME>\n>*Periodo:* <START> to <END>\n>*Tracks:* backend, frontend"
+   ```
+
+## Output
+- folder_id, list_ids para handoff ao task-importer
+- Registry atualizado
+- Notificacao Slack enviada

package/squads/sprint-planning/tasks/import-tasks.md

@@ -0,0 +1,39 @@
+# Task: Import Tasks
+
+## Objetivo
+Importar tasks de um sprint plan JSON para o ClickUp em batch.
+
+## Pre-requisitos
+- [ ] Sprint criada (folder_id e list_ids disponiveis)
+- [ ] Sprint plan JSON segue schema `data/schemas/sprint-clickup.schema.json`
+- [ ] `CLICKUP_API_KEY` definido
+
+## Steps
+
+1. **Import tasks**
+   ```bash
+   node scripts/tools/clickup.js sprint import \
+     --folder-id <FOLDER_ID> \
+     --file sprint-plan.json
+   ```
+
+2. **Process results**
+   - Verificar `imported` vs `failed` counts
+   - Se `failed > 0`, investigar errors no output
+
+3. **Update registry**
+   Atualizar `data/sprints/registry.json` com mapping:
+   ```json
+   { "taskMap": { "T-001": "clickup_id_1", "T-002": "clickup_id_2" } }
+   ```
+
+4. **Notify Slack**
+   ```bash
+   node scripts/tools/slack-notify.js send \
+     --text "*:package: Tasks importadas!*\n>*Sprint:* <SPRINT_ID>\n>*Importadas:* N tasks\n>*Falhas:* N"
+   ```
+
+## Output
+- Task map (local ID -> ClickUp ID)
+- Registry atualizado
+- Slack notificado

package/squads/sprint-planning/tasks/sync-status.md

@@ -0,0 +1,31 @@
+# Task: Sync Status
+
+## Objetivo
+Consultar status da sprint no ClickUp e gerar report.
+
+## Steps
+
+1. **Get sprint status**
+   ```bash
+   node scripts/tools/clickup.js sprint status --folder-id <FOLDER_ID>
+   ```
+
+2. **Save status JSON**
+   Salvar output em arquivo temporario para o Slack notifier.
+
+3. **Notify Slack**
+   ```bash
+   node scripts/tools/slack-notify.js sprint-summary --file sprint-status.json
+   ```
+
+4. **Alert on blockers**
+   Se `blocked > 0`, adicionar alerta:
+   ```bash
+   node scripts/tools/slack-notify.js send \
+     --text ":warning: *<BLOCKED_COUNT> tasks bloqueadas na sprint <SPRINT_ID>!*"
+   ```
+
+## Output
+- Sprint status JSON
+- Slack summary enviado
+- Alerta de blockers se necessario

package/squads/sprint-planning/workflows/wf-sprint-creation.yaml

@@ -0,0 +1,59 @@
+workflow:
+  id: wf-sprint-creation
+  name: "Sprint Creation Pipeline"
+  version: "1.0.0"
+  description: >
+    End-to-end sprint creation: from planning artifacts to ClickUp workspace.
+    Reads sprint plan, validates structure, creates ClickUp folder/lists,
+    imports tasks, sets custom fields, and produces sprint overview.
+  trigger: "*sprint-create"
+  entry_agent: sprint-chief
+  type: sequential
+
+phases:
+  - id: phase_0
+    name: "Pre-flight Check"
+    agent: sprint-chief
+    description: "Verify env vars, space ID, and sprint plan availability."
+    checkpoint:
+      gate: "CLICKUP_API_KEY set, space ID known, plan file exists"
+      veto: "Missing env vars or plan file"
+
+  - id: phase_1
+    name: "Plan Validation"
+    agent: sprint-planner-agent
+    task: create-sprint.md
+    depends_on: [phase_0]
+    description: "Validate sprint plan JSON against schema, check IDs and priorities."
+    checkpoint:
+      gate: "Schema validates, all tasks have unique IDs and priorities"
+      veto: "Schema validation failed or circular dependencies detected"
+
+  - id: phase_2
+    name: "ClickUp Sprint Setup"
+    agent: sprint-planner-agent
+    task: create-sprint.md
+    depends_on: [phase_1]
+    description: "Create ClickUp folder (sprint container) and lists (tracks)."
+    checkpoint:
+      gate: "Folder and all lists created, IDs captured"
+      veto: "API auth failure or space not found"
+
+  - id: phase_3
+    name: "Task Import"
+    agent: task-importer
+    task: import-tasks.md
+    depends_on: [phase_2]
+    description: "Bulk create tasks in ClickUp lists, set fields, add tags."
+    checkpoint:
+      gate: "All tasks created, IDs mapped back to local plan"
+      veto: "Rate limit exceeded or task creation failures > 10%"
+
+  - id: phase_4
+    name: "Status Sync & Notification"
+    agent: sprint-tracker
+    task: sync-status.md
+    depends_on: [phase_3]
+    description: "Read back sprint status, generate overview, notify Slack."
+    checkpoint:
+      gate: "Sprint overview generated, Slack notified"

package/squads/sprint-planning/workflows/wf-sprint-sync.yaml

@@ -0,0 +1,35 @@
+workflow:
+  id: wf-sprint-sync
+  name: "Sprint Bidirectional Sync"
+  version: "1.0.0"
+  description: >
+    Sync sprint status between ClickUp and local files.
+    Pulls remote state, diffs against local, applies changes.
+  trigger: "*sprint-sync"
+  entry_agent: sprint-chief
+  type: sequential
+
+phases:
+  - id: phase_0
+    name: "Pull Remote State"
+    agent: sprint-tracker
+    task: sync-status.md
+    description: "Fetch current sprint status from ClickUp."
+    checkpoint:
+      gate: "Remote state fetched successfully"
+
+  - id: phase_1
+    name: "Diff Local vs Remote"
+    agent: sprint-tracker
+    depends_on: [phase_0]
+    description: "Compare local task states with ClickUp states."
+    checkpoint:
+      gate: "Diff generated with change list"
+
+  - id: phase_2
+    name: "Apply Changes"
+    agent: sprint-chief
+    depends_on: [phase_1]
+    description: "Apply changes to local files or push to ClickUp."
+    checkpoint:
+      gate: "All changes applied, registry updated"

package/templates/adr-tmpl.yaml

@@ -0,0 +1,76 @@
+# ADR Template — Architecture Decision Record
+# Padrao Michael Nygard adaptado para G-OS
+# Used by: sprint-planner, sdd (Phase 2), @architect
+version: "1.0.0"
+
+structure:
+  id: "ADR-{NNN}"
+  title: "{Decision Title}"
+  status: "proposed | accepted | deprecated | superseded"
+  date: "{YYYY-MM-DD}"
+  deciders: "{list of people/agents involved}"
+  context: |
+    Qual e o problema ou forca que motiva esta decisao?
+    Quais forcas estao em jogo (tecnicas, negocio, time)?
+  options:
+    - name: "{Option A}"
+      pros: ["{pro 1}", "{pro 2}"]
+      cons: ["{con 1}", "{con 2}"]
+    - name: "{Option B}"
+      pros: ["{pro 1}", "{pro 2}"]
+      cons: ["{con 1}", "{con 2}"]
+  decision: |
+    Qual opcao foi escolhida e por que?
+    Qual mudanca sera feita?
+  consequences:
+    positive: ["{consequencia positiva 1}"]
+    negative: ["{consequencia negativa 1}"]
+    neutral: ["{consequencia neutra 1}"]
+  references:
+    - "{link ou caminho de arquivo}"
+
+# Quando usar ADR separado vs embedded no PRD:
+# - ADR separado: 3+ opcoes com trade-offs significativos (stack, banco, auth, arquitetura)
+# - Embedded no PRD: decisoes menores com escolha obvia (lib, naming, padrao de codigo)
+
+markdownTemplate: |
+  # {id}: {title}
+
+  **Status:** {status}
+  **Date:** {date}
+  **Deciders:** {deciders}
+
+  ## Contexto
+
+  {context}
+
+  ## Opcoes Consideradas
+
+  ### Opcao 1: {options[0].name}
+  - **Pros:** {options[0].pros}
+  - **Cons:** {options[0].cons}
+
+  ### Opcao 2: {options[1].name}
+  - **Pros:** {options[1].pros}
+  - **Cons:** {options[1].cons}
+
+  ## Decisao
+
+  {decision}
+
+  ## Decision Gate (custo & risco)
+
+  - Esta decisao atende aos objetivos de negocio declarados?
+  - Respeita todas as restricoes explicitas (seguranca, compliance, stack, orcamento, time)?
+  - Cumpre os atributos de qualidade com metricas e carga-alvo (latencia/disponibilidade/throughput)?
+  - Existe alternativa mais barata ou menos arriscada que entregue os mesmos objetivos? Se sim, por que foi descartada?
+
+  ## Consequencias
+
+  **Positivas:** {consequences.positive}
+  **Negativas:** {consequences.negative}
+  **Neutras:** {consequences.neutral}
+
+  ## Referencias
+
+  {references}

package/templates/sprint-clickup.template.md

@@ -0,0 +1,80 @@
+# Sprint {{SPRINT_ID}} — {{SPRINT_NAME}}
+
+## Metadata
+
+| Campo | Valor |
+|-------|-------|
+| **Sprint** | {{SPRINT_ID}} |
+| **Nome** | {{SPRINT_NAME}} |
+| **Início** | {{START_DATE}} |
+| **Fim** | {{END_DATE}} |
+| **Duração** | {{DURATION_DAYS}} dias |
+| **Team** | {{TEAM}} |
+| **ClickUp Folder ID** | {{CLICKUP_FOLDER_ID}} |
+| **ClickUp Space ID** | {{CLICKUP_SPACE_ID}} |
+| **Status** | {{STATUS}} |
+
+---
+
+## Track: Backend
+
+**ClickUp List ID:** {{BACKEND_LIST_ID}}
+
+| ID | Ref | Título | Escopo resumido | Points | Status | ClickUp ID |
+|----|-----|--------|-----------------|--------|--------|-------------|
+| T-001 | B-001 | | | 3 | todo | |
+| T-002 | B-002 | | | 5 | todo | |
+
+---
+
+## Track: Frontend
+
+**ClickUp List ID:** {{FRONTEND_LIST_ID}}
+
+| ID | Ref | Título | Escopo resumido | Points | Status | ClickUp ID |
+|----|-----|--------|-----------------|--------|--------|-------------|
+| T-020 | F-001 | | | 3 | todo | |
+| T-021 | F-002 | | | 5 | todo | |
+
+---
+
+## Business Rules
+
+| ID | Descrição |
+|----|-----------|
+| BR-001 | |
+
+---
+
+## Dependências (Cross-Track)
+
+| FE Task | Depende de BE Task | Sprint FE | Sprint BE | Buffer |
+|---------|-------------------|-----------|-----------|--------|
+| T-020 | T-001 | Mesmo sprint | Mesmo sprint | 0 |
+
+---
+
+## Acceptance Criteria do Sprint
+
+- [ ] Todos endpoints backend retornam dados conforme Zod schema
+- [ ] Todos componentes frontend renderizam com dados reais
+- [ ] Testes E2E passam para fluxos críticos
+- [ ] Coverage > 80% em módulos novos
+
+---
+
+## API Contracts
+
+```
+GET  /api/{{MODULE}}         -> { items: [], total: number }
+POST /api/{{MODULE}}         -> { id: string } | 400/422
+PUT  /api/{{MODULE}}/[id]    -> { updated: true } | 404
+```
+
+---
+
+## Notas
+
+- Gerado via `node scripts/tools/clickup.js sprint create`
+- Template base: `templates/sprint-clickup.template.md`
+- Schema: `data/schemas/sprint-clickup.schema.json`