← ClaudeAtlas

workflow-statuslisted

Read-only workflow sensor: compute repository, roadmap, dependency, PR, finding, and recovery state, then emit the fixed machine envelope. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next", "state of the run".
gtrabanco/agentic-workflow · ★ 21 · AI & Automation · score 80
Install: claude install-skill gtrabanco/agentic-workflow
# Workflow Status (the orchestrator's sensor) One read-only pass over the project that answers, in a single fixed JSON envelope: **what exists, what is blocked on what, what is startable right now, and what the recommended next command is.** Built for external orchestrators (see `docs/workflow/ORCHESTRATION.md`) but equally useful to a human asking "where do we stand?". ## Turn contract — verify before ending the turn ``` ✓ Every claim comes from a RUN command or a READ file (git/forge output, roadmap, fix index, feature folders) — nothing inferred from memory ✓ Nothing was edited, committed, pushed, or created — read-only, always ✓ `next.recommended` is non-bare (carries the unit's slug/NN, never a bare `/plan-feature`) AND staged by the target unit's resolved status **and** its current pre-execution evidence: `idea`/undesigned → `/design-feature <slug>`; `defined` → `/plan-feature <slug>` only on a current `SPEC-REVIEW-PASS`, else `/review-spec <slug>`; `planned`/`in-progress` → `/execute-phase <NN>` only on a current `PLAN-REVIEW-PASS`, else `/review-plan <NN>` (step 6a) ✓ A missing or non-frozen repository-state ledger emits a machine-readable substrate blocker and routes to discovery or resolution before any unit is listed as startable ✓ Every `detail.design_candidates[].next` begins with `/design-feature ` — design candidates always route to design, regardless of anything else ✓ When `--last-envelope` is supplied: the no-progress guard ran (crash-re