Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture.
Install Choosing A Workflow
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/thinkrail choosing-a-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .claude/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .claude/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/thinkrail choosing-a-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .agents/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .agents/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/thinkrail choosing-a-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .cursor/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .cursor/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JetBrains/thinkrail.git --path packages/pi-thinkrail-workflow/skills/choosing-a-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/thinkrail choosing-a-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .gemini/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .gemini/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JetBrains/thinkrail choosing-a-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .github/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .github/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/thinkrail choosing-a-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/thinkrail.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/pi-thinkrail-workflow/skills/choosing-a-workflow .opencode/skills/choosing-a-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "choosing-a-workflow" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/choosing-a-workflow into .opencode/skills/choosing-a-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "choosing-a-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
choosing-a-workflow- GitHub stars
- 513
- Token cost
- ~781 tokens
- SKILL.md length
- 394 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture.
- Works in 3 steps: Is this project onboarding? No spec… → Is this the PR lifecycle? Finished work… → Does the work require a product or…
- Development work in your project
- SKILL.md covers Classify, Route, Red flags — stop and re-route and Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Choosing A Workflow is an agent skill from JetBrains/thinkrail, published by the product's own GitHub organization. Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or localized fully specified work.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Vibe code with pi in a lightweight, real IDE that customises itself around the way you work — The Vibe You Need. The licence is Apache-2.0.
When your agent uses it
- Development work in your project
Example prompts
- “/choosing-a-workflow”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Is this project onboarding? No spec graph yet — an empty or effectively empty workspace where
- Is this the PR lifecycle? Finished work shipping as a pull request, or an existing PR being
- Does the work require a product or design choice? The request leaves scope, user-visible
What it can do on your machine
Read from SKILL.md and the folder at commit 68bb837. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Choosing A Workflow loads about 781 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 394 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JetBrains/thinkrail at commit 68bb837, republished under its Apache-2.0 licence (© JetBrains). 394 words, ~781 tokens.
Download SKILL.mdSave it as
.claude/skills/choosing-a-workflow/SKILL.md (or your agent's skills folder).- name
- choosing-a-workflow
- description
- Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or localized fully specified work.
Choosing a Workflow
The root router of the workflow family in packages/pi-thinkrail-workflow. It classifies new
workflow-eligible work and names the workflow skill that governs it — nothing more. Work already routed
resumes its active workflow instead. A routed skill's steps live in that skill alone; read it, don't run
it from memory.
Classify
For a new piece of work, read the request and use what is already known to answer three questions:
- Is this project onboarding? No spec graph yet — an empty or effectively empty workspace where the user brings a raw idea, or an existing codebase being set up or specced for the first time.
- Is this the PR lifecycle? Finished work shipping as a pull request, or an existing PR being tended — created, brought up to date, given screenshots, its checks watched, or its review comments addressed. Fixes that flow from a PR's own review comments belong here.
- Does the work require a product or design choice? The request leaves scope, user-visible behavior, or architecture to decide before implementation.
If none applies, no workflow is needed: proceed directly without a workflow announcement. A fully specified fix, mechanical refactor, documentation or configuration-only change, question, explanation, or check normally belongs here.
If the route is genuinely ambiguous from the request alone, ask one short clarifying question
(ask_user_question, composed per the asking-user-questions concept skill) rather than guessing.
Show full SKILL.md (166 more words)Show less
Route
| Classification | Route |
|---|---|
| Project onboarding — no spec graph yet | Read and follow setting-up-a-project |
| PR lifecycle work | Read and follow shipping-a-pr |
| A change requiring a product or design choice | Read and follow brainstorming |
| None of the above | No matching workflow; proceed directly without announcing the routing result |
One route per piece of work. If a request bundles unfinished implementation with PR work, route the implementation first and return to shipping-a-pr only after it lands.
Red flags — stop and re-route
- You started implementation while a required product or architecture choice is still unresolved.
- You loaded brainstorming for work whose observable result and implementation constraints are already specified.
- You re-entered this router while continuing work already assigned to a workflow.
- You are following a routed skill's steps from memory instead of reading that skill.
Handoff
This skill ends by naming exactly one of: setting-up-a-project, shipping-a-pr, brainstorming, or no matching workflow (proceed directly). Adding a workflow to the family adds a row to the table above — see the writing-workflow-skills skill.
© JetBrains, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/pi-thinkrail-workflow/skills/choosing-a-workflow of JetBrains/thinkrail.
Open the folder on GitHubat commit 68bb837
Compare with similar skills
Choosing A Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Choosing A Workflow this skillJetBrains/thinkrail | 513 | — | ~781 | Automated safety check: Pass | Apache-2.0 | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Openspec Verify ChangeFission-AI/OpenSpec | 71k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Warp Factory Fileswarpdotdev/warp | 65k | 1 repos | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Openspec Verify Change
Fission-AI/OpenSpec
Verify implementation matches OpenSpec change artifacts. An agent skill from Fission-AI/OpenSpec.
Warp Factory Files
warpdotdev/warp
Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Analyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
- Official
GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
More from JetBrains/thinkrail
All 11 skills in this repo- Official
Importing A Codebase
JetBrains/thinkrail
A skill your agent uses when asked to create the initial spec graph for an existing codebase that has source code but no specs.
- Official
Starting A New Project
JetBrains/thinkrail
A skill your agent uses when the workspace is empty, has no code, and the user brings a raw project idea.
- Official
Asking User Questions
JetBrains/thinkrail
A skill your agent uses when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step.
- Official
Setting Up A Project
JetBrains/thinkrail
A skill your agent uses when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card.
- Official
Shipping A PR
JetBrains/thinkrail
A skill your agent uses when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR.
- Official
Spec Graph
JetBrains/thinkrail
A skill your agent uses when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or…
Related
Categories
Questions about Choosing A Workflow
What does Choosing A Workflow do?
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Choosing A Workflow is an agent skill from JetBrains/thinkrail, published by the product's own GitHub organization. Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture.
When should I use Choosing A Workflow?
Choosing A Workflow fits situations like: development work in your project.
How do I install Choosing A Workflow in Claude Code?
Run `npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a claude-code`. Or copy the skill folder (packages/pi-thinkrail-workflow/skills/choosing-a-workflow in JetBrains/thinkrail) into .claude/skills/choosing-a-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Choosing A Workflow in Codex?
Run `npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a codex`. Or copy the skill folder (packages/pi-thinkrail-workflow/skills/choosing-a-workflow in JetBrains/thinkrail) into .agents/skills/choosing-a-workflow in your project. Codex loads it when a task matches its description.
Can I use Choosing A Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetBrains/thinkrail --skill choosing-a-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/choosing-a-workflow, .gemini/skills/choosing-a-workflow, .github/skills/choosing-a-workflow and .opencode/skills/choosing-a-workflow in your project.
What does Choosing A Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Choosing A Workflow is instructions for the agent only.
Does Choosing A Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Choosing A Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Choosing A Workflow use?
Choosing A Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Choosing A Workflow use?
About 781 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Choosing A Workflow?
Skills that share tags, products or a category with Choosing A Workflow: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Openspec Verify Change (Fission-AI/OpenSpec, 71k stars), Warp Factory Files (warpdotdev/warp, 65k stars) and Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Choosing A Workflow?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/thinkrail, which has 513 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 2026.
Source: JetBrains/thinkrail on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.