implement-spec

Implement the result of /to-spec and /to-tickets in code.

npx skills add https://github.com/mattpocock/skills --skill implement-spec

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

The goal is the entire spec implemented on a single integration branch, with every ticket resolved the way the issue tracker closes work.

The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.

Start every subagent with a fresh context window.

Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.

Implementer subagents should be run in the background where possible for maximum concurrency.

Steps

  1. Read the spec and tickets to understand the task graph.

  2. (optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.

  3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.

  4. Use a fresh implementer subagent for each ticket, each in its own worktree on its own branch. Each implementer subagent:

    • confirms its worktree is based on the integration branch before starting, and resets onto it if not;
    • calls the Skill tool with tdd to build the ticket;
    • merges the integration branch tip into its own branch before reporting done
  5. Once an implementer subagent completes, merge its work to the integration branch with a merger subagent.

  6. If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.

  7. Once all tickets are complete, call the Skill tool with code-review on the integration branch. Fix all issues raised by the code review in a single fresh implementer subagent.

  8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.

  9. Clean up all implementer subagent worktrees.

Más skills de mattpocock

ask-matt
mattpocock
Pregunta qué habilidad o flujo se adapta a tu situación. Un enrutador sobre las habilidades invocadas por el usuario en este repositorio.
communicationresearchproductivity
chief-of-staff
mattpocock
Persigue un objetivo a largo plazo en una sola sesión coordinando subagentes.
productivityproject-managementcommunication
claude-handoff
mattpocock
Transfiere la conversación actual a un agente de fondo nuevo que retoma el trabajo de inmediato.
codebase-design
mattpocock
Vocabulario compartido para diseñar módulos profundos. Úsalo cuando el usuario quiera diseñar o mejorar la interfaz de un módulo, encontrar oportunidades de profundización, decidir dónde va una separación, hacer que el código sea más testeable o navegable por IA, o cuando otra habilidad necesite el vocabulario de módulos profundos.
designdevelopmentcode-review
code-review
mattpocock
Revisa los cambios desde un punto fijo (commit, rama, etiqueta o merge-base) en dos ejes: Estándares (¿el código sigue los estándares de codificación documentados de este repositorio?) y Especificación (¿el código coincide con lo solicitado en el issue/PRD original?). Ejecuta ambas revisiones en subagentes paralelos y las reporta lado a lado. Úsalo cuando el usuario quiera revisar una rama, un PR, cambios en progreso, o pida "revisar desde X".
testingdevelopmentcode-review
design-an-interface
mattpocock
Genera múltiples diseños de interfaz radicalmente diferentes para un módulo utilizando subagentes paralelos. Úsalo cuando el usuario quiera diseñar una API, explorar opciones de interfaz, comparar formas de módulo o mencione "diseñarlo dos veces".
developmentdesignapi
diagnosing-bugs
mattpocock
Bucle de diagnóstico para errores difíciles y regresiones de rendimiento. Úsalo cuando el usuario diga "diagnostica"/"depura esto", o reporte algo roto/lanzando excepciones/fallando/lento.
testingdevelopmentcode-review
domain-modeling
mattpocock
Construir y afinar el modelo de dominio de un proyecto. Usar cuando el usuario quiera definir terminología del dominio o un lenguaje ubicuo, registrar una decisión arquitectónica, o cuando otra habilidad necesite mantener el modelo de dominio.
designdevelopmentdocument