- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add rohitg00/pro-workflow --skill plan-interrogate -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add rohitg00/pro-workflow --skill plan-interrogate -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add rohitg00/pro-workflow --skill plan-interrogate -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add rohitg00/pro-workflow --skill plan-interrogate -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/rohitg00/pro-workflow/tree/HEAD/skills/plan-interrogateОт издателя
Drive a plan from sketch to commitment by resolving every open decision before any code is written.
user (the user answered), inferred (the
codebase or an existing constraint settled it).inferred: <path>.Decision - Choice - Source (user | inferred: <path>).The interrogation produces three artifacts, not just answers. Offer to write each; do not force it.
Decision ledger (always). The resolved tree as a flat list:
Decision - Choice - Source (user | inferred: <path>).
CONTEXT.md (when the interrogation surfaced project-specific terms).
A short shared-language file: every domain term you and the user had to
pin down, with a one-line definition in the project's own words. This is
what stops the agent from using twenty words where one will do next
session, and keeps names in code consistent. One term per line:
term - what it means here. Point future sessions at it. On re-run, merge
new terms in place rather than overwriting existing ones.
Decision records (for contested or hard-to-reverse nodes only). One
short record per decision that a future reader would question: the
context, the choice, the alternatives rejected, and why. Keep them in
docs/decisions/NNNN-slug.md. Read the directory first and number from the
highest existing record so two records never collide. Skip the obvious ones -
a record for a trivial choice is noise.
The decision ledger the user can paste into the plan doc. No prose summary.
No hedging. If the user declines to decide a node, mark it DEFERRED with
the reason the user gave - this is not the same as open. When you write
CONTEXT.md or a decision record, keep it in the project's language, not a
generic template.
Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to pressure-test a design before implementation.
---name: plan-interrogatedescription: Stress-test a plan by walking its decision tree one question at a time. Use when the user wants to…---# skills/plan-interrogate/SKILL.mdFAQ
Скачайте skills/plan-interrogate/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/rohitg00/pro-workflow.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.