clarify-before-change

Clarifies scope, risks, assumptions, and acceptance criteria before modifying code or rules.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill clarify-before-change-ooooooooooooooooooop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-before-change
Source: https://github.com/ooooooooooooooooooop/personal-ai/tree/main/skills/clarify-before-change
Command: npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill clarify-before-change-ooooooooooooooooooop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous modification requests often lead to wrong edits, scope creep, or irreversible damage. This Skill establishes change boundaries before any modification happens, separating confirmed facts from assumptions so agents never guess their way through risky edits. ## Core Features & Use Cases - Evidence-First Disambiguation: Inspects code, configs, tests, rules, and history to resolve ambiguity from repository evidence before asking the user anything. - Canonical Intent Resolution: Defines the authoritative policy for when an agent may ask questions—autonomous resolution order, reversible assumptions, single-round questioning, and continuation semantics. - Evidence Gates & Decision Records: Classifies requests as audit, change, or high-risk, and records facts, assumptions, risks, minimal path, and non-goals before medium or large modifications. - Use Case: Before restructuring a repository or editing a shared AGENTS.md rule, run this Skill to confirm the target, affected files, rollback path, and acceptance criteria, asking at most one boundary-changing question. ## Quick Start Use clarify-before-change to analyze the scope, risks, and minimal safe path before refactoring this module.

Frequently Asked Questions about clarify-before-change

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

FAQPage Schema
How do I clarify requirements before modifying code?

Restate the goal in one sentence, then inspect code, configs, tests, and history to resolve ambiguity from evidence. Record remaining assumptions, risks, affected files, a minimal path, and acceptance criteria before making any change.

When should an AI agent ask the user questions before editing?

Only when the answer would change the objective, business semantics, irreversible actions, privacy exposure, meaningful cost, or mutually exclusive preferences. All information obtainable from context, memory, repository evidence, or reversible experiments must be resolved autonomously first.

What is a reversible assumption in change management?

A reversible assumption is a low-cost default choice that does not alter the user's goal and has no major external consequences. The agent records it in the decision log and proceeds without pausing for confirmation.

How should an agent handle a user saying continue?

Treat continue as authorization to proceed within the existing objective, constraints, and non-goals. Restore current state, check unmet done criteria, pick the next best action, and never re-ask confirmed information or restart planning.

What is the difference between audit, change, and high-risk requests?

Audit is read-only inspection with no file modifications. Change is an authorized reversible modification with clear goals and verification. High-risk covers deletion, moves, global writes, credentials, permissions, or external system operations requiring explicit confirmation.