Index of every page on this site: llms.txt
All skills
jetbrains avatar

/choosing-a-workflow

@e85862d
by jetbrainsjetbrains/thinkrail8.4k stars
532
Run it yourself

Use at the start of new project onboarding, PR lifecycle work including PR checks, or any change to what the product does — a feature, a behavior change, or a bug fix. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or edits that change no behavior.

  • 1 file
  • 3.3 KB
  • Updated 4 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jetbrains/thinkrail/choosing-a-workflow

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈80 tokens for metadata: the name and description. ≈748 when used: this file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈317 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Choosing a Workflow

The root router of the workflow family. 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:

  1. 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.
  2. 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.
  3. Does the work change what the product does? A new feature, a change in behavior, or a bug fix — however small, and even when the request already spells out the design. A detailed request shortens the interview; it never skips it.

If none applies, no workflow is needed: proceed directly without a workflow announcement. Only work that changes no behavior belongs here: a non-PR question, explanation, or check; a typo, documentation, or configuration-only edit; a mechanical refactor such as a rename.

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.

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 feature, behavior change, or bug fix 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 implementing a feature, behavior change, or bug fix without going through brainstorming.
  • "It's small" or "the request is already specific" — neither is a reason to skip; the workflow scales down, it does not switch off.
  • You loaded brainstorming for work that changes no behavior (a rename, a typo, a question).
  • 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at e85862d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 4 weeks ago

README badge

README badge for jetbrains/thinkrail/choosing-a-workflow