What problem does it solve? Teams risk building projects on generic rules that miss unfamiliar frameworks, protocols, or domains, while the opposite failure — fabricating unnecessary assets — creates bloat. This Skill provides a strict, gated audit that decides both directions before work begins. ## Core Features & Use Cases - Capability Inventory & Coverage Map: Lists every capability from the PRD and architecture stack record, then maps each against existing kit assets as COVERED, PARTIAL, or MISSING with evidence. - Necessity Gate: Scores each gap on three questions (≥3 task cards, demo-fatal risk, team unfamiliarity) and rejects anything scoring under two yes votes, logging declined assets to prevent relitigation. - Diff Ritual: Presents all proposed file additions and edits with justifications for human approval before writing, then commits and re-engages the freeze on kit self-modification. - Use Case: After the stack record is written at /blueprint, run the audit to determine whether a project using an unfamiliar protocol like WebRTC needs a new stack pack, or whether existing rules suffice. ## Quick Start Run the fit-audit skill after the stack record to check whether this project needs any new rules, stack packs, skills, or personas.