ork-implement

Solid

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.

AI & Automation 229 stars 25 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
79
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
36
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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.

Details

Author
yonatangross
Repository
yonatangross/orchestkit
Created
8 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Anthropic · AI LangChain · AI FastAPI · Backend Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ork-assess

Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution.

229 Updated today
yonatangross
AI & Automation Listed

implement

Use for an approved software change through verified implementation, independent review, bounded repair, and user acceptance. Not for unsettled scope, diagnosis-only, read-only review, or release.

1 Updated yesterday
mblauberg
AI & Automation Listed

feature-implementer

Implements approved tasks against specs, ADRs, and plans with minimal diffs and verified commands. Use only after planning/validation (or lite path for chores). Emits IMPL_REPORT. Never redesigns architecture, adds unrelated refactors, or self-certifies without running available checks.

0 Updated 1 months ago
willianbs