skills.rest
Obsidian-Owl
Obsidian-OwlOFFICIAL
Explore all skills by this author →
WebsiteGitHub

arc42-epic-decomposer

Generate a structured Epic catalogue from Arc42 architecture documentation.

1|Updated Jan 15, 2026
Search Tags:#planning#architecture#epics#decomposition#speckit#architecture-docs#arc42
One-click install
npx skills add https://github.com/Obsidian-Owl/agentlint --skill arc42-epic-decomposer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arc42-epic-decomposer
Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/arc42-epic-decomposer
Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill arc42-epic-decomposer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Arc42 architecture documentation can be verbose and difficult to translate into actionable development work. This Skill analyzes Arc42 docs and decomposes them into well-sized Epics suitable for Speckit implementation, enabling rapid planning and traceability.

Core Features & Use Cases

  • Arc42 to Epic mapping: Extracts Arc42 sections (Building Blocks, Runtime Scenarios, ADRs, QR references) to generate a structured epic catalogue.
  • Phase-guided decomposition: Produces Epics with clear boundaries, MVP definitions, and traceability to Arc42 sections.
  • Output generation: Writes final Epics into docs/planning/epics/ and maintains traceability references to source Arc42 data for governance.

Quick Start

Ensure Arc42 documentation exists under docs/architecture/arc42/ (and ADRs under docs/architecture/adr/ if present). Run the decomposition workflow to generate the epic catalogue in docs/planning/epics/, aligning Epics to Arc42 content and ADR constraints.

Frequently Asked Questions about arc42-epic-decomposer

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

FAQPage Schema
How do I decompose Arc42 architecture documentation into actionable development epics?▼

Decomposing Arc42 architecture documentation into development epics involves analyzing building blocks, runtime scenarios, and ADRs to generate a structured epic catalogue with clear boundaries, MVP definitions, and traceability to source sections.

What is the process for mapping Arc42 building blocks to Speckit-ready epics?▼

Mapping Arc42 building blocks to Speckit-ready epics requires extracting sections like runtime scenarios and architecture decision records, then generating epics with dependency mappings and traceability references saved under docs/planning/epics/.

How do I generate an epic catalogue from existing Arc42 design docs?▼

Generating an epic catalogue from Arc42 design docs requires existing architecture documentation under docs/architecture/arc42/ and optional ADRs under docs/architecture/adr/, which are analyzed to produce phase-guided epics with MVP definitions.

Does epic decomposition from Arc42 docs maintain traceability to architecture decision records?▼

Yes, epic decomposition from Arc42 docs maintains traceability by mapping generated epics directly to source Arc42 sections and ADR constraints, ensuring architecture governance is preserved throughout the planning outputs.

Can I use Arc42 epic decomposition for projects that need MVP definitions and dependency mappings?▼

Arc42 epic decomposition supports projects needing MVP definitions and dependency mappings by producing phase-guided epics with clear boundaries, ensuring structured planning outputs align directly with architecture constraints.

What are the limitations of generating epics from Arc42 architecture documentation?▼

Generating epics from Arc42 architecture documentation requires pre-existing Arc42 docs and ADRs in specific directories; without these structured inputs under docs/architecture/, the decomposition workflow cannot produce traceable epic catalogues.

Related Skills

Explore More Software Engineering Skills→
FernanSuozaFernanSuoza

arch-arc42-architect

Draft arc42 architecture documents with embedded REQ sections and traceable decisions.

Community
Advanced
Khamel83Khamel83

implement-plan

Execute approved implementation plans with persistent beads-backed task tracking.

Community
Advanced
pkuppenspkuppens

architecture-decisions

Capture architectural decisions with context, options, and consequences into arc42-compatible ADRs.

Community
Advanced
ChoiHyunjinChoiHyunjin

role-po

Define product requirements, MVP scope, and agile user stories.

Community
Intermediate