ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
@yonatangrossInstall SkillDevelopment
Skill
/ork-brainstorm
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill ork-brainstorm --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill ork-brainstorm -a windsurf -y
SKILL.md
ork-brainstorm.SKILL.mdname: ork-brainstorm
description: Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
Ork Brainstorm
Frame the outcome, constraints, non-goals, and decision deadline. Inspect the relevant repository and existing decisions before proposing options.
Generate two to four materially different approaches. For each, state the implementation shape, benefits, costs, risks, dependencies, reversibility, and the evidence that would disprove it. Do not pad the list with cosmetic variations.
When an option depends on what a library, framework, or service can actually do today, confirm it with the context7 MCP server (`resolve-library-id`, then `query-docs`) before scoring it. An option built on a capability you only remember is an assumption, and it belongs in the unresolved list.
Use one context for a normal decision. Delegate only when there are at least three independent unknowns; give each subagent one bounded question and synthesize its evidence. Prefer the installed `ork_explorer` role when available, otherwise use Codex's built-in `explorer` role.
End with a recommendation, the decision rationale, unresolved assumptions, and the smallest next action. Do not edit files until the user asks to implement the chosen approach.
Read more
name: ork-brainstorm description: Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
Ork Brainstorm
Frame the outcome, constraints, non-goals, and decision deadline. Inspect the relevant repository and existing decisions before proposing options.
Generate two to four materially different approaches. For each, state the implementation shape, benefits, costs, risks, dependencies, reversibility, and the evidence that would disprove it. Do not pad the list with cosmetic variations.
When an option depends on what a library, framework, or service can actually do today, confirm it with the context7 MCP server (`resolve-library-id`, then `query-docs`) before scoring it. An option built on a capability you only remember is an assumption, and it belongs in the unresolved list.
Use one context for a normal decision. Delegate only when there are at least three independent unknowns; give each subagent one bounded question and synthesize its evidence. Prefer the installed `ork_explorer` role when available, otherwise use Codex's built-in `explorer` role.
End with a recommendation, the decision rationale, unresolved assumptions, and the smallest next action. Do not edit files until the user asks to implement the chosen approach.
Stats
301
Stars
40
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withorchestkit
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
301122 skills36 agents
Stars on GitHub
Momentum
- stars in total
- 301
Other skills on orchestkit.
@yonatangrossInstall Skillork-explore
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request…
@yonatangrossInstall Skillork-glyph
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
@yonatangrossInstall Skillork-implement
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a…
@yonatangrossInstall Skillork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
@yonatangrossInstall Skillork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to…
@yonatangrossInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about ork-brainstorm.
- Which coding agents can use ork-brainstorm?
- ork-brainstorm installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.