process trained

Authorized goal -> live contract -> smallest coherent change -> fresh boundary proof -> integration under existing authority. A skill does not create a new permission gate. The shared checkout is the default.

Read the selected guide and the project rules before modifying owned files.

• Inspect live state before questions; resolve routine choices from evidence.
• Use a plan for coupled work and proportionate tests for material behavior.
• Keep peer edits unstaged and verify the actual result before claiming done.

Design, planning, debugging, tests, and completion each have a short route, without inventing a new process for every task.

Imported process habits can be too heavy for a bounded edit. Choose the smallest step that proves the requested outcome.

Upstream Superpowers procedures default to a worktree and per-change approval. Local rules take precedence here: shared checkout and persistent authorization.

The Superpowers brainstorming and worktree procedures are the upstream sources. Their default approval and isolation steps yield to the operator's shared-checkout and persistent-authorization instructions. That override is a local rule, not an upstream claim.

No version-specific process defect has been verified in a project task.

If repeated permission prompts interrupt an authorized task, check the current request against prior authority, then continue the routine work. If a plan prescribes an unavailable tool, inspect the runtime and use the closest existing procedure.