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.
Route by Intent
| User intent |
Read |
| Coordinate multi-stage or mixed-domain work from an unclear request to a review-ready handoff |
Workflow Orchestration |
| Audit a repository, explain a defect or surprising behavior, prioritize improvements, simplify code, or create, review, or reconcile an implementation plan |
Codebase Audit and Plans |
| Plan or execute a behavior-preserving port across languages, runtimes, frameworks, platforms, storage engines, or major APIs |
Behavior-Preserving Ports |
| Review a pull request, act on review feedback, fix findings, recover CI, or keep a branch current |
PR Review and Upkeep |
| Select a provider adapter, use the GitHub CLI recipes, or return a caller-owned review handoff |
Review Provider Access |
| Discover, rank, process, reconcile, or monitor an unspecified live issue queue when the user delegates target selection |
Issue Queue Autopilot |
| Add, choose, update, or group external dependencies; assess changelog impact; create dependency PRs |
Dependency Updates |
| Discover and run the repository's established typecheck, lint, format, test, build, benchmark, or documentation checks and report the evidence |
Repository Validation |
| Write or verify READMEs, guides, API and CLI references, migration notes, JSDoc, TSDoc, rustdoc, examples, or controlled-language documentation |
Technical Documentation |
| Resolve unclear ownership, overloaded leaders, weak one-to-ones, coordination drag, decision stalls, or a proposed reorganization |
Engineering Leadership |
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,
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.
1---2name: effective-delivery3description: Audit, diagnose, improve, and deliver changes in existing repositories: implementation plans, behavior-preserving ports, PR review and upkeep, issue queues, dependency upgrades, running existing checks, technical documentation, and engineering team ownership. Use for repository lifecycle work; system design and focused non-frontend test design belong to effective-engineering, browser work to effective-web.4---56# Effective Delivery78Choose the route that matches the requested repository outcome. Load its9references only for the decisions at hand; routine edits do not need a full10repository survey.1112Carry authorized implementation through relevant checks and the requested13handoff. An audit-only or diagnosis-only request stays read-only; a combined14audit-and-fix request already authorizes the fix. Ask only for a consequential15missing decision or authority not already granted.1617Preserve unrelated work, discover repository-native commands, and report18material evidence gaps. Rank findings by demonstrated impact and remedy cost;19a clean audit is a valid result. Keep scrutiny high at security, privacy, money,20data-loss, and irreversible boundaries. Never expose secret values.2122## Route by Intent2324| User intent | Read |25| --- | --- |26| Coordinate multi-stage or mixed-domain work from an unclear request to a review-ready handoff | [Workflow Orchestration](references/route-orchestration.md) |27| Audit a repository, explain a defect or surprising behavior, prioritize improvements, simplify code, or create, review, or reconcile an implementation plan | [Codebase Audit and Plans](references/route-audit.md) |28| Plan or execute a behavior-preserving port across languages, runtimes, frameworks, platforms, storage engines, or major APIs | [Behavior-Preserving Ports](references/route-porting.md) |29| Review a pull request, act on review feedback, fix findings, recover CI, or keep a branch current | [PR Review and Upkeep](references/route-review.md) |30| Select a provider adapter, use the GitHub CLI recipes, or return a caller-owned review handoff | [Review Provider Access](references/route-review-access.md) |31| Discover, rank, process, reconcile, or monitor an unspecified live issue queue when the user delegates target selection | [Issue Queue Autopilot](references/route-issue-autopilot.md) |32| Add, choose, update, or group external dependencies; assess changelog impact; create dependency PRs | [Dependency Updates](references/route-dependencies.md) |33| Discover and run the repository's established typecheck, lint, format, test, build, benchmark, or documentation checks and report the evidence | [Repository Validation](references/route-validation.md) |34| Write or verify READMEs, guides, API and CLI references, migration notes, JSDoc, TSDoc, rustdoc, examples, or controlled-language documentation | [Technical Documentation](references/route-docs.md) |35| Resolve unclear ownership, overloaded leaders, weak one-to-ones, coordination drag, decision stalls, or a proposed reorganization | [Engineering Leadership](references/route-leadership.md) |3637Any route that creates, adopts, writes in, integrates from, or removes a Git38worktree uses the shared [worktree safety](references/worktree-safety.md) contract.3940## Routing Boundaries4142- `effective-engineering`: system and data contracts, Rust and server/shared43 TypeScript depth, focused non-frontend test design, and benchmark methodology.44- `effective-web`: browser design, implementation, frontend diagnosis and tests,45 interface copy, and web compliance.46- `effective-product`: product direction, research, scope, and durable decisions47 recorded as ADRs.48- `effective-writing`: editorial prose, natural team English, and locale49 typography. Repository-derived or controlled-language documentation stays here.50- `effective-marketing`: positioning and commercial copy, including the51 marketing portions of a README.5253A named issue, PR, URL, or finite issue list is targeted work. Select an open54backlog only when queue selection is delegated. Do not invent repository policy,55delivery authority, private plan stores, or organizational evidence. Seek56qualified support when People/HR, employment-law, health, security, or crisis57judgment exceeds the available competence.
sebastian-software