Perform feature add simulation
Skill kunalsuri/ai-fication-kit/.claude/skills/perform-feature-add-simulation
AI-Fication Kit: A Simple & Elegant Way for Making any Codebase AI-native through Scaffolded, Human-verified Context and Development Loop.
npx -y skills add kunalsuri/ai-fication-kit --skill perform-feature-add-simulationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Dry-run the add-feature workflow for a proposed feature — friction report and per-phase readiness score, without writing code.
SKILL.md
1.3 KB, as published. Nobody here has run it
Simulate adding the feature the user names — WITHOUT writing a single line of code. This is a pre-flight check of both the plan and the knowledge layer.
Phases to walk (score each: smooth / friction / blocked)
- Locate — can MODULE_MAP + FEATURE_MAP/CATALOG identify the target modules without crawling? Name them.
- Plan — draft the touch list per layer; note Stability of every file you'd
change. Any
frozenor?file ⇒ blocked pending human approval. - Verify — which suites would prove it works; do they exist and are commands confirmed?
- Knowledge update — which ai/ files would need updating after the change?
Output
A friction report in chat (and, if asked, saved to ai/analysis/audit-reports/): per-phase score with the specific missing knowledge that caused friction, total estimated context cost, and a go / no-go recommendation. Knowledge gaps found here are the cheapest bugs you will ever fix — file each as an audit TODO.