workflow-feature-shipper
Use when you need to ship a single PR-sized feature end-to-end (plan - implement - verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
- Installs
- 50
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/heyvhuang/ship-faster --skill workflow-feature-shipper- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads workflow-feature-shipper automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Feature Shipper
Turn "I want to build a feature" into a fast execution chain.
Input (Pass Paths Only)
feature.md: Requirements description (acceptance criteria + non-goals)repo_rootrun_dir
Optional flags (recommended inside feature.md)
mode:plan-only|execute(default:execute)feature_slug: short slug for artifact naming (default: derived from title + timestamp)quality_bar:demo-ready|functional-only(default:demo-readyfor user-facing UI features)
Output (Persisted)
evidence/features/<feature_slug>-plan.md(checklist plan: tasks + verification)evidence/parallel/features/<feature_slug>/(if implementation is split)evidence/features/<feature_slug>-summary.md
Process
- Hooks doctor (required check; non-blocking): Run
tool-hooks-doctoronce at the start of the session to verifyskill-evolutionhooks are enabled. If missing, offer to install project-level hooks; continue either way. - Read
feature.md, normalize into: acceptance criteria, boundaries, risks, rollback. - Prototype UI rule (default): if this feature affects user-facing UI and
quality_barisn’tfunctional-only, propose 1 “demo moment” (animation/micro-interaction) and add it to acceptance criteria. Must respectprefers-reduced-motion. - Produce 2 options (A: minimal; B: cleaner but slower), default to A. If user cares about “demo feel”, offer A-demo-ready vs A-functional-only as explicit sub-options.
- Split into PR-sized small steps (each independently runnable + rollback-able).
- Write plan to
evidence/features/<feature_slug>-plan.md. - If
mode: plan-only, stop here and ask for confirmation before implementing. - Implement (batch execution + checkpoints):
- UI visual/layout/animation changes → First call
tool-design-style-selectorto load the project’sdesign-system.md, then strictly follow it. Iftool-ui-ux-pro-maxis installed, use it to ground motion/UX constraints (search “animation” + “accessibility”). For complex visual/animation/responsive design, delegate to/geminifrontend UI/UX senior design agent. - Business logic/data flow/integration → Implement directly.
- Default batch rhythm: 3 small tasks per batch → run verification → report and wait for feedback; stop immediately for help when blocked/verification fails.
- After each batch (or before merge), recommend using
review-qualityfor a conclusive review + verdict.review-qualityis the single entry point and will auto-triage: if React/Next.js performance risk is detected, it will also runreview-react-best-practices.- If the user explicitly wants only a React/Next.js perf audit, run
review-react-best-practicesdirectly.
- UI visual/layout/animation changes → First call
- Verification: can run, can build (and existing tests pass).
- If verification fails (tests/build/runtime error): run
tool-systematic-debuggingbefore attempting more fixes. - Persist debugging artifacts to:
evidence/features/<feature_slug>-debug.md(repro steps, hypotheses, root cause, fix + re-verify)
- If verification fails (tests/build/runtime error): run
- Write
evidence/features/<feature_slug>-summary.md: what was done, how verified, next steps. - Wrap up: Do a
skill-evolutionEvolution checkpoint (3 questions); if user chooses "want to optimize", runskill-improverbased on thisrun_dirto produce minimal patch suggestions
Delivery Requirements
- No "big bang" refactoring
- Don't introduce new complexity (unless it significantly reduces future cost, and user confirms)
FAQ
What does the workflow-feature-shipper skill do?
Use when you need to ship a single PR-sized feature end-to-end (plan - implement - verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
How do I install workflow-feature-shipper?
Run npx skills add https://github.com/heyvhuang/ship-faster --skill workflow-feature-shipper in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/workflow-feature-shipper/ (personal) or .claude/skills/workflow-feature-shipper/ (project).
Which AI agents can use workflow-feature-shipper?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is workflow-feature-shipper safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains workflow-feature-shipper?
It is published by heyvhuang in heyvhuang/ship-faster. It has 50 recorded installs.
More from heyvhuang/ship-faster
mcp-stripe
heyvhuang/ship-faster
Stripe MCP transaction operations skill. Execute transaction operations via Stripe MCP server (https://mcp.stripe.com): customer management, products/prices, invoices, payment links, subscriptions, refunds, dispute handling, balance queries. Triggers: user requests Stripe operations including create customer, create product, create invoice, generate payment link, query transactions, process refunds, manage subscriptions, view disputes, check balance, etc.
mcp-supabase
heyvhuang/ship-faster
Execute database operations via Supabase MCP (query/write/migration/logs/type generation). Triggers: query/statistics/export/insert/update/delete/fix/backfill/migrate/logs/alerts/type generation. Does not trigger for: pure architecture discussion or code planning. Write operations require confirmation; UPDATE/DELETE without WHERE is refused.
review-doc-consistency
heyvhuang/ship-faster
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
tool-ast-grep-rules
heyvhuang/ship-faster
Write AST-based code search and rewrite rules using ast-grep YAML. Create linting rules, code modernizations, and API migrations with auto-fix. Use when the user mentions ast-grep, tree-sitter patterns, code search rules, lint rules with YAML, AST matching, or code refactoring patterns.
tool-openclaw
heyvhuang/ship-faster
Help users install, configure, operate, and migrate OpenClaw (gateway, channels, nodes, plugins, model/auth setup). Use when answering OpenClaw setup/debug questions or model migration questions; use the local docs snapshot bundled with this skill as the source of truth. Triggers: openclaw, clawdbot, clawd, clawdhub, gateway, onboard, channels login, whatsapp, telegram, discord, mattermost, pairing, nodes, sandboxing, tailscale, provider migration, Claude to GPT, model swap.
tool-ui-ux-pro-max
heyvhuang/ship-faster
Use when you need concrete UI/UX inputs (palette, typography, landing patterns, UX/a11y constraints) to drive design or review. Searchable UI/UX design intelligence (styles, palettes, typography, landing patterns, charts, UX/a11y guidelines + stack best practices) backed by CSV + a Python search script. Triggers: UIUX/uiux, UI/UX, UX design, UI design, design system, design spec, color palette, typography, layout, animation, accessibility/a11y, component styling. Actions: search, recommend, review, improve UI.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.