nextjs-ai-template

Wrap up a work session by validating the repo, grouping the diff into logical change sets, stashing each group, then fanning out parallel subagents that create branches, commits, PRs, and monitor CI — following the repo's GitHub Flow strategy. Use when the user wants to close shop, end a shift, wrap up today's work, or batch a day's coding into PRs.

Assign Complexity ratings (1-5) to issues in a directory and recommend decomposition for Complexity 5 issues. Use when user wants to rate issue complexity, assess backlog difficulty, prioritize issues by effort, or decompose complex issues into smaller slices.

Discover and implement 1-3 ready-for-agent issues using the Features CLI. Use when user says "do an issue", "pick up next issue", "implement issues", "what's next", "work on backlog", "execute issues", or asks to implement ready-for-agent issues from .scratch/.

Add or tighten GitHub Flow restrictions for a GitHub repository using gh CLI in a solo developer setup. Use when asked to enforce pull-request-only main branch protection, required status checks, force-push blocking, or other branch safety rules without requiring a second reviewer.

Verify whether a GitHub repository is correctly configured for GitHub Flow, especially for a solo developer setup. Use when asked to audit branch protection, required checks, pull request rules, rulesets, or whether main is safely protected without blocking a single maintainer workflow.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Compact the current conversation into a handoff document for another agent to pick up.

Read a milestone from ROADMAP.md, audit the codebase, decompose into feature briefs, and register them. Use when user says 'decompose milestone', 'create briefs', 'break down M1', or wants to start the pipeline from a roadmap milestone.

Automated feature-scoped review that verifies acceptance criteria, runs scoped QA, detects orphans, and produces a review report. Use after all issues in a feature are implemented, before human sign-off, or when user says "review feature", "review this feature", "run feature review", or mentions feature sign-off.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Break a PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Synthesize a grilling session into a PRD (HLD document) with a feature registry that maps to existing features in features-status.json. Use when user wants to create a PRD, turn a grilling session into a plan, or says "to-prd", "create PRD", "write PRD", "turn this into a PRD".

Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.

Verify that the git-flow-check and git-flow-add-restriction skills are installed correctly and that a repository is ready for solo-maintainer GitHub Flow. Use when asked to validate skill installation, script executability, gh authentication, branch protection visibility, required checks readiness, or end-to-end GitHub Flow setup.