Load the jarvis-start skill's rules first (keys, money and safe-install rules apply to every task).
- Read
./.jarvis/state.jsonand./.jarvis/tasks.json. Missing → say there's no build in progress and offer/jarvis-start. - Restate the RUNNING BRIEF from
state.json → briefin ≤5 lines. - Flags:
--list→ printNN · status · titlefor every task (👤 foruser_action) and stop.--task <id>→ work on that task if its dependencies aredone; otherwise say which aren't.--done <id>→ run that task's full verify list; markdoneonly if every command exits 0.
- No flag:
- A task left
in_progress= crash recovery. Re-run its verify list. All pass → markdone(commit + tag). Otherwise continue that task. - Else pick the first
pendingtask (array order) whose dependencies are alldone.
- A task left
- Execute it per
questions/4-construir.mdStep 2. One task per invocation unless the person says "sigue con todo" — then loop, pausing at everyuser_actionand every task with acost. - After the last task: move to VERIFY (smoke test +
jarvis-validator) as inquestions/4-construir.md.
Never re-plan, never invent tasks, never edit a verify command to make it pass. If the plan is wrong, say so and offer to go back to ARCHITECTURE for that slot.