next-increment

Generate 3-5 architecture-grounded candidate increments and a mini-spec for mature codebases.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill next-increment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: next-increment
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/next-increment
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill next-increment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mature codebases with written architecture direction often stall on what to build next; this Skill turns architecture docs and repository state into a short, actionable set of candidate increments and a concrete mini-spec for the chosen one so teams can move forward safely and quickly.

Core Features & Use Cases

  • Architecture-aware candidates: Reads docs/02-architecture and repository state to produce 3-5 candidate increments grounded in existing design.
  • Archetype diversity and concrete verification: Ensures candidates span infrastructure-seed, user-visible, and risk-reducer archetypes with specific verify steps (curl/SQL/CLI/UI).
  • Mini-spec authoring and history persistence: Writes a pending mini-spec to docs/06-plans and appends a normalized entry to .claude/increment-history.yml to maintain flow.
  • Use case: A maintainer of a mature service asks what to build next and receives a short, verifiable increment plus a spec file and history entry ready for planning or execution.

Quick Start

Ask the assistant to run next-increment on a repository that contains docs/02-architecture to produce 3-5 candidates and write a mini-spec saved to docs/06-plans.

Frequently Asked Questions about next-increment

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

FAQPage Schema
How do I decide what to build next in a mature software codebase?

To decide what to build next, analyze your architecture docs and repository state to generate 3-5 archetype-diverse candidate increments, then select and spec the best one for verifiable implementation.

What is a verifiable increment in software development?

A verifiable increment is a small codebase update accompanied by concrete verification steps like curl, SQL, CLI, or UI tests, ensuring the new functionality works safely and quickly.

How do I create a mini-spec for a planned software feature?

Generate a mini-spec by selecting a candidate increment, anchoring it to existing architecture documentation, performing dependency checks, and writing the pending spec to a designated plans directory.

Does generating the next software increment require architecture docs?

Yes, this process requires a repository with established architecture docs to ground candidate increments in the existing design and maintain architectural alignment.

How are candidate software increments diversified during planning?

Candidate increments are diversified by spanning infrastructure-seed, user-visible, and risk-reducer archetypes, ensuring balanced development across infrastructure, features, and technical debt.

How do I persist a software increment plan and maintain development flow?

Persist an increment plan by writing the mini-spec to a plans directory and appending a normalized entry to an increment-history file, maintaining continuous development flow.