replace-with-capability-idlisted

# Capability title ## Purpose State the engineering outcome this capability improves. ## When to use - Give concrete activation situations. - Prefer task/repository conditions over keyword lists. ## Inputs Inspect the user intent and the relevant repository evidence before prescribing an approach. ## Method 1. Understand the local repository pattern. 2. Identify the minimum engineering problem to solve. 3. Apply the capability method proportionally. 4. Verify the result with repository-appropriate evidence. ## Decision points Describe choices the agent must make from evidence rather than hard-coding a framework or library. ## Project adaptation Reuse existing repository conventions unless they cannot satisfy the task or an explicit requirement justifies changing them. ## Failure modes and anti-patterns - Do not broaden scope without evidence. - Do not invent successful verification. - Do not turn recommendations into hard prohibitions without a material reason. ## Verification Define what observable evidence demonstrates that this capability achieved its intended outcome. ## Handoff Reference related capabilities only when their distinct method is actually needed.