architecture-roadmap

architecture-roadmap is a skill for Claude Code from sethdford/claude-skills. It costs 33 tokens per session (634 once invoked), scanned A, original, MIT.

A planning tool for mapping how a software system should change over several quarters. It organizes major technical projects, their order, effort, dependencies, and timing.

In plain words
What is it for?
Use it to plan work such as database migrations, service redesigns, monitoring, deployment automation, and other multi-quarter changes.
Why use it?
It turns long-term architecture work into a shared plan that accounts for business priorities and limited team capacity.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the communication plugin — 7 skills shipped together

Good fit Use it to plan work such as database migrations, service redesigns, monitoring, deployment automation, and other multi-quarter changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sethdford/claude-skills/architecture-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 sethdford/claude-skills --skill architecture-roadmap
Clone the repo
git clone --depth 1 https://github.com/sethdford/claude-skills

Made for: Claude Code.

Or install communication, the plugin that ships this one along with the rest of its 7 skills.

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 architecture-roadmap

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-roadmap"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 634 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.00033 $0.00634
Opus 5 $0.00016 $0.00317
Sonnet 5 $0.00007 $0.00127
Haiku 4.5 $0.00003 $0.00063

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

Security

Grade A, and why

architecture-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 10d 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.

architect/communication/skills/architecture-roadmap/SKILL.md · 53 lines

How it starts

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

Architecture Roadmap

Create strategic architecture roadmap aligned with business goals and organizational capacity.

Context

You are planning architecture evolution over next 2-4 quarters. Prioritize initiatives, estimate effort, communicate strategy to stakeholders. Read business strategy, current technical gaps, team capacity.

Domain Context

Based on strategic planning and architecture roadmapping:

  • Architecture Initiatives: Major changes (migrate to microservices, refactor database, implement observability)
  • Dependencies: Some initiatives block others. Database migration must complete before service redesign.
  • Timeline: When should each initiative start? Capacity constraints (limited team, shared resources).
  • Communication: Regular updates to stakeholders. Adapt roadmap as priorities shift.

Instructions

  1. Identify Themes:

    • Year 1: Foundation (infrastructure, observability, deployment automation)
    • Year 2: Scale (microservices, database sharding, multi-region)
    • Year 3: Maturity (compliance, security, advanced optimizations)
  2. Define Initiatives (per quarter):

    • Q1: "Implement centralized logging and monitoring" (2 engineers, 4 weeks)
    • Q2: "Migrate from EC2 to Kubernetes" (3 engineers, 8 weeks)
    • Q3: "Split monolith into microservices (Payment)" (4 engineers, 10 weeks)
  3. Map Dependencies: Q1 enables Q2 (monitoring needed before K8s migration). Q2 enables Q3 (K8s for service deployment).

  4. Estimate Effort: Be honest. "Migrate monolith" is 6+ months, not 2. Pad estimates; add contingency.

  5. Communicate Regularly: Monthly updates to leadership. Celebrate completions. Adjust for new priorities. Show progress.

Anti-Patterns

  • Roadmap Set in Stone: Never changes. Reality doesn't match plan. Result: roadmap ignored, decisions made ad-hoc. Guard: Review quarterly; adjust based on new information.
  • Too Ambitious: Promise 10 initiatives in 3 months. Result: miss all deadlines, team burned out. Guard: Realistic scope; 2-3 major initiatives per quarter max.
  • No Dependency Tracking: Start initiatives in wrong order, blocked by other work. Result: slow progress. Guard: Explicit dependency map; critical path analysis.
  • No Communication: Roadmap exists but teams don't know. Result: surprises, resistance. Guard: Publish and discuss; gather feedback; explain trade-offs.

Read the full file on GitHub · 53 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. 10d ago First seen · 53 lines · 33 tokens per session scan A 70f680b4c9ad

Subscribe to this mod's changes

architecture-roadmap is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 634 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-08-30.

Related

Other skills, from other repositories