skills.rest
DojoGenesis
DojoGenesisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

era-architecture

Define an Era Master Plan with vocabulary, constraints, and a multi-release roadmap.

2|Updated Apr 8, 2026
Search Tags:#architecture#dependencies#strategic-planning#era#master-plan#release-roadmap
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill era-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: era-architecture
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/continuous-learning/skills/era-architecture
Command: npx skills add https://github.com/DojoGenesis/gateway --skill era-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates strategy for long-horizon product eras by codifying vocabulary, architectural constraints, and a shared release roadmap to keep teams aligned across multiple releases.

Core Features & Use Cases

  • Establishes a conceptual architecture that spans all releases
  • Defines a release roadmap and dependency graph to guide execution
  • Serves as a living master plan that adapts as decisions evolve and releases are validated

Quick Start

Generate an Era Master Plan for the current product era spanning 3-7 releases.

Frequently Asked Questions about era-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a multi-release master plan and when do I need one for product architecture?▼

A multi-release master plan codifies vocabulary, architectural constraints, and a shared release roadmap to align teams across 3 to 7 releases. You need one during strategic pivots requiring cross-cutting architecture and long-horizon planning.

How do I plan a release roadmap for a strategic product era spanning multiple releases?▼

To plan a release roadmap, define an Era Master Plan that establishes a conceptual architecture, maps dependencies, and sequences releases. This living document adapts as decisions evolve and releases are validated.

Can I use a master plan to manage architectural dependencies across multiple teams?▼

Yes, a master plan aligns multiple teams by codifying shared vocabulary and defining a dependency graph. It ensures cross-cutting architecture remains consistent across 3 to 7 releases.

What is the best way to document architectural constraints for a long-horizon product strategy?▼

The best way to document architectural constraints is generating an Era Master Plan that codifies vocabulary, outlines a vision, and maps a release roadmap. It serves as a living document updated as decisions evolve.

Does a multi-release master plan work for strategic pivots under 3 releases?▼

No, an Era Master Plan is designed for strategic pivots spanning 3 to 7 releases. For shorter horizons, a standard release roadmap or single-release architecture plan is more appropriate.

How do I keep a release roadmap and master plan updated as product decisions evolve?▼

You keep a master plan updated by treating it as a living document. The Era Master Plan framework includes a living update process to adapt the release roadmap and constraints as releases are validated.

Related Skills

Explore More Product & Management Skills→
Tonybleything76Tonybleything76

product-strategist

Generate aligned OKRs from company strategy to team level.

Community
Advanced
shalevaminshalevamin

sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
hgflimahgflima
1

roadmap-planning-views

Create and manage focused planning views for roadmap task subsets.

Community
Intermediate
ryan-nguyen-01ryan-nguyen-01
4

agent-pm

Coordinate product delivery from backlog to release with structured templates.

Community
Advanced