# Implement

> Implements a scoped code change with inspect-report-verify discipline. Use when the user asks to implement, build, add, fix, or create something; or says /implement. Not for question-only, plan-only, or unexplained-failure debugging.

- Skill: `axidify/implement` (Agent Skill)
- Install (CLI): `npx skillmds@latest add axidify/implement`
- Raw SKILL.md: https://api.skillmd.com/api/skills/axidify/implement/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: Axidify (https://skillmd.com/u/axidify)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/axidify/implement

---


# Implement

**Not this skill:** unexplained errors, regressions, or “why does X fail?” with no
clear fix yet → **debug**. New features with unclear design →
**plan** first. Multi-phase work from `docs/plans/*.md` → **plan-driven-implementation**.

## Checklist

1. **Discover** — if needed, run **discover-project**; read relevant agent rules
2. **Inspect** — find current behavior and all affected files
3. **Report** — summarize state, gaps, and planned diff **before** large edits
4. **Implement** — minimal change that meets the request; match existing style
5. **Verify** — run lint, typecheck, and tests the project defines (discover from
   `package.json`, Makefile, CI, or linter configs — eslint, ruff, clippy, etc.)
6. **Report** — files changed, what changed, limitations, anything not done

For large multi-area work, explore with subagents/Task first, then implement in
focused passes.

## Error rules

| Situation | Action |
|-----------|--------|
| Build / typecheck fails from your changes | Fix before finishing |
| Tests fail from your changes | Fix |
| Tests fail unrelated | Report; do not “fix” opportunistically |
| Runtime error while verifying | Use **debug**, then return here |

## Scope

- No drive-by refactors or unrelated files
- No commits unless the user asked to commit
- Questions (`?`, “how does”, “should we”) → answer only; do not implement until approved

## Related skills

- **test** — run after verify when tests apply
- **review** — three-pass review before commit or PR
- **security** / **performance** — deep pass when those risks dominate
- **debug** — unexplained failures during verify
- **plan-driven-implementation** — phased work tracked in `docs/plans/`
- **web-design-engineer** — design-led UI in-repo (then return here for minimal diff)