Late Changes

Skill: fireskill-update-spec · Asks questions: only when options change the result materially · Changes: spec.md and only the gates that the change invalidates

When to use it

A spec has already passed the Definition Gate (it is Defined, Planned, Implementing, Reviewing or Complete) and you want to add, remove, fix or change something. For a spec still in Draft that never passed the gate, use Step 3: Specify instead.

What to type

Use $fireskill-update-spec para incorporar este novo pedido à especificação existente e orquestrar transições automáticas até a retomada.

specs/planned/0001-convite-de-membros-por-e-mail/spec.md
O link do convite agora expira em 24 horas, não em 48.

What the agent does

1. Keeps your request word for word before interpreting it, then finds the spec and reads its header, requirements, scenarios, plan, tasks, gates and evidence. Existing Git changes in the spec are not attributed to your request.
2. Classifies the change before writing:

   Change	What it does
   internal, reversible, no observable effect	does not touch the spec; records the assessment in the task evidence and resumes implementation
   editorial, same meaning	edits the wording only; keeps status and gates
   behavior, acceptance, scope, data, security or interface	reopens from Act I: Status: Draft, all three gates Pending
   only solution, tasks or test strategy	reopens from Act II: Status: Defined, Definition Gate stays Passed, Plan Gate and Delivery Gate become Pending
   a new, independent capability	does not add it silently: goes to $fireskill-02-backlog or $fireskill-03-specify

3. Edits only spec.md (and the indexed research/). It keeps existing IDs and never renumbers. For a behavior change, it records reason, decision and impacted IDs in section 17. It never creates change-request.md or any parallel file.
4. Projects the impact (read only):
   node fireskills/skills/fireskill-update-spec/scripts/analyze_change.mjs specs/<state>/<NNNN>-<slug>/spec.md --base HEAD --mode impact
   

   
   --mode changelog lists the IDs added, removed and changed.
5. Runs the structural validation (validate_spec.mjs … --allow-draft) and resumes the flow:
   • change from Act I: $fireskill-04-validate, then tasks, TDD/BDD and the step that raised the change;
   • change only in Act II: $fireskill-05-tasks, which reconciles the plan, calls $fireskill-06-tdd-bdd and resumes;
   • change found during implementation: $fireskill-07-implement resumes only when Definition and Plan Gates are Passed again and a valid RED exists for the new behavior;
   • change after Complete: the invalidated acts run again and Complete returns only with Delivery Gate and the Definition of Done proven; the spec goes back to review first.

Historic evidence is never rewritten as if it had been produced for the new request: proof that depends on the invalidated version is marked pending.

The folder moves

bun run fireskill transition allows going back one step (completed → review, review → in-progress, in-progress → planned, planned → defined, defined → draft), never by jumping. The skill uses it as needed.

Next

The flow resumes by itself at the step that raised the change.