innorve-skill-architecture

Decompose systems into named skills with owners, dependencies, and Mermaid diagrams.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Innorve-Inc/innorve-method --skill innorve-skill-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: innorve-skill-architecture
Source: https://github.com/Innorve-Inc/innorve-method/tree/main/plugins/innorve-method/skills/innorve-skill-architecture
Command: npx skills add https://github.com/Innorve-Inc/innorve-method --skill innorve-skill-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Innorve IM-01 flow helps teams turn a vague, monolithic AI effort into a clear, bounded set of skills with defined owners and artifacts.

Core Features & Use Cases

  • Guided workflow to split a problem into named skills with ownership.
  • Produces a Skill Graph consisting of a YAML candidate list and a Mermaid diagram.
  • Facilitates downstream contracts (IM-03) and capability graphs (IM-06) by clarifying responsibilities.

Quick Start

Walk through the IM-01 coaching flow to produce a complete Skill Graph with named skills and a Mermaid diagram.

Frequently Asked Questions about innorve-skill-architecture

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

FAQPage Schema
How do I decompose a monolithic AI system into testable skills?

A Skill Graph is a structured representation consisting of a YAML candidate list and a Mermaid diagram. It clarifies responsibilities and bounded ownership for AI work, facilitating downstream contracts and capability graphs.

Can I use Mermaid diagrams to map skill dependencies and ownership?

Yes, you can use Mermaid diagrams to map skill dependencies and ownership. The decomposition process requires each candidate skill to include a Mermaid diagram, a produced artifact name, an owner, and edge artifacts to validate the complete Skill Graph.

What do I need to define before validating a Skill Graph?

Before validating a Skill Graph, you need to define each candidate skill with a produced artifact name, an owner, dependencies, and edge artifacts. The Skill Graph must be fully complete with these elements and a Mermaid diagram before proceeding to IM-03 contracts.

Does breaking down AI work into bounded skills help with team ownership?

Breaking down AI work into bounded skills directly helps with team ownership by assigning a specific owner to each named skill. This structured decomposition clarifies responsibilities and produces reusable components for downstream contracts.

When do I need a Skill Graph for my AI architecture?

You need a Skill Graph for your AI architecture when transitioning from a vague AI effort to clear, bounded skills. It is required before proceeding to downstream IM-03 contracts and generating capability graphs for your system.