skills/woostack-status/SKILL.md
Use to show the derived woostack feature board — for every spec in .woostack/specs/ and fix in .woostack/fixes/, its reconciled phase, plan progress, increment-PR state, owner, age, and the single next action, plus flags for any drift between the authored status field and the artifacts on disk. Read-only; never fetches, commits, or pushes. Use for /woostack-status, "what's in flight", or "what should I do next".
npx skillsauth add howarewoo/woo-stack woostack-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Prints an on-demand, read-only feature board derived from the real .woostack/
artifacts. For every spec (in .woostack/specs/) and fix (in .woostack/fixes/) it shows
the reconciled phase, plan progress (N/M boxes), the increment-PR rollup, owner, age,
and the single concrete next action — and flags any drift.
The board is computed fresh each run and printed to the terminal. It never fetches, commits, or pushes.
The board is backed by the spec : plan : PRs = 1 : 1 : N invariant (for specs) and the phase
enum, both defined once in references/conventions.md. Fixes
under .woostack/fixes/ bypass the spec-to-plan join because they are self-contained: the file
acts as both the spec and the plan. This skill does not restate these definitions — that file is
the canonical home.
/woostack-status — render the in-flight feature board for the current project./woostack-status --all — also expand the done and abandoned features (hidden by
default, surfaced as a footer count)./woostack-status --fetch — opt in to a git fetch first so PR-less branch data is fresh.
This is the only network access the board ever does; it still never commits or pushes.Run the deriver. From the project root, resolve the installed skill directory, then
run the bundled script from that directory so it reads the project's ./.woostack:
WOO_STATUS_ACTION_PATH="<directory containing this SKILL.md>"
bash "$WOO_STATUS_ACTION_PATH/scripts/status.sh" [--all] [--fetch]
Keep the current working directory at the consumer project root; only the script path comes
from the skill bundle. WOO_DIR defaults to ./.woostack (override only for tests). The
script is read-only and exits 0 even when it emits drift flags — operational failure is
the only non-zero exit — so it is safe to run anywhere, including CI.
Narrate the board. Present the table as printed, then for each in-flight feature call
out its single next action (the NEXT column). Lead with whatever is actionable now.
Surface the flags. If the ! FLAGS block is non-empty, list each drift and what
resolves it — for example a second plan resolving to one spec, a blank or unknown
branch:, an unknown status: value, a head-state phase while a PR already exists, a
stale executing spec, or a same-branch collision. Flags are advisory, never a blocking
stop.
List open deferrals (read-only). Scan the working tree for deferral markers —
grep -rn 'woostack-defer(' . | grep -v '/.git/' (or a ripgrep equivalent) — and print each as
an open deferral: <file>:<line> — deferred to <ref>. These are the woostack-defer(<ref>)
markers woostack-execute writes for work a later increment completes (issue #224); a marker
still present after its increment landed is a stale deferral worth resolving. This is
read-only surfacing — never edit or remove a marker. Omit the section entirely when the scan
finds none. (A consumer repo carries the token only at real deferral sites. The woostack repo
itself also has illustrative woostack-defer(...) in skills/** / .woostack/ docs; exclude
those doc paths if the example noise distracts.)
Note degradation. If gh is absent or unauthenticated the board still renders,
omitting PR / increment / owner data for PR-phase rows; relay the script's notice rather
than hiding it. The footer also notes when PR-less branch data may be stale (pass
--fetch).
--fetch), commits, pushes, or mutates
any spec, plan, or git state. The board only reads.STATUS.md or any tracked
snapshot.status: for head states
but the computed phase for the execute → review → done band; a disagreement is a flag, not
displayed truth. The contracts live in
references/conventions.md — link it, do not restate it.gh, no specs, malformed frontmatter, or a missing
plan each produce a friendly notice or a flag and a clean exit, never a crash.testing
Use to curate the .woostack/ knowledge store. Reflects over the static memory store + docs (no session mining), then proposes a gated changeset that merges duplicate notes, replaces stale/contradicted ones, drops dead/orphaned notes, resolves conflicts, surfaces consolidated insights, and recommends evidence-guarded documentation edits. Nothing mutates before explicit approval; ends on a summary + iterate loop. Local-only memory (no commit); doc edits land in the working tree. Never commits or merges. Invoke via /woostack-dream [instructions].
development
woostack's canonical test-driven-development home and on-demand test-adder. The single source for the TDD kernel — Red→Green→Refactor, test-first, cover happy/error/edge/success+failure, framework-aware, no-runner→concrete verification — that woostack-plan, woostack-execute, woostack-debug, and bootstrap patterns.md §7 should link to instead of restating. Also the 14th public command: /woostack-tdd <target> adds appropriate tests to an existing code block, PR, spec, or plan — one verb, target-routed (code→colocated *.test files, PR→tests for the gh pr diff surface, spec→strengthen §7 acceptance criteria, plan→fill failing-test steps) — with a characterization carve-out for existing code (new code is red-first; existing code pins current behavior). Writes tests to the working tree and hands to woostack-commit; never commits, merges, or authors status:/branch:; owns no approval gate.
development
Use to resolve small technical issues (bugs, hotfixes, refactors) through a unified execution loop — diagnose root cause with woostack-debug, author a fix plan under .woostack/fixes/, harden, get explicit user approval, then delegate execution to woostack-execute (TDD per task, task review, commit via woostack-commit, distill).
development
Use to execute an approved woostack plan UNATTENDED overnight — one autonomous run with no user input after launch that drives every increment to a reviewed stack, swapping woostack-execute's stop-and-ask gates for resolve-or-log-and-continue (woostack-debug on stuck verifications; bounded auto-address on a blocking review; halt-the-track on anything unsafe or ambiguous), honoring optional `## Track:` grouping in the plan (independent, fault-isolated tracks run sequentially), and writing a morning report under .woostack/overnight/ for a human to test in the morning. It is the third choice at woostack-build's execution-handoff gate (Go / Hand off / Run overnight); also usable standalone via /woostack-execute-overnight <plan-path> [--inline|--subagent]. One plan per spec, multiple PRs per plan. Never merges; never relaxes safety for autonomy.