forge-add-task

name	forge-add-task
description	Adiciona uma task a um slice existente.
disable-model-invocation	true
allowed-tools	Read, Write, Edit, Glob

Bootstrap guard (sempre executar primeiro)

Before doing anything else, run:

ls CLAUDE.md 2>/dev/null && echo "ok" || echo "missing"
ls .gsd/STATE.md 2>/dev/null && echo "ok" || echo "missing"

Se CLAUDE.md não existe: Stop and tell the user:

Projeto não inicializado. Execute /forge-init primeiro — isso cria o CLAUDE.md que restaura o contexto automaticamente ao reabrir o chat.

Se .gsd/STATE.md não existe: Stop and tell the user:

Nenhum projeto GSD encontrado neste diretório. Execute /forge-init para começar.

Se .gsd/AUTO-MEMORY.md não existe: Create it silently before proceeding:

<!-- gsd-auto-memory | project: <from PROJECT.md or directory name> | extraction_count: 0 -->
<!-- ranked by: confidence × (1 + hits × 0.1) | cap: 50 active -->

---

Input

$ARGUMENTS

Parse the input

• Token matching S\d+ → slice ID (use active slice from STATE.md if not specified)
• Token matching T\d+ → specific task ID to plan (plan next available ID if not specified)
• Remaining text → task description / goal

Your job

1. Read slice context:

   • Active M###-ROADMAP.md — which milestone owns this slice?
   • S##-PLAN.md — existing tasks, next task ID (T0N+1), slice must-haves
   • S##-CONTEXT.md — slice-level decisions (if exists)
   • M###-CONTEXT.md — milestone architecture decisions
   • .gsd/DECISIONS.md — locked decisions
   • Summaries from completed tasks in this slice (for continuity)

2. Write T##-PLAN.md:

   # T##: Task Title
   
   **Slice:** S##
   **Milestone:** M###
   
   ## Goal
   One sentence.
   
   ## Must-Haves
   
   ### Truths
   - Observable outcome 1
   
   ### Artifacts
   - `path/to/file.ts` — description (min N lines, exports: ...)
   
   ### Key Links
   - `file-a.ts` → `file-b.ts` via import of functionX
   
   ## Steps
   1. ...
   
   ## Context
   - Relevant prior decisions
   - Key files to read first
   

3. Update S##-PLAN.md — add - [ ] **T##: Title** entry

4. Update STATE.md if this task is now the active one — Read it first before writing

5. Report: task ID, goal, must-haves count, estimated complexity

Iron rule: If the task as described won't fit in one context window (~200k tokens), split it into two tasks and plan both.