How do I install the Reuse Or Justify skill?

Run npx skillmds@latest add cwijayasundara/reuse-or-justify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reuse Or Justify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reuse Or Justify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reuse Or Justify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reuse Or Justify?

cwijayasundara (@cwijayasundara) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reuse Or Justify by cwijayasundara — Agent Skill

Name: Reuse Or Justify
Author: cwijayasundara

Reuse Or Justify

Use when reuse-scout fires at intake (band ≥ medium, a touched constitution invariant, or a same-release clone cluster) — run the confidence-gated reuse-vs-new dialogue and record the decision + performance budget before code. [Internal discipline — invoked by /change, /feature, and /sprint intake; direct use is a power-user path.]

File contents

Reuse-or-Justify Intake Dialogue

Resolve one question before a change is built: does this increment extend an existing seam, or justify a new structure? This is the forcing function that keeps sprint-by-sprint work from accreting parallel clones. It runs at intake, before the failing test.

Step 1 — Ground (deterministic)

Run reuse-scout for the change's goal:

node .claude/scripts/reuse-scout.js --graph specs/brownfield/code-graph.json --goal "<the change's one-line goal>" [--constitution specs/design/constitution.md] [--batch <stories.json-or-directory>]

Pass --goal a plain goal string, never a file path. For feature/sprint epic scope, pass --batch the epic's story-list JSON or its story directory (e.g. specs/stories/sprint-N/) so intra-batch clusters across the sprint's stories surface.

Read its JSON: fire, band, target_seam, target_action, candidates[] (each with path, total_score, recommended_action, matched_terms), touched_invariants[], intra_batch[].

Step 2 — Decide whether to interrogate

fire: false → do not interrogate. Record the net-new assumption and proceed: node .claude/scripts/record-reuse-decision.js --story <id> --decision net-new --band low --justification "reuse-scout found no goal-relevant seam, invariant, or same-release clone". Continue the caller's flow. This record is what keeps the provenance trail complete — it is not optional.
fire: true → interrogate at the genuine fork points only (below). One question at a time.

Step 3 — The dialogue (only the questions the grounding raises)

Ask each question with the decision, your recommendation, and why it matters (mirrors the clarify format). Ask one at a time.

Step 4 — Record (deterministic)

Once resolved, record each fork:

node .claude/scripts/record-reuse-decision.js --story <id> --decision <extend|new-seam|net-new> \
  --band <high|medium|low> [--seam <path-or-name>] [--action <extend|wrap|introduce-adapter|split|new>] \
  --justification "<one line>" [--invariant-impact "<txt>"] [--budget '<json>'] [--options "<considered>"]

Pass --band reuse-scout's reported band so the durable record carries the confidence the P2 seam-conformance gate reads.

Then reflect the outcome in the design artifacts (per the /design authoring instructions): set the extended component's seam/extension_mechanism/instances/budget in component-map.md, and extends_seam/budget_inherited_from in design-traces.json. These are optional fields the ownership/trace sensors already tolerate — do not backtick non-path values.

Gotchas

Do not interrogate on fire: false — that trains the team to dismiss the dialogue. The gate is deliberately confidence-gated.
A split/avoid target_action is information, not a blocker — surface it so the human isn't told to extend something that should be split.
The decision is a constraint the stage-4 enforcement (duplication ratchet, and P2's seam-conformance) verifies later; record the seam you actually committed to.

---name: reuse-or-justifydescription: Use when reuse-scout fires at intake (band ≥ medium, a touched constitution invariant, or a same-release clone cluster) — run the confidence-gated reuse-vs-new dialogue and record the decision + performance budget before code. [Internal discipline — invoked by /change, /feature, and /sprint intake; direct use is a power-user path.]---# Reuse-or-Justify Intake DialogueResolve one question before a change is built: **does this increment extend an existing seam, or justify a new structure?** This is the forcing function that keeps sprint-by-sprint work from accreting parallel clones. It runs at intake, before the failing test.## Step 1 — Ground (deterministic)Run reuse-scout for the change's goal:```bashnode .claude/scripts/reuse-scout.js --graph specs/brownfield/code-graph.json --goal "<the change's one-line goal>" [--constitution specs/design/constitution.md] [--batch <stories.json-or-directory>]```Pass `--goal` a plain goal string, never a file path. For feature/sprint epic scope, pass `--batch` the epic's story-list JSON **or** its story directory (e.g. `specs/stories/sprint-N/`) so intra-batch clusters across the sprint's stories surface.Read its JSON: `fire`, `band`, `target_seam`, `target_action`, `candidates[]` (each with `path`, `total_score`, `recommended_action`, `matched_terms`), `touched_invariants[]`, `intra_batch[]`.## Step 2 — Decide whether to interrogate- **`fire: false`** → do not interrogate. Record the net-new assumption and proceed: `node .claude/scripts/record-reuse-decision.js --story <id> --decision net-new --band low --justification "reuse-scout found no goal-relevant seam, invariant, or same-release clone"`. Continue the caller's flow. This record is what keeps the provenance trail complete — it is not optional.- **`fire: true`** → interrogate at the genuine fork points only (below). One question at a time.## Step 3 — The dialogue (only the questions the grounding raises)Ask each question with the decision, your recommendation, and why it matters (mirrors the clarify format). Ask one at a time.<question type="reuse-vs-new">Fires when `target_seam` is set. Present the ranked reuse candidate(s) and its `target_action`:- If `target_action` is `extend`/`wrap`/`introduce-adapter`: recommend extending `target_seam`.- If `target_action` is `split`/`avoid`: surface it honestly — the closest existing code is `target_seam` but it is classified `<action>`; ask whether to extend anyway, refactor first, or justify a new structure.Options: (a) extend the named seam, (b) add a pluggable strategy to it, (c) justify a new structure. A new structure requires a one-line justification naming why no existing seam fits.</question><question type="invariant-impact">Fires when `touched_invariants` is non-empty. For each, ask the human to confirm the change stays within the invariant, or to explicitly propose amending it (itself a reviewed decision).</question><question type="intra-batch">Fires when `intra_batch` clusters exist (feature/release scope). Present each cluster of stories that share a seam and ask whether to consolidate them onto one seam before building, rather than implementing each separately.</question><question type="budget">When the decision creates or extends a seam, ask for its performance budget (latency/memory/throughput/tokens/cost as applicable), recommending the inherited budget when extending an existing seam.</question>## Step 4 — Record (deterministic)Once resolved, record each fork:```bashnode .claude/scripts/record-reuse-decision.js --story <id> --decision <extend|new-seam|net-new> \ --band <high|medium|low> [--seam <path-or-name>] [--action <extend|wrap|introduce-adapter|split|new>] \ --justification "<one line>" [--invariant-impact "<txt>"] [--budget '<json>'] [--options "<considered>"]```Pass `--band` reuse-scout's reported `band` so the durable record carries the confidence the P2 seam-conformance gate reads.Then reflect the outcome in the design artifacts (per the /design authoring instructions): set the extended component's `seam`/`extension_mechanism`/`instances`/`budget` in `component-map.md`, and `extends_seam`/`budget_inherited_from` in `design-traces.json`. These are optional fields the ownership/trace sensors already tolerate — do not backtick non-path values.## Gotchas- Do not interrogate on `fire: false` — that trains the team to dismiss the dialogue. The gate is deliberately confidence-gated.- A `split`/`avoid` `target_action` is information, not a blocker — surface it so the human isn't told to extend something that should be split.- The decision is a constraint the stage-4 enforcement (duplication ratchet, and P2's seam-conformance) verifies later; record the seam you actually committed to.

Frequently asked questions