feature-spec-pipeline

Four native skills that run a Linear-free, markdown-doc feature pipeline — /triage, /plan, /work, /gap-fix — entirely inside your interactive Claude Code session. /triage turns a feature idea (inline text or a notes file) into a versioned spec at docs/specs/spec-DIO-0001.md (id allocated from docs/feature-specs/LEDGER.md), running a codebase grounding pass plus a Specification Sentinel product/UX/compliance review and appending a non-technical readiness section. /plan classifies a tier, investigates the codebase, writes docs/plans/plan-DIO-0001.md and links it from the spec. /work implements the plan in an isolated worktree via dynamic ultracode workflows (understand, implement, rebase, acceptance review, resolve), appends a progress section to the spec, and leaves the branch local — no remote PR. /gap-fix runs after /work as the remediation step: it re-enters the work branch, always re-audits the delivered code against the original spec (merging in any human/QA gaps you provide), and implements the fixes in code (file-disjoint fan-out + typecheck gates), looping audit-fix until only optional Low items remain, then commits locally and appends a gap-fix progress note — no remote PR. A doc-driven sibling of linear-issue-pipeline that needs no Linear MCP.