ad-deepen

Surface architectural deepening opportunities in stable codebases using Ousterhout/Feathers vocabulary.

728|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-deepen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-deepen
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-deepen
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-deepen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface architectural deepening opportunities in codebases using the Ousterhout/Feathers vocabulary from WORKFLOW §8 (Module / Interface / Depth / Seam / Adapter / Leverage / Locality). The process guides teams to reveal friction points, compare candidate deepening strategies, and align on refactor opportunities without breaking existing behavior.

Core Features & Use Cases

  • Three-phase workflow: explore organically, present numerically indexed candidates with deletion-test framing, and grill the chosen one.
  • Pairs with ad-audit to detect drift and propose refactors; profile-scoped to team and mature contexts.
  • Triggers on standard phrases and ADR-0020-aligned governance to ensure safe, traceable changes.

Quick Start

Run ad-deepen against a stable codebase to surface deepening opportunities and begin the grilling loop with a recommended candidate.

Frequently Asked Questions about ad-deepen

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

FAQPage Schema
How do I identify architectural deepening opportunities in a stable codebase?

You identify architectural deepening opportunities by surfacing friction points in modules with overlapping interfaces, using a three-phase workflow that explores, presents deletion-test framed candidates, and grills the chosen refactor option.

What is the deletion-test framing method for evaluating a refactor candidate?

Deletion-test framing is an evaluation method that numerically indexes candidate refactor strategies to determine if removing a specific seam or adapter would break existing behavior or expose hidden module dependencies.

How do I refactor overlapping module interfaces without breaking existing behavior?

You refactor overlapping module interfaces safely by pairing an audit tool with a deepening workflow that applies ADR-0020-aligned governance, ensuring all architectural changes remain traceable and preserve existing behavior.

Can I use this deepening workflow for a codebase with undefined domain vocabulary?

No, this deepening workflow requires ADR-0020-aligned vocabulary and explicit domain terms to function. Applying it to a codebase without defined domain vocabulary prevents accurate analysis of architectural friction and locality concerns.

When should I use architectural deepening instead of a standard code audit?

Use architectural deepening instead of a standard audit when you need to move beyond drift detection to actively compare and grill refactor candidates in mature modules with overlapping interfaces and locality concerns.