From agile-lifecycle
This skill should be used when evaluating if a change is incremental or significant, when processing a change request, or when updating the change log. Triggers when scope, requirements, or architecture changes are proposed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agile-lifecycle:change-controlThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Change control ensures that scope changes, requirement changes, and architecture changes are assessed, classified, and approved before being implemented. The classification determines whether a change can be absorbed incrementally or requires a formal change request with impact assessment and re-gating. Unmanaged changes accumulate as technical debt, scope creep, or unacknowledged risk.
Change control ensures that scope changes, requirement changes, and architecture changes are assessed, classified, and approved before being implemented. The classification determines whether a change can be absorbed incrementally or requires a formal change request with impact assessment and re-gating. Unmanaged changes accumulate as technical debt, scope creep, or unacknowledged risk.
Document the proposed change using the significant change record template: templates/transversal/significant-change-record.md.template. At a minimum, record:
Apply the classification criteria from references/change-criteria.md:
If uncertain, default to "significant" — it is better to over-classify and scope down than to miss the impact of a change.
For significant changes, assess impact across six dimensions:
Rate each dimension: None / Low / Medium / High.
Based on the impact assessment:
Re-gate means: the affected phase returns to in_progress status, the changed artefacts are updated, and the gate review is re-run with the updated evidence.
After approval:
in_progress, make the changes, re-assemble evidence, trigger gate reviewschemas/change-log.schema.json)After implementing the change:
references/change-criteria.md — Classification criteria, significant vs incremental thresholds, change request process, impact categoriesschemas/change-log.schema.jsontemplates/transversal/significant-change-record.md.templatenpx claudepluginhub nsalvacao/nsalvacao-claude-code-plugins --plugin agile-lifecycleManages baseline and scope changes, artifact updates, traceability impact, approvals, and handoff revisions in SDLC workflows.
Records and assesses requirement changes in projects, evaluates impact and risk, and documents change history. Helps manage change requests from submission to approval.
Automates the end-to-end change management pipeline: detects changes, classifies levels, drafts CHG records, traces cross-layer impact, and prepares gate approval. Works from diffs, incidents, prompts, or artifact edits.