Software Development

This skill equips you to make a change the way a project expects: formatted and linted, kept to the smallest scope that satisfies the task, verified against the surfaces it puts at risk, operated through the commands the project documents, grounded in current vendor docs where a dependency moves fast, and landed as a well-described pull request. Reach for it on every task that touches the project — it is the baseline the other, more specific skills build on.

Load only the reference sections a given task touches; each one below routes to the detail.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Independent Operations

A turn is priced by the size of the context it carries, not by what it does: a turn that issues one operation costs about what a turn that issues several unrelated operations costs, because the price follows the turn, not what is packed into it. Spreading N operations that do not depend on one another across N turns therefore costs roughly N times what issuing the same N together, in one turn, costs — without producing more than the one-turn version would have.

See independent-operations.md for:

• the pricing rationale in full — what a turn is billed for, and why the multiplier is the number of turns rather than the number of operations
• resolving uncertainty about whether an operation depends on another's result through the dependency test, worked through with a Good/Bad example pair
• why no numeric target is given for how many operations belong in one turn
• resolving an apparent conflict with change-management.md's incremental-changes rule