project-fast-status - SKILL.md Agent Skill

name: project-fast-status description: Mandatory fast-flow tracker that updates status.json after each fast stage and before handoff or escalation

Use `status.json` as the single source of truth for fast-planning phase and stage Strictly track progress, blockers, gate decision, and next action Prevent moving to the next fast-flow step without a status update This skill is mandatory for fast planning Run at the start of fast flow to initialize `status.json` Run after every step: init, pulse-scan, stack-pick, proto-spec, task-blast Run at the end of fast flow for the final gate decision If `status.json` is not updated, the step is considered incomplete Fast planning start (create initial status) After each fast-flow stage is completed Before handoff to implementation or escalation to standard flow Current fast-flow step (init, pulse-scan, stack-pick, proto-spec, task-blast) Actual step result: done/partial/blocked Short reasons and blockers list (if any) Risks, corrective actions, recheck criteria File: `status.json` Format: valid JSON without comments Updated atomically on every run of this skill phase stage step_status gate reasons blockers next_action updated_at If gate != PASS: `corrective_actions` and `recheck_criteria` are required If step_status = blocked: `owner` and `unblock_plan` are required fast-planning init pulse-scan stack-pick proto-spec task-blast finalize done partial blocked PASS CONCERNS FAIL Check `status.json`; if missing, create it with a base structure Set current `phase` and `stage` according to the actual step Update `step_status`, `reasons`, `blockers`, and `next_action` If this is fast-flow finalization, set `gate` based on all stage outcomes For `CONCERNS` or `FAIL`, add `corrective_actions` and `recheck_criteria` Update `updated_at` and save valid JSON

phase

stage

step_status

gate

reasons

blockers

next_action

corrective_actions (if gate != PASS)

recheck_criteria (if gate != PASS)

updated_at

`status.json` always reflects the actual current state Do not move to the next stage without recording the current result `next_action` is specific and executable as one next step Reasons and blockers are verifiable and not vague Do not leave `status.json` outdated after step completion Do not set `PASS` when critical blockers exist Do not write free text instead of structured JSON fields {"phase":"fast-planning","stage":"proto-spec","step_status":"done","gate":"CONCERNS","reasons":["NFR is only partially refined"],"blockers":["No confirmation for integration X"],"next_action":"Close integration risk and update proto-spec","corrective_actions":["Run API X contract verification"],"recheck_criteria":["Integration risk is closed","AC remain unchanged"],"updated_at":"2026-02-09T12:00:00Z"}