agentmods.dev

power-roadmap-status

power-roadmap-status is a skill for Claude Code, Codex from pwdev-solucoes/pwdev-claude-marketplace. It costs 30 tokens per session (834 once invoked), scanned A, original, Apache-2.0.

A read-only report for a product roadmap, which is a plan showing what a product will deliver and in what order. It reads the roadmap's records and reports progress, completeness, links between requirements and work, risks, and the next valid action.

In plain words
What is it for?
Use it to check roadmap status, progress, traceability, completeness, and the next permitted planning step.
Why use it?
It gives an evidence-based view of roadmap health without changing or approving any planning files. Missing records are reported rather than silently filled in.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the pwdev-power plugin — 16 skills, 3 agents shipped together

not rated 3repo changed 1mo ago A scan 30 tokens original Apache-2.0

Good fit Use it to check roadmap status, progress, traceability, completeness, and the next permitted planning step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status
View source ↗ pwdev-solucoes/pwdev-claude-marketplace
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 pwdev-solucoes/pwdev-claude-marketplace --skill power-roadmap-status
Clone the repo
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code, Codex.

Or install pwdev-power, the plugin that ships this one along with the rest of its 16 skills, 3 agents.

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 power-roadmap-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status)
Your own site
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status/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 power-roadmap-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-roadmap-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 834 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00834
Opus 5.5 $0.00012 $0.00334
Sonnet 5.5 $0.00006 $0.00167
Haiku 4.5 $0.00003 $0.00083

Measured 1mo ago against content hash 65b7a2ac1b5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

power-roadmap-status 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 1mo 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.

plugins/pwdev-power/skills/power-roadmap-status/SKILL.md · 74 lines

How it starts

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

Roadmap Status

Report the roadmap's health from its durable artifacts. This workflow is read-only: never create, repair, approve, reject, or otherwise edit an artifact while reporting status.

When a path or field below is unfamiliar, artifacts has the tree and collaboration §Gates says where each human gate is recorded.

Sources of truth

Inspect these paths when they exist:

  1. .planning/power/config.json for the configured response language.
  2. .planning/power/state.md for the recorded status, last gate, active artifact, and next action.
  3. .planning/power/product/prd.md for requirement approval and scope.
  4. .planning/power/product/roadmap/ROADMAP.md for the roadmap index.
  5. .planning/power/product/roadmap/TRACEABILITY.md for requirement-to-roadmap coverage in both directions.
  6. .planning/power/product/roadmap/RISKS.md, METRICS.md, ROLLOUT.md, and the phase, epic, and feature files beneath the roadmap root for completeness and counts.

Missing files are findings, not reasons to invent state. Do not treat the existence of a PRD or roadmap as approval. Human gate results recorded in state.md, plus the PRD's explicit approval field where applicable, are authoritative.

Assessment

Determine the lifecycle state without changing it:

  • NOT_INITIALIZED: .planning/power/state.md is absent.
  • NO_REQUIREMENT: state exists but prd.md does not.
  • REQUIREMENT_DRAFT: the PRD exists without exactly one Status: APPROVED field.
  • READY_FOR_ROADMAP: the requirement is approved but ROADMAP.md is absent.
  • ROADMAP_INCOMPLETE: the roadmap exists but a mandatory artifact, hierarchy link, source reference, acceptance criterion, or bidirectional traceability entry is missing or malformed.
  • AWAITING_ACCEPTANCE: the roadmap is structurally complete but state.md does not record the human roadmap gate as approved.
  • ACCEPTED: state.md records the roadmap gate as approved and the files remain structurally complete.
  • BLOCKED: state.md records a blocked gate; report its recorded reason when present.

Read the full file on GitHub · 74 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago Changed · +1 lines 65b7a2ac1b5b
  2. 1mo ago First seen · 73 lines · 30 tokens per session scan A 2dca901cfbdc

Subscribe to this mod's changes

power-roadmap-status is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 30 tokens to every session and 834 once invoked, about $0.0001 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-09-07.

PlanningProject management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens