mcpField
I
implement

implement

github.com/gabriel-lafranceDevelopment069 installsUpdated 1d ago
Repository

About implement

implement is a worker skill for bounded code changes dispatched through /task or /just-do-it. It defines repository-reading, architecture, scope, testing, and handoff rules while directing UI work to /design.

Key features

  1. 01Bounded implementation slices
  2. 02Repository and architecture checks
  3. 03Write-allowlist enforcement
  4. 04Completion and escalation format

Use cases

  1. 01Implementing a scoped task from a parent brief
  2. 02Blocking UI changes for /design
  3. 03Reporting missing decisions or dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gabriel-lafrance/skills --skill implement

After installing, type/implementin Claude Code to confirm it loaded.

Details

From the project README

Implement

Must read: ../pack-shared/standards.md. Apply the Taste and Architecture sections of AGENTS.md this turn before writing code. Do not skip.

Ask style: ../pack-shared/asking.md

This skill is a worker step for /task or /just-do-it, not a typical user start. You own how. The parent sends what and need-to-know, not a recipe.

User-facing UI is /design. If this brief's write allowlist is screens, components, styling, or visible copy, return blocked and tell the parent to dispatch /design instead.

Use the shared execution context. The parent sends a complete Worker Brief in chat; do not reconstruct intent from a workspace, plan, or agent-owned state. Fail the job if taste or architecture bars are skipped.

Read first

  1. The Taste and Architecture sections of AGENTS.md (keep it simple, named principles, and structure). Do not implement user-facing UI here (/design owns that).
  2. The inline outcome, Done when, non-goals, Ticket / PR, fixed point, locked decisions, Active Rules, current slice, write lane, and dependencies.
  3. Only the named ticket / PR, relevant Git diff/history, repository code and rules, and repo paths listed in the brief.

Deliver one bounded slice

  1. Stay in the write allowlist. Parallel work is safe only when the parent brief proves non-overlapping lanes and compatible interfaces.
  2. Honor the inline Structure decisions and Active Rules. Create the owning folder from the folder map before writing files (architecture:folders). Do not add new files as mixed siblings in src/, app/, convex/, or any other mixed parent. If a required behavior-preserving move is in the brief, do it before feature code and show that the old observable behavior still holds. Apply the Taste checklist and the Architecture self-check in AGENTS.md before Completion.
  3. Reuse existing services and primitives. Do not copy a known-wrong shape or invent a shared API, service, abstraction, or lane. Return the smallest viable option as a finding when the slice needs one. Before adding an environment variable, inventory existing names and jobs (taste:reuse-env). If SITE_URL already holds the public site URL, read it; do not create FRONTEND_URL.
  4. Gather only slice-local evidence needed for Completion: existing terminal output first, then a narrow relevant command if needed.
  5. Do not run acceptance evidence or /code-review; the parent integrates Completion reports and owns those gates. Do not update tickets, registries, status, or other agent bookkeeping.
  6. Do not write or edit tests. Only /create-test writes tests (always via tester), and only after the user starts it.

Completion

End with only the ## Completion envelope: status, scope, evidence, Taste / architecture: applied, findings, and handoff. Skip on that mark is a fail. Do not append Progress, workspace status, or a validation/review report.

Escalation

If acceptance, dependencies, behavior, or a structural decision is missing, return blocked with the smallest decision or interface the parent must provide. The parent updates the inline context or asks the user; the worker does not create a plan or hidden artifact.

Comments

Markdown supported