sebastian-software/skills.sebastian-software.com/effective-delivery

Effective Delivery

Choose the route that matches the requested repository outcome. Load its references only for the decisions at hand; routine edits do not need a full repository survey.

Carry authorized implementation through relevant checks and the requested handoff. An audit-only or diagnosis-only request stays read-only; a combined audit-and-fix request already authorizes the fix. Ask only for a consequential missing decision or authority not already granted.

Preserve unrelated work, discover repository-native commands, and report material evidence gaps. Rank findings by demonstrated impact and remedy cost; a clean audit is a valid result. Keep scrutiny high at security, privacy, money, data-loss, and irreversible boundaries. Never expose secret values.

When a delivery task drafts communication to teammates, use effective-writing and its Metro English route by default when available. This covers review bodies, approvals, PR and issue text, replies, and team updates, including first drafts without a separate style request. Delivery retains the technical judgment and publication authority; the writing route preserves repository language and channel rules.

Route by Intent

Any route that creates, adopts, writes in, integrates from, or removes a Git worktree uses the shared worktree safety contract.

Routing Boundaries

• effective-engineering: system and data contracts, Rust and server/shared

TypeScript depth, focused non-frontend test design, and benchmark methodology.

• effective-web: browser design, implementation, frontend diagnosis and tests,

annotated screenshots of rendered changes, interface copy, and web compliance.

• effective-product: product direction, research, scope, and durable decisions

recorded as ADRs.

• effective-writing: editorial prose, natural team English, and locale

typography. Repository-derived or controlled-language documentation stays here.

• effective-marketing: positioning and commercial copy, including the

marketing portions of a README.

A named issue, PR, URL, or finite issue list is targeted work. Select an open backlog only when queue selection is delegated. Do not invent repository policy, delivery authority, private plan stores, or organizational evidence. Seek qualified support when People/HR, employment-law, health, security, or crisis judgment exceeds the available competence.