Workflow: Ship Faster (Next.js 16.1.1)

The goal of this chain is: Ship an idea or small prototype to production-ready state in the shortest time, while maintaining iteration speed afterward.

When to use

Use this workflow when the user wants an end-to-end chain like:

• “ship this MVP”, “make it production-ready”, “launch/deploy this project”
• “take this prototype and turn it into a real app”
• “set up the foundation + UI system + deployment”

Core principles (non-negotiable)

• Pass paths only, not content: agents/sub-agents only pass ..._path.
• Files are first-class citizens: Every step must persist artifacts; failures can be retried; replayable.
• Confirmation points: Any "high-risk/high-effort/side-effect" action must write a plan first and wait for confirmation.
• Plans are checklists: progress is tracked in tasks.md via - [ ] → - [x] (not in chat).
• Progressive disclosure: Only open step files in this skill directory (foundation.md, deploy-vercel.md, etc.) when needed—avoid loading all details at once.
• Hooks doctor (required check; non-blocking): If running under Claude Code and you want the evolution loop active, run tool-hooks-doctor once at the start of the session; if hooks are missing, offer to install project-level hooks (continue either way).