Update to Claus Argos Skill OS

{
  "description": "Implement an approved software feature or change in an existing repository through evidence-based preflight, bounded decision authority, reversible edits, tests, regression checks, independent review, and a verified change report. Use when the user asks to implement a specification, execute a coding task, or change code under controlled scope. Do not use to invent product requirements, create the specification, conduct a read-only audit, perform a broad migration, or diagnose an unknown defect as the primary task.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 302
    }
  ],
  "name": "implement-controlled-software-changes",
  "skill_md_contents": "---\nname: implement-controlled-software-changes\ndescription: Implement an approved software feature or change in an existing repository through evidence-based preflight, bounded decision authority, reversible edits, tests, regression checks, independent review, and a verified change report. Use when the user asks to implement a specification, execute a coding task, or change code under controlled scope. Do not use to invent product requirements, create the specification, conduct a read-only audit, perform a broad migration, or diagnose an unknown defect as the primary task.\n---\n\n# Implement Controlled Software Changes\n\nImplement approved scope without silently changing the product, architecture, design, interfaces, data, security posture, or surrounding code.\n\n## Preflight\n\n1. Inspect repository instructions, working-tree state, relevant source, tests, configuration, and the controlling specification.\n2. Identify source versions, precedence, protected areas, permitted files or modules, environment, required commands, and rollback path.\n3. Convert the assignment into the shared [task execution contract](../../shared/expert-system/task-execution-contract.md).\n4. Route the smallest expert set using the [expert routing model](../../shared/expert-system/expert-routing-model.md). Assign an independent reviewer when risk warrants it.\n5. Classify choices with the [decision-authority model](../../shared/expert-system/decision-authority-model.md).\n\nStop before editing when a required source is missing, controlled sources conflict, the repository differs materially from the specification, acceptance cannot be tested, or a Class-1 decision is unresolved. Report the exact blocker instead of inventing a solution.\n\n## Controlled implementation\n\n1. Establish a recoverable before-state through existing version control or an approved checkpoint. Preserve user changes and unrelated work.\n2. Implement the smallest coherent change that satisfies the approved contract.\n3. Make Class-3 engineering choices within repository conventions and record only material ones.\n4. Exercise Class-2 judgment only when role, target, bounds, reversibility, evidence, review, and stop condition are explicit. Log the decision.\n5. Do not introduce a dependency, tool, framework, service, migration, feature, redesign, or unrelated refactor without authority.\n6. Keep external mutations, deployment, publication, messages, purchases, and destructive operations behind their own approvals.\n\n## Verification\n\n- Run the specified focused tests first, then applicable type, lint, build, integration, regression, security, accessibility, performance, and smoke checks.\n- Inspect the real changed behavior. A passing command is not proof of user-visible correctness.\n- Compare before and after for protected behavior and connected interfaces.\n- Route visual acceptance to `$verify-production-implementation` or `$audit-premium-digital-experience` checkpoint mode when applicable.\n- Apply the [specialist review model](../../shared/expert-system/specialist-review-model.md) for critical work.\n\nCorrect compliance with a defective specification is not success. If implementation exposes a specification defect, stop the affected path, preserve evidence, and return it to the responsible author or owner.\n\n## Output\n\nReturn the implemented outcome, exact change manifest, material decisions by class, test commands and actual results, regression evidence, reviewer result, deviations, rollback instructions, residual risks, and remaining approvals. Commit only when the project gate explicitly requires or the user authorizes it.\n"
}