The skill in practice
Effective Delivery
Move the repository and the team forward.
Effective Delivery handles the work around code that already exists: finding the cause of a problem, improving a repository, reviewing changes, updating dependencies, keeping documentation accurate, and helping a team deliver. It connects the request to a verified handoff.
The range
What it covers
- Audits and execution plans
- Root-cause investigation, repository audits, ranked findings, plan reviews, sequencing, and backlog reconciliation.
- Ports and migrations
- Behavior-preserving ports across languages or runtimes, migration contracts, parity checks, and execution plans.
- Pull requests and issue queues
- Risk-based reviews, provider access, CI recovery, delegated queue discovery, isolated implementation, and PR upkeep.
- Dependency maintenance
- Changelog research, compatible upgrade groups, adoption decisions, and focused upgrade PRs.
- Checks and documentation
- Discover and run repository quality gates, report skipped or failed checks honestly, and derive guides and references from the implementation.
- Team delivery
- Responsibilities, delegation, meetings, cognitive load, and reversible management interventions with clear ownership.
From request to result
How it works
Establish the task
Read repository conventions and the requested outcome, authority, and evidence already available.
Do the focused work
Investigate or implement, preserve existing contracts, and keep each change reviewable.
Verify and hand off
Run the relevant checks and report what passed, failed, was skipped, or remains unproven.
The result: A reviewable change or diagnosis, with the checks and remaining uncertainty clearly reported.
Ask in your own words
Try a real task.
Give the agent the relevant files, source material, and constraints. Start with an outcome like one of these:
Why does this endpoint return stale data after a deploy? Read-only — trace it and tell me the best-supported cause, not a fix.
Research our outdated dependencies, group the compatible ones, and prepare focused upgrade PRs with reviewer-grade bodies.
Validate this branch. Tell me exactly which checks ran, which were skipped, and what that leaves unproven.
Choose the right discipline
When to use it
Use this skill for existing repositories, changes, PRs, dependencies, documentation, and team responsibilities. New architecture, data models, and test design belong to Effective Engineering; browser implementation belongs to Effective Web. Review, implementation, publishing, and merging remain distinct actions governed by the task’s authorization.
For the complete workflow and routing rules, read the agent instructions on GitHub .
Add this discipline
Install Effective Delivery
With Node.js installed, run this command for an agent that supports Agent Skills:
npx skills add sebastian-software/effective-agent --skill effective-delivery
Then describe your task in the agent. This skill works on its own; add another when the work crosses disciplines.
For managed installations, pinned selections, and multiple agent targets, see all installation options or the DALO setup guide.