Add feature

Skill kunalsuri/ai-fication-kit/templates/claude/skills/add-feature

AI-Fication Kit: A Simple & Elegant Way for Making any Codebase AI-native through Scaffolded, Human-verified Context and Development Loop.

Install

npx -y skills add kunalsuri/ai-fication-kit --skill add-feature

Assembled 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

Add a feature to this repository the safe way — spec, locate via maps, respect Stability, surgical implementation, verification, knowledge update. Use whenever the user asks to add, build, or implement functionality.

SKILL.md

1.9 KB, as published. Nobody here has run it

Add a feature

The contract: no code before a spec, no edits to frozen code, no "done" without green tests, no merge without a review and a knowledge update.

1. Spec

If ai/lab/specs/SPEC_<name>.md doesn't exist, draft it from SPEC_TEMPLATE.md (goal, scope, touch list, acceptance criteria, verification). Get the user's OK.

2. Locate

ai/guide/MODULE_MAP.md → which modules; note Stability of every target.
ai/analysis/FEATURE_CATALOG.md → the "where new code lives" decision tree and the 3-file rule for related features.
ai/lab/WORKLOG.md → recent history: was this area just changed? is the behavior deliberate?
Delegate broad reading to repo-explorer.

3. Gate

Any file in the touch list with Stability frozen or ? ⇒ stop and ask the human. Record their approval in the spec before proceeding.

4. Implement

Delegate to feature-builder with the exact touch list. Conventions per ai/guide/CONVENTIONS.md — see also reference/checklist.md.

5. Verify

Delegate to test-runner: narrowest suite first, then the suites the spec names. Red or unrun ⇒ not done.

6. Update knowledge

FEATURE_MAP entry; catalog amendment; MODULE_MAP if layout changed; all [inferred]. Tell the user which tags await their [verified] flip.

7. Review & record

Request /review-change on the diff (fresh context — not this session). Append the work's row to ai/lab/WORKLOG.md linking spec, review, and commits, and move the feature's ai/lab/ROADMAP.md row from Planned to Shipped (cross-link spec, WORKLOG row, and PR by feature ID).