mega-brain-ai 1.3.0

package/.claude/commands/gsd/research-phase.md

@@ -0,0 +1,189 @@
+---
+name: gsd:research-phase
+description: Research how to implement a phase (standalone - usually use /gsd:plan-phase instead)
+argument-hint: "[phase]"
+allowed-tools:
+  - Read
+  - Bash
+  - Task
+---
+
+<objective>
+Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.
+
+**Note:** This is a standalone research command. For most workflows, use `/gsd:plan-phase` which integrates research automatically.
+
+**Use this command when:**
+- You want to research without planning yet
+- You want to re-research after planning is complete
+- You need to investigate before deciding if a phase is feasible
+
+**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
+
+**Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
+</objective>
+
+<context>
+Phase number: $ARGUMENTS (required)
+
+Normalize phase input in step 1 before any directory lookups.
+</context>
+
+<process>
+
+## 0. Initialize Context
+
+```bash
+INIT=$(node ./.claude/get-shit-done/bin/gsd-tools.cjs init phase-op "$ARGUMENTS")
+```
+
+Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`, `state_path`, `requirements_path`, `context_path`, `research_path`.
+
+Resolve researcher model:
+```bash
+RESEARCHER_MODEL=$(node ./.claude/get-shit-done/bin/gsd-tools.cjs resolve-model gsd-phase-researcher --raw)
+```
+
+## 1. Validate Phase
+
+```bash
+PHASE_INFO=$(node ./.claude/get-shit-done/bin/gsd-tools.cjs roadmap get-phase "${phase_number}")
+```
+
+**If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.
+
+## 2. Check Existing Research
+
+```bash
+ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
+```
+
+**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
+
+**If doesn't exist:** Continue.
+
+## 3. Gather Phase Context
+
+Use paths from INIT (do not inline file contents in orchestrator context):
+- `requirements_path`
+- `context_path`
+- `state_path`
+
+Present summary with phase description and what files the researcher will load.
+
+## 4. Spawn gsd-phase-researcher Agent
+
+Research modes: ecosystem (default), feasibility, implementation, comparison.
+
+```markdown
+<research_type>
+Phase Research — investigating HOW to implement a specific phase well.
+</research_type>
+
+<key_insight>
+The question is NOT "which library should I use?"
+
+The question is: "What do I not know that I don't know?"
+
+For this phase, discover:
+- What's the established architecture pattern?
+- What libraries form the standard stack?
+- What problems do people commonly hit?
+- What's SOTA vs what Claude's training thinks is SOTA?
+- What should NOT be hand-rolled?
+</key_insight>
+
+<objective>
+Research implementation approach for Phase {phase_number}: {phase_name}
+Mode: ecosystem
+</objective>
+
+<files_to_read>
+- {requirements_path} (Requirements)
+- {context_path} (Phase context from discuss-phase, if exists)
+- {state_path} (Prior project decisions and blockers)
+</files_to_read>
+
+<additional_context>
+**Phase description:** {phase_description}
+</additional_context>
+
+<downstream_consumer>
+Your RESEARCH.md will be loaded by `/gsd:plan-phase` which uses specific sections:
+- `## Standard Stack` → Plans use these libraries
+- `## Architecture Patterns` → Task structure follows these
+- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
+- `## Common Pitfalls` → Verification steps check for these
+- `## Code Examples` → Task actions reference these patterns
+
+Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
+</downstream_consumer>
+
+<quality_gate>
+Before declaring complete, verify:
+- [ ] All domains investigated (not just some)
+- [ ] Negative claims verified with official docs
+- [ ] Multiple sources for critical claims
+- [ ] Confidence levels assigned honestly
+- [ ] Section names match what plan-phase expects
+</quality_gate>
+
+<output>
+Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
+</output>
+```
+
+```
+Task(
+  prompt="First, read ./.claude/agents/gsd-phase-researcher.md for your role and instructions.\n\n" + filled_prompt,
+  subagent_type="general-purpose",
+  model="{researcher_model}",
+  description="Research Phase {phase}"
+)
+```
+
+## 5. Handle Agent Return
+
+**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
+
+**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
+
+**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
+
+## 6. Spawn Continuation Agent
+
+```markdown
+<objective>
+Continue research for Phase {phase_number}: {phase_name}
+</objective>
+
+<prior_state>
+<files_to_read>
+- .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md (Existing research)
+</files_to_read>
+</prior_state>
+
+<checkpoint_response>
+**Type:** {checkpoint_type}
+**Response:** {user_response}
+</checkpoint_response>
+```
+
+```
+Task(
+  prompt="First, read ./.claude/agents/gsd-phase-researcher.md for your role and instructions.\n\n" + continuation_prompt,
+  subagent_type="general-purpose",
+  model="{researcher_model}",
+  description="Continue research Phase {phase}"
+)
+```
+
+</process>
+
+<success_criteria>
+- [ ] Phase validated against roadmap
+- [ ] Existing research checked
+- [ ] gsd-phase-researcher spawned with context
+- [ ] Checkpoints handled correctly
+- [ ] User knows next steps
+</success_criteria>

package/.claude/commands/gsd/resume-work.md

@@ -0,0 +1,40 @@
+---
+name: gsd:resume-work
+description: Resume work from previous session with full context restoration
+allowed-tools:
+  - Read
+  - Bash
+  - Write
+  - AskUserQuestion
+  - SlashCommand
+---
+
+<objective>
+Restore complete project context and resume work seamlessly from previous session.
+
+Routes to the resume-project workflow which handles:
+
+- STATE.md loading (or reconstruction if missing)
+- Checkpoint detection (.continue-here files)
+- Incomplete work detection (PLAN without SUMMARY)
+- Status presentation
+- Context-aware next action routing
+  </objective>
+
+<execution_context>
+@./.claude/get-shit-done/workflows/resume-project.md
+</execution_context>
+
+<process>
+**Follow the resume-project workflow** from `@./.claude/get-shit-done/workflows/resume-project.md`.
+
+The workflow handles all resumption logic including:
+
+1. Project existence verification
+2. STATE.md loading or reconstruction
+3. Checkpoint and incomplete work detection
+4. Visual status presentation
+5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
+6. Routing to appropriate next command
+7. Session continuity updates
+   </process>

package/.claude/commands/gsd/set-profile.md

@@ -0,0 +1,34 @@
+---
+name: gsd:set-profile
+description: Switch model profile for GSD agents (quality/balanced/budget)
+argument-hint: <profile>
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+<objective>
+Switch the model profile used by GSD agents. Controls which Claude model each agent uses, balancing quality vs token spend.
+
+Routes to the set-profile workflow which handles:
+- Argument validation (quality/balanced/budget)
+- Config file creation if missing
+- Profile update in config.json
+- Confirmation with model table display
+</objective>
+
+<execution_context>
+@./.claude/get-shit-done/workflows/set-profile.md
+</execution_context>
+
+<process>
+**Follow the set-profile workflow** from `@./.claude/get-shit-done/workflows/set-profile.md`.
+
+The workflow handles all logic including:
+1. Profile argument validation
+2. Config file ensuring
+3. Config reading and updating
+4. Model table generation from MODEL_PROFILES
+5. Confirmation display
+</process>

package/.claude/commands/gsd/settings.md

@@ -0,0 +1,36 @@
+---
+name: gsd:settings
+description: Configure GSD workflow toggles and model profile
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+<objective>
+Interactive configuration of GSD workflow agents and model profile via multi-question prompt.
+
+Routes to the settings workflow which handles:
+- Config existence ensuring
+- Current settings reading and parsing
+- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
+- Config merging and writing
+- Confirmation display with quick command references
+</objective>
+
+<execution_context>
+@./.claude/get-shit-done/workflows/settings.md
+</execution_context>
+
+<process>
+**Follow the settings workflow** from `@./.claude/get-shit-done/workflows/settings.md`.
+
+The workflow handles all logic including:
+1. Config file creation with defaults if missing
+2. Current config reading
+3. Interactive settings presentation with pre-selection
+4. Answer parsing and config merging
+5. File writing
+6. Confirmation display
+</process>

package/.claude/commands/gsd/update.md

@@ -0,0 +1,37 @@
+---
+name: gsd:update
+description: Update GSD to latest version with changelog display
+allowed-tools:
+  - Bash
+  - AskUserQuestion
+---
+
+<objective>
+Check for GSD updates, install if available, and display what changed.
+
+Routes to the update workflow which handles:
+- Version detection (local vs global installation)
+- npm version checking
+- Changelog fetching and display
+- User confirmation with clean install warning
+- Update execution and cache clearing
+- Restart reminder
+</objective>
+
+<execution_context>
+@./.claude/get-shit-done/workflows/update.md
+</execution_context>
+
+<process>
+**Follow the update workflow** from `@./.claude/get-shit-done/workflows/update.md`.
+
+The workflow handles all logic including:
+1. Installed version detection (local/global)
+2. Latest version checking via npm
+3. Version comparison
+4. Changelog fetching and extraction
+5. Clean install warning display
+6. User confirmation
+7. Update execution
+8. Cache clearing
+</process>

package/.claude/commands/gsd/verify-work.md

@@ -0,0 +1,38 @@
+---
+name: gsd:verify-work
+description: Validate built features through conversational UAT
+argument-hint: "[phase number, e.g., '4']"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Edit
+  - Write
+  - Task
+---
+<objective>
+Validate built features through conversational testing with persistent state.
+
+Purpose: Confirm what Claude built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
+
+Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd:execute-phase
+</objective>
+
+<execution_context>
+@./.claude/get-shit-done/workflows/verify-work.md
+@./.claude/get-shit-done/templates/UAT.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS (optional)
+- If provided: Test specific phase (e.g., "4")
+- If not provided: Check for active sessions or prompt for phase
+
+Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
+</context>
+
+<process>
+Execute the verify-work workflow from @./.claude/get-shit-done/workflows/verify-work.md end-to-end.
+Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
+</process>

package/.claude/commands/inbox.md

@@ -0,0 +1,296 @@
+---
+description: Lista arquivos pendentes de processamento no INBOX
+---
+
+# INBOX - Verificar e Organizar Arquivos
+
+> **Versão:** 2.0.0
+> **Alias:** `/i`
+
+---
+
+## SINTAXE
+
+```
+/inbox [FLAGS]
+```
+
+| Flag | Descrição |
+|------|-----------|
+| (nenhuma) | Lista arquivos pendentes de processamento |
+| `--pending` | Mesmo que padrão |
+| `--all` | Lista todos (processados e pendentes) |
+| `--person "Nome"` | Filtra por pessoa |
+| `--organize` | Preview da auto-organização (dry-run) |
+| `--organize --execute` | Executa auto-organização |
+
+---
+
+## EXECUÇÃO
+
+### Step 1: Scan INBOX
+```
+SCAN /inbox/ recursively for .txt, .md, .pdf files
+
+FOR each file:
+  CHECK if file exists in CHUNKS-STATE.json (already processed)
+  GET file metadata: size, date added, word count
+  DETECT person from path
+```
+
+### Step 2: Categorizar
+```
+PENDING = files NOT in CHUNKS-STATE.json
+PROCESSED = files IN CHUNKS-STATE.json
+
+IF --all: show both
+IF --person: filter by person
+ELSE: show only PENDING
+```
+
+### Step 3: Gerar INBOX STATUS
+```
+═══════════════════════════════════════════════════════════════════════════════
+                              INBOX STATUS
+                         {TIMESTAMP}
+═══════════════════════════════════════════════════════════════════════════════
+
+📥 AGUARDANDO PROCESSAMENTO: {COUNT}
+
+   1. {PERSON}/PODCASTS/{filename}.txt
+      ├─ Adicionado: {relative_date} | ~{WORD_COUNT} palavras
+      └─ Comando: /process-jarvis "inbox/{full_path}"
+
+   2. {PERSON}/MASTERCLASS/{filename}.txt
+      ├─ Adicionado: {relative_date} | ~{WORD_COUNT} palavras
+      └─ Comando: /process-jarvis "inbox/{full_path}"
+
+───────────────────────────────────────────────────────────────────────────────
+
+📊 POR PESSOA:
+   • {PERSON_1}: {COUNT} arquivo(s)
+   • {PERSON_2}: {COUNT} arquivo(s)
+
+⭐️ AÇÃO RÁPIDA
+   Processar todos: /process-inbox --all
+   Processar próximo: /process-inbox --next
+   Processar pessoa: /process-inbox --person "Nome"
+
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+---
+
+## OUTPUT SE VAZIO
+
+```
+═══════════════════════════════════════════════════════════════════════════════
+                              INBOX STATUS
+                         {TIMESTAMP}
+═══════════════════════════════════════════════════════════════════════════════
+
+✅ INBOX LIMPO - Nenhum arquivo pendente de processamento
+
+📊 TOTAIS:
+   • Arquivos processados: {COUNT}
+   • Pessoas no sistema: {COUNT}
+   • Último processamento: {DATE}
+
+⭐️ PRÓXIMOS PASSOS
+   Adicionar material: /ingest [URL ou PATH]
+   Ver estado do sistema: /system-digest
+
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+---
+
+## OUTPUT COM --all FLAG
+
+```
+═══════════════════════════════════════════════════════════════════════════════
+                         INBOX COMPLETO
+                         {TIMESTAMP}
+═══════════════════════════════════════════════════════════════════════════════
+
+📥 PENDENTES: {COUNT}
+   [lista como acima]
+
+✅ PROCESSADOS: {COUNT}
+
+   1. {PERSON}/PODCASTS/{filename}.txt
+      ├─ Processado: {DATE} | Source ID: {ID}
+      └─ Chunks: {N} | Insights: {N}
+
+   2. {PERSON}/MASTERCLASS/{filename}.txt
+      ├─ Processado: {DATE} | Source ID: {ID}
+      └─ Chunks: {N} | Insights: {N}
+
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+---
+
+## EXEMPLOS
+
+```bash
+# Ver pendentes
+/inbox
+
+# Ver tudo
+/inbox --all
+
+# Filtrar por pessoa
+/inbox --person "Cole Gordon"
+
+# Preview de organização (dry-run)
+/inbox --organize
+
+# Executar organização
+/inbox --organize --execute
+```
+
+---
+
+## 🤖 AUTO-ORGANIZAÇÃO
+
+### Processo (7 Steps)
+
+```
+┌─────────────────────────────────────────────────────────────────────────────┐
+│  STEP 1: SCAN                                                               │
+│  └─ Listar todos os arquivos em inbox/ recursivamente                    │
+│                                                                             │
+│  STEP 2: DETECT SOURCE                                                      │
+│  └─ Identificar pessoa/empresa pelo nome do arquivo ou conteúdo             │
+│                                                                             │
+│  STEP 3: DETECT TYPE                                                        │
+│  └─ Classificar tipo de conteúdo (PODCASTS, COURSES, etc.)                  │
+│                                                                             │
+│  STEP 4: STANDARDIZE                                                        │
+│  └─ Padronizar nome do arquivo (CAIXA ALTA, [youtube link])                 │
+│                                                                             │
+│  STEP 5: ORGANIZE                                                           │
+│  └─ Mover para pasta correta: {PESSOA}/TIPO/                                │
+│                                                                             │
+│  STEP 6: HASH                                                               │
+│  └─ Calcular MD5 para rastreabilidade                                       │
+│                                                                             │
+│  STEP 7: REGISTRY                                                           │
+│  └─ Registrar em INBOX-REGISTRY.md com status NEW                           │
+└─────────────────────────────────────────────────────────────────────────────┘
+```
+
+### Detecção de Fonte
+
+| Padrão no Nome/Conteúdo | Pessoa Detectada | Empresa |
+|-------------------------|------------------|---------|
+| hormozi, alex, acquisition | ALEX HORMOZI | ALEX HORMOZI |
+| cole, gordon, closers | COLE GORDON | COLE GORDON |
+| jordan, lee, ai business | JORDAN LEE | AI BUSINESS |
+| jeremy, haynes, jeremy haynes program | JEREMY HAYNES | JEREMY HAYNES PROGRAM |
+| sam, ovens, setterlun | SAM OVENS | SETTERLUN UNIVERSITY |
+
+### Detecção de Tipo
+
+| Padrão | Tipo Detectado |
+|--------|----------------|
+| podcast, episode, entrevista | PODCASTS |
+| mastermind, summit, evento | MASTERMINDS |
+| course, module, aula, treinamento | COURSES |
+| blueprint, playbook, pdf, doc | BLUEPRINTS |
+| vsl, sales letter, oferta | VSL |
+| script, copy, template | SCRIPTS |
+
+### Output do --organize (Dry-Run)
+
+```
+═══════════════════════════════════════════════════════════════════════════════
+                         INBOX AUTO-ORGANIZE (PREVIEW)
+                              {TIMESTAMP}
+═══════════════════════════════════════════════════════════════════════════════
+
+📋 AÇÕES PLANEJADAS: {COUNT}
+
+   1. 📁 MOVER: how-i-scaled-sales.txt
+      ├─ De: inbox/
+      ├─ Para: inbox/alex hormozi/PODCASTS/
+      ├─ Renomear: HOW I SCALED MY SALES TEAM.txt
+      └─ Detectado: Fonte=HORMOZI | Tipo=PODCAST
+
+   2. 📁 CRIAR PASTA: inbox/JEREMY HAYNES (JEREMY HAYNES PROGRAM)/COURSES/
+      └─ Motivo: Novo conteúdo detectado
+
+   3. 📁 MOVER: client-accelerator-module1.txt
+      ├─ De: inbox/
+      ├─ Para: inbox/JEREMY HAYNES (JEREMY HAYNES PROGRAM)/COURSES/
+      └─ Detectado: Fonte=JEREMY | Tipo=COURSE
+
+───────────────────────────────────────────────────────────────────────────────
+
+📊 RESUMO:
+   • Arquivos a mover: {N}
+   • Pastas a criar: {N}
+   • Arquivos a renomear: {N}
+   • Sem mudança: {N}
+
+⚠️ NENHUMA AÇÃO EXECUTADA (dry-run)
+   Para executar: /inbox --organize --execute
+
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+### Output do --organize --execute
+
+```
+═══════════════════════════════════════════════════════════════════════════════
+                         INBOX AUTO-ORGANIZE (EXECUTADO)
+                              {TIMESTAMP}
+═══════════════════════════════════════════════════════════════════════════════
+
+✅ AÇÕES EXECUTADAS: {COUNT}
+
+   1. ✅ MOVIDO: how-i-scaled-sales.txt → ALEX HORMOZI/PODCASTS/
+   2. ✅ CRIADA PASTA: JEREMY HAYNES (JEREMY HAYNES PROGRAM)/COURSES/
+   3. ✅ MOVIDO: client-accelerator-module1.txt → JEREMY HAYNES/COURSES/
+
+───────────────────────────────────────────────────────────────────────────────
+
+📊 RESUMO:
+   • Arquivos movidos: {N}
+   • Pastas criadas: {N}
+   • Arquivos renomeados: {N}
+   • Erros: {N}
+
+⭐️ PRÓXIMOS PASSOS:
+   Ver status atualizado: /inbox
+   Processar arquivos: /process-inbox --all
+
+═══════════════════════════════════════════════════════════════════════════════
+```
+
+### Workflow Recomendado
+
+| Passo | Comando | Descrição |
+|-------|---------|-----------|
+| 1 | `/inbox --organize` | Preview das ações (seguro) |
+| 2 | Revisar output | Verificar se detecções estão corretas |
+| 3 | `/inbox --organize --execute` | Executar organização |
+| 4 | `/inbox` | Confirmar novo estado |
+| 5 | `/process-inbox --all` | Processar arquivos organizados |
+
+---
+
+## INTEGRAÇÃO COM PIPELINE
+
+Após organização, arquivos ficam prontos para Pipeline Jarvis:
+
+```
+inbox/{PESSOA}/{TIPO}/{arquivo}.txt
+       │
+       └──→ /process-jarvis "inbox/{path}"
+              │
+              └──→ processing/ (chunks, insights, narratives)
+                      │
+                      └──→ knowledge/dossiers/ (output final)
+```