How do I install the Add Feature skill?

Run npx skillmds@latest add kunalsuri/add-feature in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Add Feature safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add Feature?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Add Feature free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Add Feature?

kunalsuri (@kunalsuri) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Add Feature by kunalsuri — Agent Skill

Name: Add Feature
Author: kunalsuri

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.

kunalsuri f05dd25 2 files · 2.7 KB Updated Sep 17, 2026

File contents

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?
Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.

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

Make the smallest diff that satisfies the spec. Conventions per ai/guide/CONVENTIONS.md — see also reference/checklist.md. Match the license headers of neighboring files. No drive-by refactors, no layout changes, no dependency additions unless the plan says so.

5. Verify

Run the narrowest suite that covers the change first, then the suite(s) the spec names. Report command run · exit status · failures verbatim. 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).

---name: add-featuredescription: 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.---# Add a featureThe contract: **no code before a spec, no edits to frozen code, no "done" withoutgreen tests, no merge without a review and a knowledge update.**## 1. SpecIf `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?- Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.## 3. GateAny file in the touch list with Stability `frozen` or `?` ⇒ stop and ask the human.Record their approval in the spec before proceeding.## 4. ImplementMake the smallest diff that satisfies the spec. Conventions per`ai/guide/CONVENTIONS.md` — see also `reference/checklist.md`. Match the licenseheaders of neighboring files. No drive-by refactors, no layout changes, nodependency additions unless the plan says so.## 5. VerifyRun the narrowest suite that covers the change first, then the suite(s) the specnames. Report command run · exit status · failures verbatim. Red or unrun ⇒ not done.## 6. Update knowledgeFEATURE_MAP entry; catalog amendment; MODULE_MAP if layout changed; all `[inferred]`.Tell the user which tags await their `[verified]` flip.## 7. Review & recordRequest `/review-change` on the diff (fresh context — not this session). Appendthe work's row to `ai/lab/WORKLOG.md` linking spec, review, and commits, and move thefeature's `ai/lab/ROADMAP.md` row from Planned to Shipped (cross-link spec, WORKLOGrow, and PR by feature ID).

Frequently asked questions