What problem does it solve? Removing a completed feature from a codebase is risky: later commits may depend on it, history can be lost, and ad-hoc reverts often break unrelated work. This Skill plans a guarded rollback by locating the exact feature commit, reviewing later changes for dependency risk, and writing a reviewable rollback spec before any code changes. ## Core Features & Use Cases - Exact Commit Resolution: Matches a build-plan number, feature name, or archive path to the squashed git commit that introduced the feature, refusing ambiguous or merge-commit targets. - Later-Change Risk Review: Inspects every commit after the target touching the same product paths and classifies the rollback as no overlap, compatible, dependency risk, or blocked. - Guarded Rollback Spec: Writes a Type: Rollback spec to blueprint/context/current-feature.md with protected paths, verification commands, and observable removal criteria, then stops for human review before /implement applies changes. - Use Case: After shipping a PDF export feature that corrupts files, run /rollback 4 to generate a reviewed plan that reverses only that feature's product diff while preserving Blueprint history and later compatible work. ## Quick Start Ask the assistant to roll back a completed feature by name or build-plan number, for example: run /rollback 4 because the new export flow is corrupting files.
