Implement Change

Use this skill only when the user explicitly selects it by name. A request to implement, verify or deliver a change does not activate it by itself. Once selected, keep it active for the same implementation task and its direct follow-ups. A separate task requires a new explicit selection.

Deliver the selected outcome through code, evidence and a Draft PR, with progress written back to existing authorized Working Records. Honor a narrower requested endpoint such as local changes or a commit. Merging PRs, deploying and releasing are outside this workflow.

Use Assess Findings and its Investigate with Evidence dependency for shared records and decision-changing factual gaps. Reuse an existing assessment; implementing an agreed request does not require running discovery first. Read the working-record contract when source records or configured history exist and coordination before assigning work. If a dependency is unavailable, report the missing method and continue only work whose scope and evidence remain supported; do not claim its checks occurred.

English output

simple-english is optional. If it is installed and readable, use it when writing or revising English prose. Reuse instructions already loaded. If it is unavailable, write clear English and complete the task normally. Its absence does not require installation, an exception, or draft-only delivery.

Preserve meaning, uncertainty, requirement strength, domain terms, and requested formats when style rules conflict. Keep the requested language. Preserve code, identifiers, commands, original quotations, and historical evidence.