implementation — Claude Code skill: what it does, how to install
Guides the agent to write production-ready code following existing patterns, handle errors, and avoid scope creep before verification.
npx skills add cyrusagents/cyrus --skill implementation -a claude-codeWhat implementation does
This skill sets concrete boundaries for drafting production code in Claude Code and supported IDEs. The agent inspects existing repository patterns and matches them closely. It ignores unrelated cleanup. Edits remain strictly focused on the requested scope.
Workflow progression is explicit. When automated tests fail, the model must fix them immediately instead of advancing to subsequent tasks. Testing strategy leans on verify-and-ship. The agent runs relevant existing tests or direct checks, reserving fresh tests exclusively for consequential regressions worth long-term maintenance.
Because the instructions explicitly route output to a verification and shipping phase, using this skill outside the broader Cyrus workflow requires handling the next handoff step on your own.
What it helps with
- implement requested changes without drifting into unrelated refactoring
- preserve existing repository patterns and conventions
- handle edge cases and runtime failure scenarios
- prepare code for the
verify-and-shipworkflow step - resolve failing tests before proceeding to the shipping phase
Example prompts for the agent
- Implement the requested feature changes while following our existing code style
- Handle edge cases in this data parser without touching unrelated modules
- Add the new calculation logic and ensure all current tests pass before shipping
How to install implementation
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill implementation -a claude-code2Manually: put the files in place
~/.claude/skills/implementation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/implementation/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill implementation -a codex2Manually: put the files in place
.agents/skills/implementation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill implementation -a cursor2Manually: put the files in place
.cursor/skills/implementation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cyrusagents/cyrus implementation2Manually: put the files in place
.github/skills/implementation/SKILL.md1Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill implementation -a gemini-cli2Platform CLI
gemini skills install https://github.com/cyrusagents/cyrus --path skills/implementationManually: put the files in place
.devin/skills/implementation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cyrusagents/cyrus --skill implementation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about implementation
How to install implementation in Claude Code?
Run npx skills add cyrusagents/cyrus --skill implementation -a claude-code in your terminal.
What does the implementation skill do?
It instructs the agent to write production-ready code matching project conventions, handle errors properly, and avoid modifying unrelated code.
Does the skill require writing new tests for every change?
No, it instructs the agent to rely on existing tests or direct checks. New tests are only written for consequential regressions worth maintaining over time.
Source text
SKILL.md · Apache-2.0
--- name: implementation description: Implement the requested changes. Write production-ready code, follow existing patterns, and use proportionate verification. --- # Implementation Implement the requested changes: - Write production-ready code that follows existing patterns and conventions - Choose verification using `verify-and-ship`: use relevant existing tests or direct checks; add new tests only for concrete consequential regressions worth maintaining - Handle edge cases and error scenarios appropriately - Keep changes focused on what was requested — avoid unrelated improvements If tests fail, fix them before moving on to the next phase of the workflow. When implementation is complete, proceed to the verification and shipping phase.
© cyrusagents · Apache-2.0 · cyrusagents/cyrus