skills.rest
swingerman
swingermanCOMMUNITY
Explore all skills by this author →
Website𝕏@miklosszanyiGitHub

feature-edit

Update existing feature artifacts and cascade changes downstream after confirmation.

134|9|Updated Feb 16, 2026
Search Tags:#Claude Code#acceptance criteria#mutation testing#ATDD#deterministic guardrails#feature editing#spec cascade
One-click install
npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill feature-edit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-edit
Source: https://github.com/swingerman/disciplined-agentic-engineering/tree/main/engineer/skills/feature-edit
Command: npx skills add https://github.com/swingerman/disciplined-agentic-engineering --skill feature-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill coordinates a disciplined, intent-driven update when an existing feature’s scope, acceptance criteria, or architecture needs to change, preventing inconsistent edits and uncontrolled ripple effects.

Core Features & Use Cases

  • Intent-driven edit orchestration: determines which methodology artifacts must change (outcome/scope, behaviors, GWT/spec details, and plans) based on the human’s corrected intent.
  • Strict downstream cascade: propagates changes only downstream (feature.md → acs.md → spec.md → plan.md) while surfacing upstream issues instead of auto-propagating them.
  • Human-confirmed mixed mode: generates a concrete edit plan first and performs writes only after explicit confirmation.
  • Regeneration and verification hooks: regenerates build/spec.json after spec changes and re-runs affected test streams when code exists, stopping to surface upstream problems if regeneration uncovers them.

Quick Start

Use feature-edit when you need to update an existing feature so it matches refined acceptance criteria by sending the updated intent for the change and confirming the proposed edit plan before any files are written.

Frequently Asked Questions about feature-edit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update acceptance criteria for an ongoing feature without breaking the spec cascade?▼

To update acceptance criteria safely, this Skill orchestrates a strict downstream cascade from feature.md to acs.md, spec.md, and plan.md, applying deterministic guardrails to prevent inconsistent ripple effects across your methodology artifacts.

What is the best way to propagate scope changes downstream during feature editing?▼

Propagating scope changes safely requires a strict downstream cascade that updates dependent files sequentially while surfacing upstream issues for human review rather than auto-propagating them blindly.

How does mixed mode human confirmation work when modifying feature specs?▼

Mixed mode confirmation generates a concrete edit plan based on your refined intent and waits for explicit approval before performing any file writes, ensuring you review changes before they are applied.

Do I need to regenerate build/spec.json manually after spec changes?▼

No, you do not need to regenerate build/spec.json manually; the feature editing process automatically regenerates it after spec changes and re-runs affected verification streams if code exists.

Can ATDD verification streams detect upstream problems when acceptance criteria are refined?▼

Yes, when acceptance criteria are refined, the process re-runs affected ATDD verification streams and stops to surface upstream problems if regeneration uncovers them, preventing silent failures.

When should I not use an automated feature edit orchestration tool?▼

You should avoid automated feature edit orchestration when upstream issues are detected, as the tool intentionally stops and surfaces these problems rather than auto-propagating changes that cause inconsistent edits.

Related Skills

Explore More Software Engineering Skills→
jshsakurajshsakura
22

qa-expert

Define risk-based test scope and acceptance criteria for software releases.

Community
Advanced
swingermanswingerman
134

atdd-mutate

Run mutation testing on ATDD two-stream test suites to measure kill and survive scores.

Community
Advanced
prestariusprestarius
1

power-phrase

Coordinate six build-session phases using native Claude Code skills.

Community
Advanced
swingermanswingerman
134

plan

Draft a human-confirmed architecture plan with spec-driven DAE checkpoints.

Community
Advanced