luastoned/code-kit/adopt-change-shape

Adopt ChangeShape

Adapt the execution contract to the project's actual ownership, validation, and coordination needs. A request for an audit or recommendations is read-only; a request to adopt, apply, or synchronize authorizes the corresponding guidance edits. Infer mode from the conversation, including earlier authorization.

Sources and Scope

Resolve symlinks to locate this skill in code-kit, then read docs/workflows/change-shape.md two directories above the skill directory, or use the source supplied by the user. It contains the canonical operating contract. If unavailable, check the known source location before requesting a path; do not invent a substitute contract.

Read its examples only for a classification or artifact-design question, and its changelog only when upgrading a recorded version. Read EvidenceProbe only when adapting a bounded-decision route that needs more than the ChangeShape contract explains. Following a link does not make every linked document required.

Identify the requested repository or project boundary. Read applicable AGENTS.md files and inspect relevant workflow rules, ownership, validation commands, active coordination, and version-control status. Follow additional document links only when they resolve an adoption question.

Audit or Adoption

Compare behavior with the operating contract, not filenames, headings, or identical wording. Check the execution flow, classification, verification and risk acceptance, authorization and completion, coordination capacity, artifact lifecycle, and, when OutcomeFlow applies, the outcome handoff.

In audit mode, report compatible, partially compatible, or adoption recommended, with material gaps and the smallest useful changes. Include the recorded and current versions; changelog entries not yet adopted are gaps. Missing examples, optional artifacts, or generic advice are not gaps. Stop without editing.

In adoption mode:

• Preserve local architecture, commands, security, release, ownership, and commit rules.
• Adapt the missing contract behaviors into existing workflow or agent guidance; do not copy the full reference or create a second classifier.
• Record the authorized endpoint and meaningful escalation conditions. Prior authorization and delegated decisions remain valid through verification and repairs.
• Treat solo-owner concurrency limits as defaults for that operating model; preserve explicitly delegated ownership.
• Reuse existing coordination. Create a work index or temporary specification only for active work whose boundaries must survive and have no adequate home.
• Classify active work only when it helps adoption. Do not manufacture candidates or reclassify an entire backlog.
• Consolidate duplicate guidance within the requested scope. Remove material history only when its removal is authorized.

Version

Keep the adopted rules together in one section of the target guidance and start that section with the source version on its own line: Version: x.y.z. The line lets later runs see whether an update exists; add no other provenance.

• No recorded version: compare with the full contract, then record the current version.
• Lower recorded version: read the entries after it in the Changelog section of docs/workflows/references/change-shape.md, adapt only those changes while preserving local adaptations, then update the line.
• Same version: nothing to upgrade.
• Higher recorded version: the code-kit checkout is stale. Report it and leave the section unchanged.

Completion

Check changed links, Markdown, and the final diff for conflicting authorities or duplicated rules. Run relevant local checks and git diff --check when Git is available. Fix issues introduced by the change before handing back.

Report the files changed, where the operational rules live, the recorded version, material local adaptations, and verification or unresolved decisions. Adoption does not authorize implementing product work, publishing, or integrating unrelated changes.