audit-necessity

Identify code and dependencies whose maintenance cost exceeds delivered value.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill audit-necessity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-necessity
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/audit-necessity
Command: npx skills add https://github.com/JHostalek/dotclaude --skill audit-necessity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies code, features, abstractions, dependencies, and operational burdens that do not justify their continuing maintenance cost, while protecting required behavior, compatibility, and system obligations.

Core Features & Use Cases

  • Necessity Analysis: Reconstruct intended outcomes, capability ownership, runtime paths, dependencies, and lifecycle obligations before judging what can be removed.
  • Evidence-Based Decisions: Classify findings as confirmed cuts, worthwhile improvements, unresolved questions, or justified keeps using usage evidence, architecture context, and total removal cost.
  • Safe Reduction Planning: Trace consumers, variants, stored state, compatibility requirements, operational assets, migration paths, rollback concerns, and verification needs for each proposed change.
  • Use Case: Apply it to a service folder to determine whether obsolete feature flags, duplicate mechanisms, unused internal abstractions, or stale support assets can be safely deleted.

Quick Start

Use the audit-necessity skill to review the specified path and identify safe cuts, worthwhile simplifications, unresolved questions, and justified keeps with evidence and a completion ledger.

Frequently Asked Questions about audit-necessity

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

FAQPage Schema
How do I identify code and dependencies to safely remove for technical debt reduction?

Technical debt reduction requires evidence-based necessity analysis that reconstructs runtime paths, capability ownership, and lifecycle obligations to classify code as confirmed cuts, worthwhile improvements, or justified keeps. This ensures continuing maintenance cost does not exceed delivered value.

What is necessity analysis in software architecture audits?

Necessity analysis is an architecture audit technique that evaluates whether operational mechanisms, abstractions, and data lifecycles justify their continuing cost. It traces consumers, variants, and compatibility requirements to determine safe deletion candidates without losing required system outcomes.

How can I reduce maintenance cost by removing unused internal abstractions?

Reducing maintenance cost involves applying necessity analysis to internal abstractions by evaluating usage evidence and total removal cost. Findings are classified into confirmed cuts, unresolved questions, or justified keeps, producing a completion ledger for safe deletion or replacement.

When should I keep legacy code instead of removing it during dependency reduction?

Legacy code should be kept when necessity analysis confirms it fulfills domain obligations, security requirements, or compatibility constraints that outweigh its maintenance cost. Evidence-based evaluation classifies these as justified keeps to preserve required system outcomes and reliability.

Can I audit a service folder to find duplicate mechanisms and stale support assets for deletion?

Auditing a service folder identifies obsolete feature flags, duplicate mechanisms, and stale support assets by reconstructing intended outcomes and tracing dependencies. Safe reduction planning generates migration paths, rollback plans, and verification needs for each confirmed cut.