# Implement > Implement a piece of work based on a spec or set of tickets. - Skill: `fellipeutaka/implement` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add fellipeutaka/implement` - Raw SKILL.md: https://api.skillmd.com/api/skills/fellipeutaka/implement/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: fellipeutaka (https://skillmd.com/u/fellipeutaka) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/fellipeutaka/implement --- Implement the work described by the user in the spec or tickets. The main agent is the **orchestrator**. It owns the preflight, branch and worktree state, integration, validation, independent review, and delivery. An **implementer subagent** owns the code for one ticket in one isolated context. ## Process ### 1. Pin the work Read the complete ticket or spec, identify its acceptance criteria and pre-agreed test seams, and choose the delivery mode below. Record the fixed point for review: the immediate parent branch for a stack, the integration branch for a child ticket, or the trunk/explicit parent for standalone work. If the seams are not settled, ask the user before dispatching implementation. This step is complete when the scope, seams, blockers, fixed point, target branch, and target worktree are all explicit. ### 2. Delegate implementation For any ticket that crosses more than one layer, changes more than one file, or would benefit from a fresh context, dispatch one implementer subagent using the brief in [IMPLEMENTER-BRIEF.md](IMPLEMENTER-BRIEF.md). A tiny, isolated edit can stay in the orchestrator context. Give each subagent its own context and worktree. Dispatch independent frontier tickets in parallel, one worktree per ticket; wait for a blocker before dispatching a dependent ticket. The orchestrator never lets two agents edit the same worktree or branch concurrently. The implementer subagent calls the Skill tool with "tdd" at the pre-agreed seams, typechecks regularly, runs focused tests during the loop, runs the full suite once, and commits only to its implementation branch. It returns the commit, changed files, checks, and any blocker. It does not choose delivery topology or review its own work. If the harness has no isolated subagent or worktree capability, execute the same brief in the orchestrator context and record that fallback in the final report. This step is complete when every dispatched ticket has either returned a verifiable commit and report or has been completed through the documented local fallback. ### 3. Review independently Inspect the implementation diff and run the relevant checks before reading the implementer's narrative. Check out the returned implementation branch at its commit in the reviewer context or worktree, then call the Skill tool with "code-review" against the fixed point. Verify that `git diff ...` is non-empty before review. The review must run after the implementation commit and in a clean reviewer context or worktree where the harness supports it. The orchestrator classifies every finding as resolved, deferred with a reason, or blocking. Fix blocking findings in the orchestrator or a distinct repair subagent, rerun the affected checks, and repeat the review after material fixes. The implementer report is evidence about what was attempted, not acceptance of the result. This step is complete when the diff satisfies the ticket's acceptance criteria, the relevant checks pass, and no blocking review finding remains. ### 4. Deliver Continue with the selected delivery mode below. The orchestrator owns the final Git history, branch/PR operations, merges, and the final report; the implementer subagent only supplies the committed implementation. ## Delivery mode Choose the delivery mode from the user's instruction, the repository's `AGENTS.md`, or the current branch state. Do not infer stacked or integration delivery merely because a feature has multiple tickets. ### Standalone delivery Use standalone delivery by default when no stack has been requested: 1. Prepare a new branch named `feat/implement-` and assign its worktree to the implementer subagent. 2. After independent review, push the branch and create a pull request against the appropriate trunk or parent branch, closing the ticket or spec. ### Stacked delivery Use stacked delivery when the user requests it or the repository explicitly enables it for the current flow. Use the `gh-stack` skill's commands as the operational reference. Before writing code: 1. Read the full ticket and verify that its real blockers are complete or that the requested parent branch already contains them. 2. Confirm the worktree is clean. 3. Run `gh stack view --json` to inspect the current stack. If it reports that the branch is not in a stack, initialize or continue with standalone delivery as appropriate. If the existing implementation branch already has a PR, adopt it with `gh stack init ` rather than recreating the branch or PR. 4. Plan the layer against the immediate parent. A ticket dependency graph can contain forks and joins; `gh-stack` is strictly linear. Do not append a sibling or join ticket to a stack unless serializing that work is an intentional decision. Create and navigate branches with `gh stack`: - For the first layer, use `gh stack init feat/implement-`. - For each subsequent layer, use `gh stack add feat/implement-` while checked out on the stack top. - Use standard `git add` and `git commit` for deliberate staging; do not use `git switch -c` for a stacked layer. The implementation, TDD loop, typechecking, full test suite, and independent review requirements are the same in both modes. In stacked mode, review the diff against the immediate parent branch, not against the trunk, so the review matches the PR's incremental change. At the end of a stacked layer: 1. Include `Closes #` in the commit body or edit the generated PR body afterwards. `gh stack submit --auto` derives PR metadata from commits. 2. Run `gh stack submit --auto --open` to push the stack and create or synchronize ready-for-review PRs. 3. Run `gh stack view --json` and report the resulting stack and PR URLs. Use `gh stack sync --prune` after merges and `gh stack merge --yes` when the entire approved stack should be merged. Do not use `gh pr merge` for a stacked PR. ### Integration delivery Use integration delivery for a multi-ticket spec or PRD whose approved dependency graph has forks or joins and whose merge policy requires one final pull request into the trunk. This is different from a `gh-stack`: the integration branch is a shared feature branch, not a linear stack. The shape is: ```text trunk └── integration/ → final PR to trunk (Closes #) ├── ticket-a → PR to integration/ ├── ticket-b → PR to integration/ └── ticket-c → PR to integration/ ``` Before writing code: 1. Read the full ticket and verify that its real blockers are already merged into the integration branch. A blocker PR being open is not enough. 2. Confirm the worktree is clean and use a separate worktree for each ticket that will be developed in parallel. 3. Create or check out the durable `integration/` branch from the updated trunk. Open one draft integration PR from that branch to the trunk before or alongside the child PRs. 4. Create each ticket branch from the latest integration branch and target the child PR at the integration branch, never at the trunk. At the end of an integration-delivery ticket: 1. Include `Refs #` in the child PR body. The final integration PR is responsible for `Closes #` and may close any child tickets that are still open. 2. Push the ticket branch and create or update a normal PR whose base is `integration/`. 3. After the child PR is merged into the integration branch, rebase or recreate dependent ticket branches from the updated integration branch before continuing. 4. Do not merge a child PR directly into the trunk. Only the final integration PR is merged into the trunk. Use the repository's normal PR merge policy for child PRs and the final PR; `gh-stack` is optional for any strictly linear sub-chain inside the larger integration effort. Each implementation still starts in a fresh context when the ticket flow calls for it. The stack is durable repository/GitHub state, so the new context must perform the stack preflight above instead of relying on conversation memory.