roadmap

roadmap is a skill for Claude Code from cryndoc/polisade-orchestrator. It costs 109 tokens per session (7,428 once invoked), scanned A, original, Apache-2.0.

An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.

In plain words
What is it for?
Use it for large initiatives, multi-phase projects, complex dependencies, or work that spans several weeks. A monorepo or other repository structure is not specified here.
Why use it?
It helps teams understand the order of work and coordinate changes that depend on one another.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Part of the polisade plugin — 25 skills, 2 commands shipped together

Good fit Use it for large initiatives, multi-phase projects, complex dependencies, or work that spans several weeks. A monorepo or other repository structure is not specified here.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cryndoc/polisade-orchestrator/roadmap
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 roadmap
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.

agentmods badge for roadmap

README.md
[![agentmods](https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/roadmap/github.svg)](https://agentmods.dev/skills/cryndoc/polisade-orchestrator/roadmap)
Your own site
<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/roadmap"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/roadmap/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for roadmap

Your own site · 80×15
<a href="https://agentmods.dev/skills/cryndoc/polisade-orchestrator/roadmap"><img src="https://agentmods.dev/badge/skills/cryndoc/polisade-orchestrator/roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,428 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 114
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • high Prompt Injection · line 114
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • medium analysis-evasion · line 1
    Suspicious Unicode normalization or mixed-script content
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00109 $0.07428
Opus 5.5 $0.00044 $0.02971
Sonnet 5.5 $0.00022 $0.01486
Haiku 4.5 $0.00011 $0.00743

Measured 13d ago against content hash e5bd09ca09d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

roadmap 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 13d ago.

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/roadmap/SKILL.md · 710 lines

How it starts

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

/polisade:roadmap [SPEC-XXX] — План реализации через субагент

Создание плана реализации на основе технической спецификации через изолированный субагент.

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

/polisade:roadmap SPEC-001   # План для конкретной спеки
/polisade:roadmap            # Выбрать из доступных ready SPEC

Когда нужен roadmap

Нужен PLAN:

  • Крупная инициатива с несколькими фазами
  • Сложные зависимости между задачами
  • Работа на несколько недель
  • Требуется координация компонентов

Не нужен PLAN (иди сразу в /polisade:tasks):

  • Простая фича (2-5 задач)
  • Линейная последовательность работ
  • Нет сложных зависимостей

Архитектура с субагентом

┌─────────────────────────────────────────────────────────────┐
│  PM: /polisade:roadmap SPEC-001                                 │
└─────────────────────────────────────────────────────────────┘
                        │
                        ▼
┌─────────────────────────────────────────────────────────────┐
│  ОСНОВНОЙ АГЕНТ                                             │
│  1. Валидация: SPEC со статусом ready                       │
│  2. Читает SPEC + связанный PRD                             │
│  3. Читает knowledge.json                                   │
│  4. Формирует prompt с системным промптом                   │
│  5. Запускает Task tool: subagent_type="general-purpose"    │
└─────────────────────────────────────────────────────────────┘
                        │
                        ▼
┌─────────────────────────────────────────────────────────────┐
│  СУБАГЕНТ general-purpose (чистый контекст)                 │
│                                                             │
│  System role: Product Delivery Roadmap Architect            │
│  Input: SPEC + PRD + project context                        │
│                                                             │
│  Делает:                                                    │
│  1. Анализирует техническую спецификацию                    │
│  2. Разбивает на логические фазы                            │
│  3. Определяет roadmap items с зависимостями                │
│  4. Выявляет критический путь                               │
│  5. Создаёт PLAN файл                                       │
│  6. Возвращает: путь, summary, items count                  │
└─────────────────────────────────────────────────────────────┘
                        │
                        ▼
┌─────────────────────────────────────────────────────────────┐
│  ОСНОВНОЙ АГЕНТ                                             │
│  1. Обновляет PROJECT_STATE.json                            │
│  2. Номер выдаст /polisade:sync на транке                   │
│  3. SPEC.children += PLAN (статус НЕ меняется)              │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 710 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.

  1. 13d ago Changed e5bd09ca09d7
  2. 14d ago Changed ef9f1c11edc3
  3. 1mo ago Changed · +9 lines 220c264d6749
  4. 1mo ago Changed · +8 lines 2e915c307840
  5. 1mo ago First seen · 693 lines · 109 tokens per session scan A cc64248f2508

Subscribe to this mod's changes

roadmap is a skill published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 5d ago), licensed Apache-2.0. It adds 109 tokens to every session and 7,428 once invoked, about $0.0004 per session on Opus 5.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.

Related

Other skills, from other repositories