workflow-feature-shipper

Turn feature.md into an executable plan and PR-sized implementations in Next.js.

339|58|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-feature-shipper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-feature-shipper
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/workflow-feature-shipper
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-feature-shipper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and engineers convert a feature idea into a concrete, executable plan, implement it in manageable PR-sized slices, and preserve artifacts for verification and audit, all within a Next.js codebase.

Core Features & Use Cases

  • Plan-first execution: transform a feature.md into a structured plan with acceptance criteria, boundaries, and risks.
  • PR-sized delivery: break work into small, independently runnable tasks with checkpoints and rollbacks.
  • Artifact-driven progress: store plans, evidence, and summaries under runs/ or OpenSpec changes as artifacts, enabling replay and review.

Quick Start

Define a feature in feature.md, specify the repo_root and run_dir, choose mode (plan-only or execute), and then run the skill to generate a plan, implement in PR-sized steps, and persist artifacts.

Frequently Asked Questions about workflow-feature-shipper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan and ship PR-sized features in a Next.js project?

To ship PR-sized features in a Next.js project, define your idea in a feature.md file, specify the repo_root and run_dir, and execute a plan-first workflow that generates incremental implementations and stores verifiable artifacts.

What is plan-first scoping for feature development?

Plan-first scoping transforms a feature idea into a structured plan with acceptance criteria, boundaries, and risks before implementation. It enforces disciplined PR-sized batch execution and artifact-based verification.

Does this automated feature shipping workflow require specific dependencies?

No specific external dependencies are required to use this workflow. It operates within a Next.js codebase, reading a feature.md file and creating evidence artifacts under an evidence/features directory.

Can I generate a feature implementation plan without writing any code?

Yes, you can use a plan-only mode to generate a structured plan with acceptance criteria and risks from your feature.md file without proceeding to the actual PR-sized code implementation phase.

How does artifact-driven progress work for feature delivery?

Artifact-driven progress stores plans, evidence, and summaries under runs/ or OpenSpec changes as artifacts. This enables teams to replay, review, and verify incremental PR-sized batches during product development.

What is the best way to break down a large feature into manageable PRs?

The best way to break down a large feature is to use a disciplined PR-sized batch rhythm, transforming the feature into small, independently runnable tasks with checkpoints, rollbacks, and design-system integration.