agentleFS
Crypto69Crypto69/claude-skills/add-feature/SKILL.md

add-feature

Skill0 starsChanged 5 months agoMITView on GitHub

Add a feature request to docs/features.md with description, priority, and implementation status. Use when the user wants to log a feature idea or enhancement.

28 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

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Only Backlog is used by this skill.

    line 56
  2. Very specific:

    Use the <TIMEZONE> timezone for timestamps

    line 77
  3. Distinctive:

    Keep the short title under 60 characters

    line 78
  4. Distinctive:

    If the user provides multiple features in one message, create a separate entry for each

    line 79

“Common” is measured: kept by at least 6 in 10 of the 26 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

Add Feature Request

Log a feature request to docs/features.md with structured metadata for tracking and implementation.

Process

  1. Get feature details — The user will describe the feature either as arguments to the command or in their message. If no description is provided, ask for one using AskUserQuestion.
  2. Read the current file — Read docs/features.md to understand the current content and find the right place to append.
  3. Generate the entry — Create a new feature entry using this format:
### FEAT-{NNN}: {Short title}

| Field | Value |
|-------|-------|
| **Status** | Backlog |
| **Added** | {YYYY-MM-DD HH:MM <TIMEZONE>} |
| **Priority** | {High / Medium / Low / Nice-to-have} |
| **Area** | {<area-1> / <area-2> / <area-3> / cross-cutting} |

**Description:**
{Detailed description of the feature}

**Notes:**
{Any implementation notes, constraints, or related context — otherwise "None"}

---
  1. Assign the feature number — Look at existing entries in docs/features.md and increment from the highest FEAT-NNN number found. If no entries exist, start at FEAT-001.
  2. Determine priority — If the user doesn't specify priority, infer from the description:
    • High: Revenue-impacting, user-blocking, or frequently requested
    • Medium: Meaningful UX improvement or operational efficiency gain
    • Low: Minor enhancement, polish, or edge-case improvement
    • Nice-to-have: Exploratory idea, no urgency
  3. Determine area — Infer from the description which part of the system is affected. Use cross-cutting if it spans multiple areas. If unclear, ask.
  4. Append the entry — Add the new feature entry to the end of docs/features.md.
  5. Confirm — Tell the user the feature has been logged with its ID, e.g. "Logged as FEAT-003 (Medium, <area-1>)".
  6. Do NOT implement — After logging the feature, do NOT start implementing it. Ask the user if they would like you to implement it now. Only proceed with implementation if the user explicitly confirms.

Status lifecycle

Only Backlog is used by this skill. Other statuses are for reference when features are triaged or implemented later:

StatusMeaning
BacklogLogged, not yet planned
PlannedAccepted and scheduled for implementation
In ProgressActively being built
DoneImplemented and verified
Won't DoDeclined or out of scope

Configuration

Replace these placeholders with your project's values before using the skill:

  • <area-1> / <area-2> / <area-3> — the modules / sub-projects in your repo used to tag features (e.g. frontend / backend / api / mobile / infra). cross-cutting is generic — keep it for features that span areas. Edit the Area field in the template.
  • <TIMEZONE> — the timezone for timestamps (e.g. UTC, America/New_York, Europe/London). Edit the Added field.

See the repository README for the full placeholder reference shared across skills.

Notes

  • Use the <TIMEZONE> timezone for timestamps
  • Keep the short title under 60 characters
  • If the user provides multiple features in one message, create a separate entry for each

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.