---
name: software-craft
description: "Use when repository-grounded software work is cross-language or has no narrower language-specific owner."
---

# Software Craft

Own the requested repository outcome with the smallest coherent change. Let the task and repository determine the implementation path; this skill is a router for useful decision context, not a fixed itinerary.

## Choose context when needed

- Use [architecture](references/architecture.md) for ownership, boundaries, or a cross-module design decision.
- Use [implementation](references/implementation.md) when the change is more than a local edit or needs an explicit completion contract.
- Use [review](references/review.md) when assessing an existing change or falsifying a proposed solution.
- Use [verification](references/verification.md) when evidence depth or an external boundary is material.

Do not load these references for a typo, a clearly local change, or a task whose repository instructions already settle the decision. Python repository work belongs to `python-engineering-harness`; explicit MARGOS, ReThinking, and Agent Plugins Author requests remain separate.

## Ownership and completion

Preserve repository conventions, public behavior, user scope, and real safety boundaries. Safe local implementation may continue through relevant checks and repairs without an approval pause. Production, destructive, credentialed, irreversible, or external actions remain separately authorized.

Finish with the requested behavior, relevant evidence, and unresolved risks. Do not claim a check, installation, deployment, or external result that was not observed.