Roll back a spec to an earlier pipeline phase and mark artifacts stale.
npx skills add https://github.com/amoutiers/maxi-superpowers --skill revise-amoutiers
Please help me install this Agent Skill. Skill: revise Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/revise Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill revise-amoutiers
Rolling back a spec to an earlier pipeline phase when requirements or design change helps keep the project aligned with current goals and prevents downstream drift.
Describe the change that requires revision and run /maxi:revise to roll back to the target status.
High-intent search queries and answers about installing and using this skill.
To rollback a spec when requirements change, you describe the design change and trigger the revision command. The system validates that the requested status is allowed and writes the new status to spec.md, marking downstream artifacts as stale.
When you reverse a spec transition, downstream artifacts are left on disk but explicitly marked as stale. This prevents downstream drift while keeping previous outputs accessible for reference or deletion.
No, you cannot roll back a spec from done or cancelled statuses. The system enforces guardrails that validate the current state permits a reverse transition to a previous phase like clarified, planned, tasked, analyzed, or implemented.
When multiple in-flight specs exist, the system prompts you to select the target slug. This ensures the rollback operation targets the correct active spec without accidentally modifying unrelated pipeline phases.
Yes, rolling back a pipeline spec requires manual confirmation. The system prompts for consent before writing the new status to spec.md to ensure the reverse transition is intentional and provenance is recorded for auditability.
A guarded rollback process for spec status changes prevents invalid reverse transitions and records provenance for auditability. It keeps the project aligned with current goals by validating allowed statuses before modifying spec.md.
tinkermonkeyValidate orchestrator restart by inspecting logs and confirming job reconciliation.
noelserdnaRead pipeline-state.json to verify stage artifacts and detect stale results.
AhmedElhadareyCoordinate Conductor track lifecycles with Evaluate-Loop phases and v2 metadata.
pradeepmouliRefine an existing spec.md in-place within a spec-kit project structure.
