Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add yonatangross/orchestkit --skill ork-implement --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ork Implement?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yonatangross-ork-implement)More formats (shields.io, HTML) on the badges page.
---
name: ork-implement
description: Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.
---
# Ork Implement
Implement only the agreed scope. Read repository instructions first and use an isolated worktree whenever a shared primary checkout may be active.
Before writing against an unfamiliar third-party API, confirm its current surface through the context7 MCP server (call `resolve-library-id`, then `query-docs`) rather than recalling it.
Keep the diff small. Add focused tests when behavior changes, and report the exact verification output. Do not self-certify a high-impact change: request `$ork-verify` (or `ork_verifier` when installed) after implementation.
Prefer `ork_implementer` when installed; otherwise implement in this context. Delegate only independent, bounded units; keep integration in one place.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
