onboard vs make-it-work

End-to-end Claude tooling generator for existing codebases. Performs deep codebase analysis (languages, frameworks, conventions, complexity), walks you through an interactive wizard, then generates a complete suite of Claude artifacts — CLAUDE.md files, path-scoped rules, project-specific skills and agents, hook configuration, PR templates, and commit conventions. Unlike recommendation-only tools, onboard produces actual files tailored to your project's detected patterns and enforced configs. Includes drift detection via /onboard:evolve to keep tooling aligned as your codebase changes. Also serves as the generation engine for the companion forge plugin (new projects) via headless invocation.

Skills that make Claude actually work in your project. Not just generally, but specifically, the way your codebase is built. Built for engineering teams working on large, complex codebases. Not greenfield side projects. When your codebase has history, domain rules, and legacy decisions baked in, "generally smart" isn't enough. Claude needs to know your project. go-deep maps your codebase from the inside out and builds a layered documentation system so every Claude session starts grounded in your project's real structure, rules, and use cases. Not generic assumptions. close-the-gaps acts as a Product Analyst before development begins: it finds every gap in a ticket (unclear language, missing edge cases, conflicting requirements), walks you through them one by one, and outputs a Gherkin-ready refined spec. The cost of a vague ticket is paid in rework. close-the-gaps makes sure requirements are solid before a single line of code is written.