ship-feature

End-to-end feature delivery conductor for your product. Takes ONE feature (inline description or a markdown file) and drives it from a bare idea to merged, tested, production code by orchestrating the existing skills in a single in-session flow: design-craft (represent the whole feature UI in the design-system elements/composites/mock-pages, grounded in the repo's design system — e.g. apps/web-design-system — plus an optional DESIGN.md design-language spec when provided or present, and any provided HTML/CSS/JS mock) → triage (spec) → plan → work (isolated worktree) → a deferred-work loop (re-work, or child triage+plan+work for extra phases, all on the SAME branch) → gap-fix → acceptance-e2e (a comprehensive Playwright suite over every user flow/action/menu, run against the feature branch locally and fixed) → finalize (commit → rebase → merge into the integration branch → push → clean up worktree(s)). Stays in-session to keep the accumulated feature context across every stage and leans on the on-disk spec/plan/mock artifacts as durable, resumable memory; one feature = one branch = one worktree, with the merge behind a fail-closed pre-merge gate. Builds on the design-craft, feature-spec-pipeline, and acceptance-e2e plugins.