feature-edit SKILL.md skillA
feature-edit from swingerman/engineer is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add swingerman/engineer/feature-edit@git:20261020.d56de69Pins git:20261020.d56de69 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- swingerman/engineer
- Path
engineer/skills/feature-edit/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261020.d56de69, committed Oct 20, 2026
- First version recorded
- May 15, 2026
- Size
- 3,201 bytes
- Repository stars
- 162
- License
- MIT
Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or removed. Triggers — "/engineer.feature-edit", "change feature X to", "the ACs need updating", "revise the plan", "scope changed".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# feature-edit
Intent-driven editing of an in-flight feature. The human describes *what should now be true*; this skill figures out *which files and tools to touch* and orchestrates the change, including the downstream cascade.
The cascade-owning skill — `clarify` and `refine` deliberately stay single-artifact and route multi-artifact propagation here. Mixed mode: the agent proposes an edit plan, the human confirms before any write.
## When to use
Any time an existing feature's artifacts must change. `checkpoint: null`.
**Not for:** a brand-new capability (`discuss`); within-one-artifact ambiguity, no behavior change (`clarify`); validating consistency (`consistency-check`); cleaning up code (`refine`).
## Workflow
1. **Resolve + identify the feature** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py` (see `references/resolving.md`); locate the feature (slug, branch, or search `feature.md` titles/outcomes).
2. **Is this actually an edit?** — if the intent is a new capability or too big for one feature, surface it and redirect to `discuss`. Stop.
…Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/feature-edit@sha256:a3b6be6c5e2f1b48The line at the top of this page pins the label git:20261020.d56de69, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_s2kg43kntifxlszt)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 15, 2026 and Oct 20, 2026, about one every 39 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.d56de69 latest | 2026-10-20 | d56de69 | 3,201 B | A | view · diff |
| git:20260518.62751f4 | 2026-05-18 | 62751f4 | 3,007 B | A | view · diff |
| git:20260516.48406db | 2026-05-16 | 48406db | 3,011 B | A | view · diff |
| git:20260515.595977f | 2026-05-15 | 595977f | 2,918 B | A | view · diff |
| git:20260515.7a2f96e | 2026-05-15 | 7a2f96e | 8,946 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3201 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
swingerman/engineer · 162 stars · license MIT · pushed 2026-10-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_s2kg43kntifxlszt GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/feature-edit GET https://markdownregistry.com/api/v1/blob/a3b6be6c5e2f1b48022ce86701a862934705bd9bcc61285a4b7090e859e69b31
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.