FeatureKit documentation

FeatureKit is a set of plain-Markdown skills that gives your coding agent a disciplined way of working: agree a written plan before production code, build in small vertical slices, prove each acceptance criterion with evidence, and size review and model effort to the risk. It runs inside the agent you already use, with no CLI, server or runtime of its own.

Most of these pages are generated from the FeatureKit repository on every release, so they describe the version you install. Each page says where it came from.

01 · Get startedTry it in a repoWhat FeatureKit is, install, one-time setup, and your first feature from idea to approved slice.02 · GuidesWork this way every dayThe main flow, slices, review, context hygiene, orchestration, security and troubleshooting.03 · Reference & internalsUnderstand the engineeringEvery skill, the rules FeatureKit is built by, how it is evaluated, and the full changelog.

Start here

1. Install the skills into your product repo with the open skills CLI.
2. Run /setup-featurekit once. Setup records your repo’s conventions and saves the session bootstrap.
3. Follow Your first feature to take one real idea to an implemented, reviewed slice.

Prefer to read a complete run first? The end-to-end example follows one feature through every step.

Requirements

• A coding agent that can load skills or repo instructions: Claude Code, Codex or OpenCode. Other agents and local LLMs work through a compiled prompt.
• Node.js, to run npx skills@latest.
• A product repository with the checks you already run, such as tests, lint and build. FeatureKit uses them as evidence; it does not choose your stack.