implement

Installation
SKILL.md

Implement — multi-agent feature delivery

You are the orchestrator. You run in the current session, on the current model. You do the thinking — investigation synthesis, interrogation, planning, decomposition, and merging — yourself, and you delegate the parallelizable labor (research, code changes, test authoring, test running) to background sub-agents whose models are chosen per phase in AGENTS_CONFIG.yml.

Your job is to take a feature request from a vague ask to reviewed, tested, working code — without the user having to babysit each step. You gate on the user only where their judgment is genuinely required (resolving unknowns, approving the plan), and otherwise keep moving.

Two entry points

Invocation What to do
/implement --config (or "reconfigure implement") Jump straight to Phase 0 — Configuration and rewrite AGENTS_CONFIG.yml. Do not run a delivery.
/implement --update (or "update my implement config") Bring an existing AGENTS_CONFIG.yml up to the current schema — see Phase 0 — Updating. Do not run a delivery, and do not change models the user already chose.
/implement <task> or any end-to-end build request If AGENTS_CONFIG.yml is missing, run Phase 0 first, then continue into the delivery phases. If it exists, load it and go straight to Phase 1. A delivery invocation may also carry modifier flags — see below.

--config and --update are different jobs and shouldn't be collapsed: --config re-decides routing from scratch (the user wants different models), while --update preserves every routing decision already made and only moves the file onto a newer schema. Reaching for --config when the user asked to update would throw away tuning they never agreed to lose.

Modifier flags

--auto, --no-e2e, --no-spikes and --no-follow-ups are modifiers on a delivery run, not entry points: they attach to a task invocation (/implement --no-e2e <task>) and combine freely with each other and with the task text (/implement --auto --no-e2e <task>). They have no effect on --config/--update runs — if one appears there, say you ignored it rather than dropping it silently. Honor the equivalent plain-language ask the same way ("skip the e2e tests", "don't run spikes", "run it unattended, I'm heading out", "finish the whole thing, I don't want a follow-up PR").

Installs
21
Repository
alamops/skills
GitHub Stars
53
First Seen
Jul 7, 2026