Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

architecture-roadmap | communication | ClaudePluginHub

Skill

architecture-roadmap

From communication

Create multi-quarter architecture vision and roadmap. Prioritize initiatives, estimate effort, communicate strategy. Use when planning architecture evolution or communicating long-term vision.

$

npx claudepluginhub sethdford/claude-skills --plugin architect-communication

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/communication:architecture-roadmap

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

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

SKILL.md

53 lines · ~726 tokens

Similar Skills

technical-roadmap

13

Build multi-quarter technical roadmaps aligned with business goals, clearly showing strategic investments, trade-offs, and dependencies. Use when planning longer-term technical direction, communicating with stakeholders, or aligning engineering capacity with business priorities.

2 files5 tools

technical-planning

roadmap-generator

89

Generates phased roadmaps (MVP, Scale, Advanced) from architecture designs with Epic/Story/Task breakdowns, T-shirt effort estimates, and validation gates.

2 files

roadmap-planning

4.4k

Guides product managers through strategic roadmap planning: prioritization, epic definition, stakeholder alignment, and release sequencing. Use to turn strategy into an actionable release plan.

2 files

product-manager-skills

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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

Identify Themes:
- Year 1: Foundation (infrastructure, observability, deployment automation)
- Year 2: Scale (microservices, database sharding, multi-region)
- Year 3: Maturity (compliance, security, advanced optimizations)
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)
Map Dependencies: Q1 enables Q2 (monitoring needed before K8s migration). Q2 enables Q3 (K8s for service deployment).
Estimate Effort: Be honest. "Migrate monolith" is 6+ months, not 2. Pad estimates; add contingency.
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.

Further Reading

Roadmapping in Product Management by Todd Olson — strategic planning
The Goal by Eliyahu Goldratt — dependency and bottleneck management
Scaling Up by Verne Harnish — organizational alignment and execution