implementer
Skill2 starsChanged 9 days agoMITView on GitHub
Execution agent skill focused on implementing changes based on an approved Blueprint. Use this skill when implementing targeted, atomic code changes once the plan is solid — even if they just say "implement this" or "make the changes". Gated by human or primary agent approval of the implementation strategy.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- gopalparashar421/agent-skillstheir own version, first seen Nov 8, 2026
- kcayme/k-agentstheir own version, first seen Nov 1, 2026
- karim-bhalwani/agent-skills-collectiontheir own version, first seen Oct 20, 2026
- HuntercodeT/dsh-stafftheir own version, first seen Oct 20, 2026
- Nemikolh/devsandboxestheir own version, first seen Oct 13, 2026
- alphazede/bearing-litetheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- keli-wen/agy-staff★ 828same name
- Nemikolh/devsandboxes★ 5same name
- alphazede/bearing-lite★ 3same name
- gopalparashar421/agent-skills★ 2same name
- GaaamJ/simple★ 0same name
- HuntercodeT/dsh-staff★ 0same name
- karim-bhalwani/agent-skills-collection★ 0same name
- karim-bhalwani/agentic-harness★ 0same name
- kcayme/k-agents★ 0same name
- smitshivalkar-spectims4567/hsj-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/avoid-ai-writing/AGENTS.mdAGENTS.md
- .agents/skills/do-web-doc-resolver/AGENTS.mdAGENTS.md
- .agents/skills/skill-evaluator/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibility-auditorSkill
- agent-browserSkill
- agentic-abstentionSkill
- agents-mdSkill
- api-design-firstSkill
- architecture-diagramSkill
- avoid-ai-writingSkill
- cicd-pipelineSkill
- cloudflare-worker-apiSkill
- codacySkill
- codeberg-apiSkill
- code-review-assistantSkill
- css-render-performanceSkill
- database-devopsSkill
- debuggerSkill
- delegateSkill
- dependency-upgradesSkill
- dist-channel-selectionSkill
- docs-hookSkill
- document-rendering-and-locatorsSkill
- dogfoodSkill
- dora-reportSkill
- do-web-doc-resolverSkill
- durable-objectsSkill
- eu-ai-act-complianceSkill
- git-github-workflowSkill
- goap-agentSkill
- intent-classifierSkill
- iterative-refinementSkill
- jules-delegatorSkill
- learnSkill
- lifecycle-managementSkill
- local-context-sanitizationSkill
- memory-contextSkill
- migration-refactoringSkill
- nested-build-isolationSkill
- privacy-firstSkill
- progressive-deliverySkill
- pwa-offline-syncSkill
- reader-ui-uxSkill
- readme-best-practicesSkill
- secrets-managementSkill
- secure-invite-and-accessSkill
- security-code-auditorSkill
- shell-script-qualitySkill
- skill-creatorSkill
- skill-evaluatorSkill
- static-analysisSkill
- testing-strategySkill
- test-runnerSkill
- triz-solverSkill
- turso-dbSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Before making any changes, verify the Blueprint (ADR) exists and includes:
- Distinctive: line 33
If the Blueprint is missing or incomplete, stop and request it before proceeding.
- Distinctive: line 37
Blueprint Check: Verify that a clear implementation strategy (ADR) with TRIZ analysis exists.
- Distinctive: line 39
Verification: Run tests and the quality gate after each atomic change.
- Distinctive: line 54
Never bundle unrelated changes in a single commit — if the quality gate fails, you can't tell which change caused it.
- Distinctive: line 55
If the Blueprint says "modify files X, Y, Z" but you find a better approach mid-implementation, update the Blueprint first rather than …
- Distinctive: line 56
Run the quality gate locally before pushing — CI failures are expensive to diagnose remotely.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implementer Skill
The Implementer skill is an execution-focused tier responsible for making atomic, high-quality code changes.
When to Use
- Implementing features based on a solid technical specification
- Applying identified bug fixes
- Executing planned refactoring tasks
- Ensuring all changes pass quality gates and tests
- Even if they just say "implement this" or "make the changes"
Blueprint Validation
Before making any changes, verify the Blueprint (ADR) exists and includes:
- Clear problem statement
- Proposed solution with specific files to modify
- TRIZ contradiction analysis (if applicable)
- Success criteria and test plan
- Rollback strategy
If the Blueprint is missing or incomplete, stop and request it before proceeding.
Workflow
- Blueprint Check: Verify that a clear implementation strategy (ADR) with TRIZ analysis exists.
- Atomic Edits: Apply changes one concern at a time. Each edit should be independently committable.
- Verification: Run tests and the quality gate after each atomic change.
Atomic Edit Pattern
1. Identify the single concern to change
2. Make the edit
3. Run: ./scripts/quality_gate.sh
4. If pass → commit with conventional format
5. If fail → fix, re-run quality gate, then commit
6. Move to next concernGotchas
- Never bundle unrelated changes in a single commit — if the quality gate fails, you can't tell which change caused it.
- If the Blueprint says "modify files X, Y, Z" but you find a better approach mid-implementation, update the Blueprint first rather than deviating silently.
- Run the quality gate locally before pushing — CI failures are expensive to diagnose remotely.
Rationalizations
| Rationalization | Reality |
| "I'll just fix it now" | Skipping the Blueprint phase leads to scope creep and architectural regressions. |
| "The change is obvious, no need for a Blueprint" | Obvious changes still need atomic edits and quality gate verification. |
Red Flags
- Making non-atomic changes that touch multiple unrelated areas
- Committing code without running the required quality gate
- Deviating from the Blueprint without updating it first
- Skipping the Blueprint Check step because "it's a small change"
See Also
delegate— Context retrieval before implementationgoap-agent— Orchestrator that assigns implementer tasks
Voice & Context
- Default:
professional+blog - Reference:
voice-profilesskill for definitions and auto-detection.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

