features-update
Skill2 starsChanged 31 days agoMITView on GitHub
Maintainer only (needs pmctl with the maintainer's tracker DB). After implementing, changing or removing a user-visible feature in pm, spawn the features-keeper sub-agent to add or update its entry in FEATURES.md. Use when you finish a feature or behaviour change, before the final report, or when the maintainer says "update FEATURES.md" / "document this feature". Contributors describe the change in the PR instead.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- arch-guardSkill
- builder-previewSkill
- features-auditSkill
- screen-validatorSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Run for any new, changed or removed user-visible behaviour: a page, route, button, setting, slash command, notification, keyboard/touch …
- Very specific: line 29
After the code is done and tests pass, launch one sub-agent: Agent(subagent_type="features-keeper", prompt=...).
- Distinctive: line 34
Read its report. If it flags something it could not verify, answer or fix the code.
- Very specific: line 38
If FEATURES.md does not exist yet, the sub-agent creates it by running the audit skill (.claude/skills/features-audit/SKILL.md) instead.
- Very specific: line 68
Every route/setting/file named in the entry exists (Grep).
- Distinctive: line 69
No duplicate entry for the same feature.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update FEATURES.md after a feature
Maintainer only: needs pmctl with the maintainer's tracker DB (project polymux). Contributors: describe
the change in the PR instead; the maintainer adds the FEATURES and CHANGELOG entries. Without pmctl
(command -v pmctl fails), skip this skill and say so in the PR text.
FEATURES.md (repo root) is the catalogue of what pm can do now. CHANGELOG.md says what changed
and when; FEATURES.md says what exists. Both are updated for a user-visible change. Both files are generated
from the tracker DB: entries change only through pmctl feature set/rm and pmctl change add, never by
editing the file.
When to run
Run for any new, changed or removed user-visible behaviour: a page, route, button, setting, slash command, notification, keyboard/touch gesture, MCP/agent action, in either theme. Skip for refactors, tests, docs-only, and pure bug fixes that restore documented behaviour.
How (main agent)
- After the code is done and tests pass, launch one sub-agent:
Agent(subagent_type="features-keeper", prompt=...). The prompt holds: the feature in one or two sentences, the theme (classic or dt), the files/routes/templates/settings it touched (git diff --statoutput is fine), and whether it is new, changed or removed. Do not paste its desired wording; let it read the code. - Read its report. If it flags something it could not verify, answer or fix the code.
- Include
FEATURES.mdin the same commit as the feature (the pre-commit hook re-renders and stages it). Mention it in the final report.
If FEATURES.md does not exist yet, the sub-agent creates it by running the audit skill
(.claude/skills/features-audit/SKILL.md) instead.
Commands (the sub-agent uses these)
pmctl feature list [--area Chat],pmctl feature show "<Area>" "<Name>": what is there now.pmctl feature set "<Area>" "<Name>" --text "<text>"(or--text-file -): add or replace one entry; a new name goes at the end of its area, a new area at the end of the file.<text>is the line after- **<Name>** —.pmctl feature rm "<Area>" "<Name>": delete an entry. TheSummary:line is recomputed after a change.
Entry format (the sub-agent follows this)
FEATURES.md is grouped by area (Navigation, Inbox, Agents, Chat, Projects, Git, tmux, Servers / VMs, Settings,
Notifications, Security, Phones / Builder, Background, Tools, dt theme). Everything that only the dt theme does
goes in dt theme (docs/themes/dt/CONDUCT.md V7-GATE-6); a core feature both themes show stays in its
usual area. Within an area, one bullet per feature:
- **Name** — one sentence on what the user can do. Where: `/route` or UI spot. Code: `src/pm/x.py`, `templates/y.html`, `static/js/z.js`. Since: 2026-10-11.Rules: present tense, user's words not internal names; one line per feature (a short sub-list only for
distinct modes); keep Where concrete (route, button label, setting key; dt: also ?ui=dt); update Since
only for new features, add Changed: <date> for behaviour changes; delete the bullet when the feature is removed
(the changelog keeps the history); keep areas alphabetical-by-feature unless the file says otherwise.
Top of file: a Last audited: <date> line, which only the audit skill changes (pmctl feature audited).
Checks before finishing (sub-agent)
- Every route/setting/file named in the entry exists (
Grep). - No duplicate entry for the same feature; merge instead.
- Hard-rule features (CSRF, audit, masking, no native popups) are stated as guarantees, not duplicated per page.
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.

