amend

Amends approved SDD pipeline artifacts in place and flags affected downstream stages for revalidation.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill amend-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amend
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/amend
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill amend-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changing an already-approved artifact in a spec-driven development pipeline normally forces you to restart the entire workflow, even when the change only affects one or two downstream stages. This Skill edits the artifact in place, logs the revision, and propagates revalidation flags only to the stages genuinely impacted. ## Core Features & Use Cases - In-place artifact editing: Modifies PRD, TRD, implementation code, code review, QA report, security review, or SRE review documents without recreating them from scratch. - Scoped downstream propagation: Uses the fixed pipeline order (PRD → TRD → implementation → code review → QA → security → SRE) to determine exactly which later stages require revalidation, leaving unaffected approvals intact. - Validation-debt resolution: Marks "VALIDAR DEPOIS" pending items as validated while preserving their history, and records every change in a revision log with date, author, and rationale. - Use Case: A stakeholder changes an acceptance criterion in an approved PRD. The Skill edits the PRD, logs the amendment, and flags only the TRD, implementation, and QA stages for revalidation instead of rerunning the whole pipeline. ## Quick Start Ask the assistant to amend the approved TRD for a specific feature slug to change a design decision and flag the affected downstream stages for revalidation.

Frequently Asked Questions about amend

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

FAQPage Schema
How do I change an approved PRD without restarting the whole pipeline?▼

Edit the PRD in place with the amendment, record the change in its revision log, then flag only the downstream stages actually affected for revalidation. Unaffected stages keep their existing approvals, so you rerun only the relevant commands.

How do I resolve a VALIDAR DEPOIS pending item in a spec document?▼

Edit the artifact to address the pending item, then mark it as validated rather than deleting it, preserving the history that the question existed. Log the resolution in the revision log with date and rationale.

Which pipeline stages need revalidation after a TRD change?▼

A TRD change can require revalidation of implementation, code review, QA, and security. SRE only needs revalidation if the change involves infrastructure. Earlier stages like the PRD remain approved.

Why does a revalidation flag never clear after I rerun the stage?▼

Status detection greps log lines for the revalidation phrase, so a closing entry that quotes the original flag text is read as a new unresolved occurrence. Describe the resolution without repeating the phrase and add a formal reapproval line with a later date.

When should I amend an artifact instead of rerunning the pipeline stage?▼

Amend when the change is a targeted correction to an approved artifact, such as a revised decision or a resolved pending item. Rerun the full stage only when the artifact must be regenerated from scratch.