# Deliver Nextjs Feature

> Implements a named Next.js App Router feature when explicitly requested within approved routes and files; follows installed-version docs and repository gates without adding unrequested infrastructure.

- Skill: `jovanipink/deliver-nextjs-feature` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add jovanipink/deliver-nextjs-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/deliver-nextjs-feature/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/deliver-nextjs-feature

---


# Next.js Feature Delivery

Read [version-matched delivery](references/delivery.md) only when its checks apply to the task. Project-local copies include a project contract; compare it with current repository settings before relying on it.

## Workflow

1. Establish the user-visible behavior, route boundary, accepted inputs, evidence requirements, repository instructions, and existing edits.
2. Resolve the installed Next.js package and its bundled documentation from the project directory. Preserve managed AGENTS documentation routing, supported Node lanes, lockfile, and compiler contracts.
3. Derive a deduplicated path allowlist from task authority and current changes. Preserve unrelated edits; exclude generated routes/build output/vendor directories. Return Not Needed for empty authorized scope.
4. Implement the smallest slice with server components by default and explicit interactive client boundaries. Reuse existing product capabilities; do not scaffold auth, persistence, analytics, or providers absent a concrete requirement.
5. Test observable behavior, accessibility, error/empty states, and server/client data flow. Run existing type, lint, test, build, and dependency gates, then inspect the final allowlisted diff.

## Done when

The slice is complete only when the requested behavior and acceptance criteria are satisfied within the allowlist, required checks pass, and the final allowlisted diff has been inspected. Blocked and partial work remain unfinished. Unavailable required validation must be reported with its limitation and the next authorized check; it cannot establish completion. Not Needed requires evidence that no applicable authorized change exists. Stop and ask only when the slice needs a path outside the allowlist, an unsupported API, an action listed under Boundaries, or a product decision the repository cannot answer.

## Boundaries

Do not run broad mutating formatters, framework upgrades, codemods, deployments, package installation, or provider mutations as an incidental step. Unsupported APIs require a compatibility decision.

## Evidence and output

Lead with the result and anything that needs the user's decision. Then report the authorized scope, applicable settings, observed evidence, missing evidence, and next bounded check. Use Not Needed when no applicable authorized work exists and Blocked when a required precondition is missing. Do not substitute required headings for semantic compliance or invent executed checks.

## Example

Synthetic example; not an observed client result.

Input: Add a filter to one approved App Router page; the project has a pinned Next.js version.

Output: Inspect installed route and data APIs, implement the filter within the approved page, and run its repository gates. No infrastructure change follows from this request.

