grimoire-remove

Decommission features or deprecated decisions with a tracked, auditable workflow.

Updated Jan 26, 2025

Search Tags:#deprecation #change-management #decision-tracking #grimoire #feature-removal

Ready to run

npx skills add https://github.com/jlissner/lissner.io --skill grimoire-remove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grimoire-remove
Source: https://github.com/jlissner/lissner.io/tree/main/.claude/skills/grimoire-remove
Command: npx skills add https://github.com/jlissner/lissner.io --skill grimoire-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove a feature or deprecate a decision through a tracked, deliberate change, ensuring decisions are auditable and reversible.

Core Features & Use Cases

Formal removal workflow: identify target feature or ADR, assess impact, plan changes, and document migration steps.
Artifact generation: produce change manifests, tasks lists, and retroactive decisions to preserve rationale.
Use Case: when a feature conflicts with policy or product strategy, this guide helps sunset it safely.

Quick Start

Identify the feature to remove, confirm scope, and begin the change plan with migration steps.

Frequently Asked Questions about grimoire-remove

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

FAQPage Schema

How do I safely remove a deprecated feature from my codebase?▼

To safely remove a deprecated feature, use a formal removal workflow that includes impact assessment, migration planning, artifact generation, and change verification across code, docs, and tests. This ensures the feature sunset is tracked and reversible.

What is the best way to track architecture decision cleanups?▼

Tracking architecture decision cleanups requires a formal workflow that generates change manifests, task lists, and retroactive decisions. This approach preserves the rationale behind deprecated decisions, making the change management process auditable.

How do I sunset a software feature that conflicts with product strategy?▼

Sunsetting a software feature that conflicts with product strategy involves identifying the target feature, confirming scope, assessing impact, and documenting migration steps. This deliberate process ensures all code, doc, and test changes are tracked.

Can I document migration steps when deprecating an ADR?▼

Yes, you can document migration steps when deprecating an ADR by generating artifacts like change manifests and task lists. This allows your software product team to execute the feature removal while preserving the auditable decision history.

When should I use a formal feature removal workflow?▼

Use a formal feature removal workflow when your software product team needs to decommission a feature or deprecated decision safely, ensuring the changes across code, docs, and tests are deliberate, auditable, and reversible.

Does feature sunset planning work for both code and documentation updates?▼

Yes, feature sunset planning works across code, docs, and tests by applying a tracked change management process. It assesses the full impact of deprecated decisions and generates the necessary artifacts to verify the removal.