Stats
Actions
Available In
Tags
Plugin
spec-ops
Spec workflow by Zak Sakata: write-spec is the workflow entrypoint that turns a bare idea into a spec — eliciting and distilling requirements (full rigor) before drafting concise, scannable feature specs at a requested rigor (light/standard a code-free, implementation-agnostic WHAT to full deep spec that may pin implementation) that open with a flat, id'd Acceptance Criteria contract (optionally organized into ordered named groups); refine-spec hardens a draft into an accurate, not-over-engineered, implementation-ready spec via a grounded multi-pass review loop, commits the grounded AC group order, and hunts unstated non-functional constraints; launch-spec compiles a verified spec into one of three drivers (/goal, ultracode, /batch), each completed by a verify-spec gate on every acceptance criterion (emit-only), phasing a large or hard-sequenced build by AC group; verify-spec checks that the implementation actually matches the spec's claims and every acceptance criterion, grounded against the real code, git history, and live state — scaling each criterion's evidence standard and recording a per-AC verification method — and flags delivered code that maps to no criterion (backward coverage); on a spec re-run it drifts against the last clean verification, re-grounding only criteria whose evidence moved and flagging regressions. spec-ops commits the spec artifact at each stage (write the draft, refine the ready spec with Stop-hook enforcement, launch bakes a per-phase commit cadence into the /goal driver), each commit scoped to the spec file and never pushed. A verify→refine handoff carries verify-spec's backward-sweep proposed ACs to refine-spec via /tmp (hook-written), so a missed-requirement finding amends the spec on the next refine run without re-keying; verify stays read-only.
