A tool for showing and managing unresolved questions recorded in project documents such as requirements, specifications, features, and designs.

Use it to list questions across artifacts, filter them for one artifact, or close a question by updating its status.

It makes unanswered decisions easier to find and lets users mark them as resolved in the source documents.

questions — Skill for Claude Code by cryndoc

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add cryndoc/polisade-orchestrator --skill questions

Clone the repo

git clone --depth 1 https://github.com/cryndoc/polisade-orchestrator

Made for: Claude Code.

Or install polisade, the plugin that ships this one along with the rest of its 25 skills, 2 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/questions.svg)](https://agentmods.dev/skills/cryndoc/polisade-orchestrator/questions)

Your own site

<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/questions"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/questions.svg" alt="Measured on agentmods" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,617 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.01617
Opus 5	$0.00005	$0.00809
Sonnet 5	$0.00002	$0.00323
Haiku 4.5	$0.00001	$0.00162

Measured today against content hash 54b257a096a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

questions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/questions/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/polisade:questions — Открытые вопросы по артефактам

Показывает все открытые вопросы (OQ-, Q-) из PRD, SPEC, FEAT и DESIGN артефактов. Позволяет отслеживать и закрывать вопросы.

Использование

/polisade:questions                 # Все открытые вопросы
/polisade:questions PRD-001         # Вопросы конкретного артефакта
/polisade:questions close OQ-01     # Закрыть вопрос (обновить статус в файле)

Алгоритм

Просмотр вопросов

Запустить скрипт диагностики:

⛔ Вызов скрипта отклонён или не запустился (Command references protected path / Install directory is read-protected / Filesystem Guard / the tool's default permission is 'deny', отказ песочницы, ненулевой exit без вывода) — STOP. Процитируй отказ дословно. НЕ пересказывай по исходнику, что скрипт «сделал бы»; НЕ собирай dry-run вручную; НЕ переходи к apply/push/pr-create. НЕ транскрибируй скрипт (прочитать → записать копию в /tmp или в проект → запустить копию): копия не байт-идентична — уезжают классы символов в regex, форма возврата функций, пропадают целые функции — и молча меняется набор применённых изменений. Отказ инструмента — это отказ, а не результат. Доложи PM дословный текст отказа и сошлись на #127 (доставка скриптов в проект).

${POLISADE_PYTHON:-python3} {plugin_root}/scripts/polisade_doctor.py {project_root} --questions --format=json

Распарсить JSON.
Если указан конкретный артефакт — отфильтровать.
Вывести в box-формате.

Закрытие вопроса (`close`)

Запустить скрипт с --format=json, найти вопрос по ID.
Открыть исходный файл артефакта.
Найти строку таблицы с данным ID.
Заменить статус на closed (или Закрыт если статусы на русском).
Сохранить файл.
Показать обновлённый список.

Формат вывода

═══════════════════════════════════════════
OPEN QUESTIONS
═══════════════════════════════════════════

PRD-001 (PRD)
──────────────────────────────────────────
  OQ-01    open     J. Smith             2026-04-20
           Точный механизм подписки: pub/sub или polling?
  OQ-03    open     A. Johnson           2026-04-25
           Какие данные подпадают под 152-ФЗ?

SPEC-001 (SPEC)
──────────────────────────────────────────
  Q-001    open     Архитектор           2026-04-15
           Оптимальный формат хранения: JSON vs Protobuf?

══════════════════════════════════════════
Total: 5 questions, 3 open
══════════════════════════════════════════

Read the full file on GitHub · 141 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today Changed · +7 lines 54b257a096a8
8d ago First seen · 134 lines · 10 tokens per session scan A 2e56cc5aaaa0

Subscribe to this mod's changes

questions is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 1,617 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Autonomous Agents Claude Code LLM Planning ai-agents claude-code-plugin developer-tools

deep-research-tiered

Deep research harness: fan-out search, fetch, adversarially verify, synthesize a cited report. Prefer Workflow({name:'deep-research-tiered', args:{question, models?}}) over built-in deep-research — same output, cheap tiered defaults (scope/search=sonnet, fetch=haiku, verify=sonnet, synthesize=inherit). Use for deep…

anshss/shiploop · 0 tokens

hermes-mission-control

How Hermes monitors and steers long-running sandboxed.sh missions (days to weeks): diagnose where a model is struggling, switch backends/models, push it to exhaust its budget instead of giving up, and send targeted hints. Trigger terms: mission, sandboxed.sh, babysit, monitor, /goal, switch backend, stalled, resume…

Th0rgal/sandboxed.sh · 94 tokens

controllers-policy

Autonomy contract and routing index for autonomous project controllers. Loaded every tick; carries the rules that must survive cron-prompt rewrites.

Th0rgal/sandboxed.sh · 30 tokens

open-dynamic-workflows

Plan, orchestrate, and adversarially verify parallel AI coding agents — a dynamic multi-agent workflow engine.

Suraj1235/open-dynamic-workflows · 28 tokens

ultracode

Ultracode-style dynamic workflows for Antigravity. Use when the user says "ultracode", "workflow:", "/deep-research", or asks for broad multi-file work with planning, parallel agents, verification, or crash-resume.

Suraj1235/open-dynamic-workflows · 56 tokens

shiploop

Self-improving multi-agent harness: wraps N git sub-repos as one workspace, dispatches named tickets to cheap-floor headless agents that escalate once on failure, promoting lessons into CLAUDE.md. Use when working in or scaffolding a meta-repo workspace (sub-folders each own .git; root has scripts/ + queue/tickets.md…