ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
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.
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill ork-implement --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill ork-implement -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill ork-implement -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill ork-implement -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill ork-implement -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill ork-implement -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill ork-implement -a windsurf -y
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.
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.
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request…
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request…
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.