agentleFS
kunalsurikunalsuri/ai-fication-kit/.agents/skills/add-feature/SKILL.md

add-feature

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

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.

27 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 13
  2. Distinctive:

    Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.

    line 22
  3. Distinctive:

    Run the narrowest suite that covers the change first, then the suite(s) the spec names.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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?
  • 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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.