A roadmap-planning workflow that orders feature specifications into deliverables, where each deliverable is a usable minimum version of the product. It focuses on delivery order rather than implementation details.

Use it to group and sequence completed feature specifications into a delivery roadmap.

It helps decide what to ship first and ensures each stage can stand on its own. This prevents feature specifications from becoming an unclear or impractical delivery sequence.

aid-plan — Skill for Claude Code by AndreVianna

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 AndreVianna/aid-methodology --skill aid-plan

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

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/andrevianna/aid-methodology/aid-plan/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-plan)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-plan"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-plan"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,794 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.00041	$0.02794
Opus 5	$0.00020	$0.01397
Sonnet 5	$0.00008	$0.00559
Haiku 4.5	$0.00004	$0.00279

Measured 8d ago against content hash 51434c220580, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

aid-plan 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 8d 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.

.claude/skills/aid-plan/SKILL.md · 280 lines

How it starts

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

Delivery Roadmap

Sequence features into deliverables where each is a functional MVP that works on its own.

Core Principle

Plan answers ONE question: "In what order do we deliver, and does each delivery stand on its own?"

What Plan does NOT do (already covered by Specify):

Module mapping, test scenarios, per-feature risks, technical details — all in SPEC.

The Loop

Each deliverable follows the same cycle:

1. PROPOSE  → agent proposes deliverable grouping and sequence
2. DISCUSS  → the user and the agent negotiate (move, reorder, split, merge, defer)
3. WRITE    → save agreed deliverable to PLAN.md
4. REVIEW   → grade against SPECs/KB — pass? next deliverable. fail? back to 1.

Re-run = enter at step 4 with existing PLAN.md.

Workspace

.aid/
  knowledge/                <- shared KB (read)
    STATE.md                <- minimum grade
  work-NNN-{name}/
    STATE.yml                <- frontmatter-zone keys (authored); Plan/Deliveries is DERIVED (never written here)
    REQUIREMENTS.md         <- read; § 11 holds the `### Feature NNN` sections
                            #  (check Features State in work STATE.yml)
    PLAN.md                 <- OUTPUT: delivery stanzas (each one the delivery
                            #  definition: objective, scope, gate criteria) + execution graph
    deliveries/
      delivery-NNN/           <- CREATED by aid-plan per delivery approved in PLAN.md
        STATE.yml              <- OUTPUT: delivery lifecycle (initial delivery_state: Pending-Spec) + gate key + qa key

Note: deliveries/delivery-NNN/ must exist before aid-detail nests tasks/task-NNN/ under it. The work STATE.yml's Plan/Deliveries view is a DERIVED read-only view assembled at read time from deliveries/delivery-NNN/STATE.yml files. aid-plan does NOT write delivery rows into the work STATE.yml.

Arguments

Argument	Effect
`work-NNN`	Plan a specific work. Required if multiple works exist.
(no arg)	Auto-selects if only one work exists.
`--reset`	Delete PLAN.md and start fresh.

Read the full file on GitHub · 280 lines

Files

What ships with it

3 files 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.

8d ago First seen · 280 lines · 41 tokens per session scan A 51434c220580

Subscribe to this mod's changes

aid-plan is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,794 once invoked, about $0.0002 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-09-03.

Planning Project management

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens