JetBrains

Build a draft specification graph for an existing codebase that has no specs. Survey its guidance files, documentation, manifests, and code; infer project purpose and module boundaries, adopt suitable existing design documents, and validate the resulting graph for review.

• Creating initial specs for an undocumented codebase
• Mapping modules and their dependencies
• Turning existing architecture documents into specs

Guides agents in drafting concise, reliable product and technical specifications. It keeps settled decisions and rationale in the right document, marks unconfirmed inferences, and defines how goal-and-requirements documents should describe capabilities, non-goals, and durable principles.

• Drafting a product goal and requirements document
• Recording architecture or module boundaries
• Revising a spec after a product decision changes

Use this checklist to create or revise a workflow skill in the ThinkRail workflow package. It guides decisions about the skill’s role, trigger, structure, routing, and handoff, and helps check that the workflow family’s rules are followed.

• Adding a workflow skill to the package
• Changing a skill’s role or handoff
• Reviewing workflow skills against system rules

Manage MCP server settings in ThinkRail when servers need to be added, changed, enabled, or troubleshot. It explains user and repository configuration, safe credential references, approval and sign-in steps, and how to load deferred tools.

• Adding or removing an MCP server
• Changing server settings or exposure
• Troubleshooting missing or failing MCP tools

Routes project setup to the appropriate workflow by checking whether specs and source code already exist. It sends an empty workspace with a new idea toward a requirements document, or an existing codebase toward an initial spec graph, and offers review when specs are already present.

• Setting up a project with no existing specifications
• Routing a new idea to a requirements workflow
• Preparing initial specs for an existing codebase

Turns a raw project idea in an empty workspace into a reviewed `goal-and-requirements.md`. The workflow infers a suitable document shape, confirms key decisions with the user, records settled sections incrementally, and can optionally research alternatives before final review.

• Turning an initial idea into product requirements
• Creating a lightweight personal project brief
• Drafting a PRD for a product with named users

Clarify the product goal and technical choices before a feature, behavior change, or bug fix is built. The workflow records an agreed task specification, guides implementation against it, and updates durable project specs when the work lands.

• Clarifying goals before building a feature
• Agreeing on behavior changes before coding
• Investigating and planning a bug fix

Find and maintain project specs that record architecture, decisions, contracts, and boundaries. Use the graph and search tools to locate relevant guidance, align changes with it, update specs when decisions change, and validate links and structure.

• Finding specs that govern a code change
• Understanding module boundaries and contracts
• Recording an architecture decision in a spec

Route new project setup, pull request lifecycle work, and product changes such as features or bug fixes to the workflow that governs them. It also identifies when a request needs no workflow, so routine questions and nonbehavioral edits can proceed directly.

• Choosing a workflow for a new project
• Routing a feature or bug fix
• Handling pull request checks or review feedback

Create and maintain pull requests for finished work. The workflow can sync a branch, update PR details or screenshots, report checks, monitor CI when asked, and address review comments while confirming the latest Git and GitHub state.

• Opening a pull request for finished changes
• Syncing a PR branch with its base
• Updating a PR title, body, or screenshots

Helps an agent ask focused questions when a workflow needs user decisions. It groups independent questions into rounds, frames choices as visible outcomes, and explains how to continue when answers are skipped or interactive questions are unavailable.

• Gathering scope and behavior decisions for a feature
• Clarifying choices that depend on earlier answers
• Confirming an inference with clear options

Organize substantial requests into a shared, chat-scoped task plan. Track actionable steps and their status in the user-visible Todo panel, keep the plan in sync with user edits, and provide a concise handoff summary when the work is complete.

• Planning a task with several execution steps
• Tracking progress on shared work
• Picking up a pending TODO item