ospec-change

# OSpec Change Use this skill for small or routine requirements where the classic OSpec 1.0 change flow is enough. ## Scope This skill is the fast change lifecycle inside an initialized OSpec project: - requirement intake - change naming or matching - proposal and task refinement - implementation guidance - verification - archive readiness check - finalize closeout The user owns profile selection. Once the user chooses a change, keep it on the classic flow regardless of complexity, flags, file count, or batch size. Never auto-promote, reject, or replace it with a Goal. Use `ospec-goal` only when the user explicitly selects a Goal. ## Read Order 1. `.skillrc` 2. `ospec index query <keyword...>` for the relevant `.ospec/SKILL.index.json` entries (root `SKILL.index.json` for legacy classic projects); never read the whole index file — it grows without bound as changes archive 3. `.ospec/for-ai/change-protocol.md` for nested projects, or legacy `for-ai/change-protocol.md` 4. `.ospec/changes/active/<change>/proposal.md`, `tasks.md`, and `state.json` for nested projects, or their legacy classic paths 5. Read `verification.md` only when entering verification 6. Read `review.md` only when entering closeout If `change-protocol.md` is missing, fall back to the full `ai-guide.md` and `execution-protocol.md`. Read those full guides otherwise only when a blocking plugin is active or one specific ambiguous rule requires them. ## Language - Follow the project-adopted document langu...