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
- NVIDIA/nvcftheir own version, first seen Nov 15, 2026
- SHREESHMAN/lineupifytheir own version, first seen Nov 15, 2026
- subhashkhileri/agntreetheir own version, first seen Oct 25, 2026
- WhatIfWeDigDeeper/claude-code-courseratheir own version, first seen Oct 20, 2026
- NumericalEarth/Breeze.jltheir own version, first seen Oct 17, 2026
- CliMA/Oceananigans.jltheir own version, first seen Oct 17, 2026
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- fullstackhero/dotnet-starter-kit★ 6.9ksame name
- JamieMason/syncpack★ 2.1ksame name
- CliMA/Oceananigans.jl★ 1.4ksame name
- OpusGameLabs/game-creator★ 360same name
- microsoft/SqlScriptDOM★ 284same name
- NVIDIA/nvcf★ 268same name
- NumericalEarth/Breeze.jl★ 90same name
- nikandr-surkov/ai-saas-starter★ 16same name
- Azure/azure-functions-agents-runtime★ 13same name
- aiqadam/qadam-flow★ 5same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- add-bugSkill
- fix-bugSkill
- list-bugsSkill
- review-my-codeSkill
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
- Very specific: line 56
Only Backlog is used by this skill.
- Very specific: line 77
Use the <TIMEZONE> timezone for timestamps
- Distinctive: line 78
Keep the short title under 60 characters
- Distinctive: line 79
If the user provides multiple features in one message, create a separate entry for each
“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.
Files
Add Feature Request
Log a feature request to docs/features.md with structured metadata for tracking and implementation.
Process
- 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.
- Read the current file — Read
docs/features.mdto understand the current content and find the right place to append. - 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"}
---- Assign the feature number — Look at existing entries in
docs/features.mdand increment from the highestFEAT-NNNnumber found. If no entries exist, start atFEAT-001. - 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
- Determine area — Infer from the description which part of the system is affected. Use
cross-cuttingif it spans multiple areas. If unclear, ask. - Append the entry — Add the new feature entry to the end of
docs/features.md. - Confirm — Tell the user the feature has been logged with its ID, e.g. "Logged as FEAT-003 (Medium,
<area-1>)". - 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:
| Status | Meaning |
| Backlog | Logged, not yet planned |
| Planned | Accepted and scheduled for implementation |
| In Progress | Actively being built |
| Done | Implemented and verified |
| Won't Do | Declined 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-cuttingis 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
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
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.

