- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add JetBrains/thinkrail --skill spec-graph -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add JetBrains/thinkrail --skill spec-graph -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add JetBrains/thinkrail --skill spec-graph -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add JetBrains/thinkrail --skill spec-graph -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/JetBrains/thinkrail/tree/HEAD/packages/spec-graph/skills/spec-graphDo publicador
spec_search / spec_grep / spec_get / spec_graph to find the applicable record and align with it. If a change contradicts a recorded
decision, surface and reconcile the contradiction rather than silently diverging.foo.ts with "the foo tool" is noise, so say it in a sentence instead.id rather than restate
it. If a paragraph is being copied between specs, move it to the spec that owns the concept and point at
it. Duplicated prose drifts and turns into contradictions.parent links form a hierarchy that mirrors the code structure: a SPEC.md sits beside the module it
describes (fractal — a package and its sub-directories each have one), and root documents sit at the
repository root.depends-on, references, and implements form a dependency layer across the tree.id (a unique slug), type, title.status (lifecycle), parent (single link), depends-on / references / implements
(link lists), covers, tags.id and type.status tracks a spec's lifecycle: draft (being written) → active (in force), then stale (drifting
from the code), done, or deprecated. It's optional, but keep it current as a spec firms up or ages.goal-and-requirements — the product goal and scope; the root of the graph.architecture-design — system-wide topology, cross-cutting decisions, and invariants.module-design — a package or module's responsibility and boundary.submodule-design — the same, for a directory-level module inside a package.task-spec — a working document for one piece of work; not durable. Once the work lands it is
retired with status: done, never deleted: spec search skips it, and the user keeps it as an
artifact.Read:
spec_search — the sections that answer a question, ranked by words: any order, word forms
(renaming ↔ rename), identifiers split (renameSession ↔ rename session). Several phrasings
fuse into one ranking. It matches words, not meaning — when nothing fits, rephrase with the words a
spec would use.spec_grep — search within specs (content, narrowed by metadata filters).spec_get — a spec's frontmatter, its resolved links, and its path. Read the body with the normal
read tool using that path.spec_graph — a bounded slice of the graph: a subtree, ancestors, or a node's neighbors, to a depth.Manage:
spec_create — a new spec with scaffolded frontmatter and headings.spec_update — a spec's frontmatter (fields and links). It does not touch the body.spec_delete — remove a spec.spec_validate — report dangling links, duplicate ids, and parent cycles.Prose is written and edited with the normal write/edit tools; the spec tools own frontmatter and
structure.
spec_graph for the neighborhood, spec_get for a node's metadata, and read for its body. Use
spec_search to find the governing section by words, and spec_grep for an exact pattern or
metadata narrowing.status) with spec_update, prose with edit — and add spec_create for a new module.spec_validate after structural changes.Use 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 architecture decision.
---name: spec-graphdescription: Use when locating, reading, creating, updating, or validating project specs, or when work is governed by or…---# packages/spec-graph/skills/spec-graph/SKILL.mdPerguntas frequentes
Baixe packages/spec-graph/skills/spec-graph/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/JetBrains/thinkrail.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.