How do I install the Feature Edit skill?

Run npx skillmds@latest add kdoronin/feature-edit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Feature Edit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Feature Edit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Feature Edit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Feature Edit?

kdoronin (@kdoronin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Feature Edit by kdoronin — Agent Skill

Name: Feature Edit
Author: kdoronin

Feature Edit

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 plugin -> feature-edit skill", "change feature X to", "the ACs need updating", "revise the plan", "scope changed".

kdoronin eb63aa5 3.0 KB Updated Sep 17, 2026

File contents

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

Resolve + identify the feature — resolve the methodology root + manifest via ${PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md); locate the feature (slug, branch, or search feature.md titles/outcomes).
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.
Classify the entry artifact — the highest-level artifact the intent directly changes: outcome/scope → feature.md; a behavior → acs.md; a GWT detail → spec.md; architecture/phasing → plan.md.
Build the edit plan — the cascade runs strictly downstream (feature.md → acs.md → spec.md → plan.md); upstream problems are surfaced, never auto-propagated. Per downstream artifact, classify by blast radius: small/mechanical → feature-edit edits directly; substantial → invoke the owning skill (discover-acs / atdd plugin atdd skill / plan) in edit-pass mode.
Present the plan; human confirms — show entry artifact, cascade, and how each step is handled. Nothing is written before confirmation.
Execute — in cascade order: direct edits and owning-skill invocations; regenerate .build/spec.json after any spec.md change; re-run affected test streams if code exists. If regeneration reveals an upstream problem, stop and surface it.
Sync — update progress.md (affected checkpoint rows) and the tracker via the driver.
Handoff — emit a summary.

Handoff

Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts lists every artifact edited. recommended_next: typically "re-run engineer plugin -> consistency-check skill".

References

Foundation Design — artifact schemas, the IR pipeline (Section 7)
Discuss & Upstream Funnel — when an "edit" is really a new feature

---name: feature-editdescription: 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 plugin -> feature-edit skill", "change feature X to", "the ACs need updating", "revise the plan", "scope changed".---# feature-editIntent-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 useAny 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`).## Workflow1. **Resolve + identify the feature** — resolve the methodology root + manifest via `${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.3. **Classify the entry artifact** — the highest-level artifact the intent directly changes: outcome/scope → `feature.md`; a behavior → `acs.md`; a GWT detail → `spec.md`; architecture/phasing → `plan.md`.4. **Build the edit plan** — the cascade runs **strictly downstream** (`feature.md → acs.md → spec.md → plan.md`); upstream problems are surfaced, never auto-propagated. Per downstream artifact, classify by blast radius: small/mechanical → feature-edit edits directly; substantial → invoke the owning skill (`discover-acs` / `atdd` plugin `atdd` skill / `plan`) in edit-pass mode.5. **Present the plan; human confirms** — show entry artifact, cascade, and how each step is handled. Nothing is written before confirmation.6. **Execute** — in cascade order: direct edits and owning-skill invocations; regenerate `.build/spec.json` after any `spec.md` change; re-run affected test streams if code exists. If regeneration reveals an upstream problem, stop and surface it.7. **Sync** — update `progress.md` (affected checkpoint rows) and the tracker via the driver.8. **Handoff** — emit a summary.## HandoffEmit per `${PLUGIN_ROOT}/references/handoff-summary.md`. `checkpoint: null`; `artifacts` lists every artifact edited. `recommended_next`: typically "re-run engineer plugin -> consistency-check skill".## References- [Foundation Design](https://www.notion.so/3585ecdee0e2811bbc67ff4913c03207) — artifact schemas, the IR pipeline (Section 7)- [Discuss & Upstream Funnel](https://www.notion.so/35a5ecdee0e281eaa35fced0c4e23384) — when an "edit" is really a new feature

Frequently asked questions