Step 5: Tasks

Skill: fireskill-05-tasks · Asks questions: no (goes back to the backlog if a decision is missing) · Changes: sections 14 and 15 of spec.md; moves the spec to specs/planned/

When to use it

The spec has Definition Gate: Passed and sits in specs/defined/. The flow gets here by itself after Step 4.

What to type

Use $fireskill-05-tasks para preencher tarefas rastreáveis com checklist PREP/EXECUTE/VERIFY/VISUAL/EVIDENCE/IMPROVE em specs/<estado>/<NNNN>-<slug>/spec.md. Orquestre transições automáticas com anúncio, execução e retomada na mesma conversa.

What the agent does

1. Requires Formato: Specsfy/2.0, Definition Gate: Passed and Status: Defined. It runs the context monitor and inspects the real stack, commands and paths (layers/*, apps/*) before it writes anything.
2. Replaces only sections 14. Tarefas and 15. Ordem de execução of the same spec.md. It never creates tasks.md.
3. Writes each task in this format:
   - [ ] T001 [TEST] [TDD] [US-001] Derivar teste Vitest do BDD da spec em layers/teams/shared/utils/abilities.test.ts — Refs: FR-002, AC-003 — Depends: none
   - [ ] T002 [CODE] [US-001] Implementar validação em layers/teams/server/trpc/teams.ts — Refs: FR-002, AC-003 — Depends: T001
   

   
   Allowed tags after the ID: [P] (can run in parallel), [TEST], [TDD], [CODE], [DOC], [OPS], [US-NNN], and [MIGRATION] together with [CODE] or [OPS].
4. Gives every task the same checklist, in this order:
     - [ ] **PREP**: Confirmar escopo, IDs, dependências e baseline.
     - [ ] **EXECUTE**: Produzir a entrega no caminho declarado.
     - [ ] **VERIFY**: Executar a verificação focal adequada.
     - [ ] **VISUAL**: Conferir bordas, espaçamentos, margens, padding e tipografia do sistema; se não houver interface, registrar `Não aplicável` e o motivo.
     - [ ] **EVIDENCE**: Registrar comando, resultado e IDs nas seções 11–13.
     - [ ] **IMPROVE**: Registrar melhoria aplicada ou ausência justificada.
   

5. Applies the rules that come from the spec:
   • one [TEST] [TDD] task per AC, and every [CODE] task depends on its TDD predecessor with a valid RED;
   • a separate [CODE] [MIGRATION] task whenever the schema changes, pointing at a versioned file in apps/functions/src/database/migrations/ (generated by drizzle-kit generate). Its VERIFY records two commands approved by check_database_safety.mjs: one applies the migration to the test database, one queries the migration state;
   • a [DOC] task for .fireskills/STACK.md when manifests or structure change, and for .fireskills/DATABASE.md when the database changes;
   • for a screen: tasks for each screen, menus, forms and actions, in a subsection #### Fase de interface, and a task that updates .fireskills/INTERFACE.md. Every task that writes a .vue with U* components lists $fireskill-specialist-nuxt-ui in PREP.
6. Validates:
   node fireskills/skills/fireskill-05-tasks/scripts/validate_tasks.mjs specs/defined/<NNNN>-<slug>/spec.md --allow-draft
   node fireskills/skills/fireskill-05-tasks/scripts/validate_interface_tasks.mjs specs/defined/<NNNN>-<slug>/spec.md
   

   
   The second one runs when the delivery has a screen. Up to three fix cycles.
7. While Plan Gate: Pending, it hands off to $fireskill-06-tdd-bdd in prepare mode to write the first failing test (see Step 6), then resumes: Plan Gate: Passed, Status: Planned, result written to section 13, and bun run fireskill transition <id> planned.

If validation fails, the spec stays Defined with Plan Gate: Failed, and the agent reports what blocks it.

Result

A spec.md in specs/planned/<NNNN>-<slug>/ with the full task list, ordered by dependency, and Plan Gate: Passed.

Next

Automatic: Step 7: Implement, after the failing tests of Step 6 exist.