keefhub

You can turn prose requests into Gherkin feature files, produce gated BA/SA specifications with BDD acceptance criteria, write numbered implementation plans, execute plans via reviewed subagents, harden existing specs through adversarial review, verify and commit code safely, and ship non-templated frontend designs.

They target software engineers and technical leads practicing spec-driven development, particularly in Next.js App Router repositories where data, domain, component, and route work must be separated into distinct planned tasks with verification gates.

feature-discovery splits raw requests into features, feature-spec produces a gated specification, writing-plans saves a task-by-task plan.md, sdd executes it via reviewed subagents with resumable state, and git-commit runs lint, typecheck, build, and Playwright before committing and pushing.

It fails closed: nothing commits on lint, typecheck, build, or Playwright failure, with errors logged to output/error/{feature}.md. It never pushes to master/main directly, runs an unconditional final build before every push, and routes protected-branch work through a feature branch.

Skills expect a repository structured around features/NNN.*.md specs and doc/features/ documentation, a plan.md for execution, and a project supporting lint, typecheck, build, and Playwright specs. The writing-plans skill assumes a Next.js App Router codebase layout.