fit-audit

Audits whether a project requires new rules, stack packs, skills, or personas in the kit.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill fit-audit-vinodkrishna221
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fit-audit
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/fit-audit
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill fit-audit-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about fit-audit

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

FAQPage Schema
How do I audit whether a project needs new rules or skills?▼

Run the fit-audit after the stack record at /blueprint. It inventories every capability from the PRD and architecture, maps coverage against existing kit assets, and applies a necessity gate before drafting anything new.

What is the necessity gate for adding new stack packs?▼

The gate scores three questions: will agents touch this across at least 3 task cards, is getting it wrong demo-fatal, and is the team unfamiliar with it. Fewer than two yes answers means no new asset is created.

When should a new persona be created for a project?▼

A new persona requires a whole track of work, at least 8 cards, in that domain. Otherwise the nearest existing persona takes the cards backed by a stack pack, keeping persona creation rare.

Can the fit-audit edit kit files without approval?▼

No. The diff ritual requires presenting all proposed additions and edits with justifications to the human first. Only after approval does it write files, sync, commit, and log a DECISIONS entry.

What happens if the audit finds nothing is needed?▼

It reports a clean bill of health in one line and moves on. This is the most common correct outcome and costs zero files, since fabricating unnecessary packs is treated as bloat.