agentsclimarketplace

Add feature

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

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.From its SKILL.md

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.

2 things 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.
  • runs commandsInstructs the agent to run 1 command, including `/review-change`.

SKILL.md

1.9 KB, 439 tokens by cl100k_base, as published. Nobody here has run it

<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

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).

What ships with it: 1 file

603 B alongside SKILL.md

reference/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.