Step 2: Backlog

Skill: fireskill-02-backlog · Asks questions: yes, one per round, up to 8 per area · Creates: specs/backlog/<NNNN>-<slug>.md

When to use it

You have an idea (in specs/inbox/ or just in your head) and want it turned into something a spec can be written from.

What to type

Use $fireskill-02-backlog para pesquisar referências, registrar ou atualizar o item, resolver lacunas por perguntas adaptativas e executar transições automáticas até $fireskill-03-specify.

Add the idea, or the path of the inbox file, below it:

Refine specs/inbox/2026-09-18-174245-convite-de-membros-por-e-mail.md

What the agent does

1. Looks for duplicates and references in specs/inbox/, specs/backlog/, specs/<state>/*/spec.md and docs/, and shows you any material match with its path. If it looks like a duplicate, it asks whether to update the existing item or record a real difference.
2. Checks the minimum capture: the problem, the person affected, the expected result and enough context to tell this idea from similar ones. If one is missing, it asks about the one with the biggest impact. It does not create the file until these are clear.
3. Creates the item with fireskills/skills/fireskill-02-backlog/scripts/iniciar_backlog.mjs. The inbox file is only referenced, never changed or moved.
4. Deepens the decisions by numbered questions, choosing each time the gap with the highest impact times uncertainty. It reads what already exists first (rules, stack, screens) so it does not ask what the project already answers.
   • If the delivery has a screen, Interface becomes its own area: screens, information flow, menus, forms, where the action happens (page, side panel, modal). It loads $fireskill-specialist-interface-experience, -ux-design, -ui-design and -nuxt-ui, and offers options compatible with the current screens. Any CRUD must register UTable (with enterpriseTableUi), filters, UForm, UModal or USlideover, and the states.
   • If the idea needs stored information, it hands off to $fireskill-data-discovery, which talks in everyday language and records confirmed answers in .fireskills/DATABASE.md.
5. Closes with a Brief pronto para especificar: problem and goal, actors, scope and out of scope, journeys and essential rules, acceptance criteria in Given/When/Then, technical and quality constraints, assumptions, open decisions (or Nenhuma lacuna aplicável), ambiguous vocabulary.
6. Hands off to $fireskill-03-specify (Transição automática: $fireskill-02-backlog → $fireskill-03-specify).

What you will be asked

A round looks like this (always in Portuguese):

Pergunta 1. <pergunta específica sobre a lacuna de maior impacto>
1. <opção sugerida>
2. <opção sugerida>
3. <opção sugerida>
4. Escrever outra resposta
5. Gere outras opções
6. Avançar

At the eighth question in an area the agent summarizes, records what is open and stops. Avançar at any point ends the questions for that area without filling anything by inference; the spec then stays Draft with Definition Gate: Pending.

Result

specs/backlog/0001-convite-de-membros-por-e-mail.md:

# Backlog: Convite de membros por e-mail

| Metainformação | Valor |
| --- | --- |
| ID | BACKLOG-0001 |
| Status | Captured |
| Produto | A esclarecer |
| Épico | A esclarecer |
| Prioridade | Não priorizado |
| Spec promovida | Nenhuma |

The Status moves Captured → Refining → Ready for specification → Promoted (when a spec exists). The backlog item is a brief, not a source of requirements: the spec is.

Starting from an MVP document

If you have an MVP.md at the repository root, use $fireskill-mvp-milestone-interviewer instead: it imports it and creates one backlog item and one Draft spec per development requirement. See Other entry points.

Next

Automatic: Step 3: Specify.