swingerman/feature-edit
engineer/skills/feature-edit/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add swingerman/atdd feature-editInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 5:03 AM102.2s1 file scanned
SKILL.md
- name:
- feature-edit
- description:
- 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".
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
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md); locate the feature (slug, branch, or searchfeature.mdtitles/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:atdd/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.jsonafter anyspec.mdchange; 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 ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; artifacts lists every artifact edited. recommended_next: typically "re-run /engineer.consistency-check".
References
- Foundation Design — artifact schemas, the IR pipeline (Section 7)
- Discuss & Upstream Funnel — when an "edit" is really a new feature
Related Skills
swingerman/post-merge
data-ai
VerifiedTrustedCommunity
Use immediately after a PR is merged to clean up the local feature branch and resync main. Triggers — "/engineer.post-merge", "did we merge", "did we push", "PR merged", "post-merge cleanup", or right after a `gh pr merge` succeeds in the same session.
103SKILL.mdUpdated Jun 5, 2026
swingerman/fix
data-ai
VerifiedTrustedCommunity
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".
103SKILL.mdUpdated May 26, 2026
swingerman/reorient
testing
VerifiedTrustedCommunity
Use mid-task when the working thread is lost — after a context compaction, a long agent run, or coming back to a feature unsure of the role, the current checkpoint, or the next action. Triggers — "/engineer.reorient", "reorient", "re-anchor", "what should I be doing right now", "I lost track", "where was I".
103SKILL.mdUpdated May 20, 2026
swingerman/arch-check
development
VerifiedTrustedCommunity
Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden patterns, file naming, file size. Triggers — "/engineer.arch-check", "architecture check", "check architecture fitness", "does this follow the charter", "check layering".
103SKILL.mdUpdated May 19, 2026