skills.rest
zhongadamwang
zhongadamwangCOMMUNITY
Explore all skills by this author →
GitHub

hierarchy-management

Decompose control-type participants into hierarchical sub-process boundaries in EDPS collaboration diagrams.

Updated Mar 15, 2026
Search Tags:#decomposition#metadata#hierarchy#documentation-automation#EDPS#process-diagrams
One-click install
npx skills add https://github.com/zhongadamwang/pricing-tool --skill hierarchy-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hierarchy-management
Source: https://github.com/zhongadamwang/pricing-tool/tree/main/.github/skills/hierarchy-management
Command: npx skills add https://github.com/zhongadamwang/pricing-tool --skill hierarchy-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and propagate hierarchical decomposition of control-type participants in EDPS collaboration diagrams, enabling Level N+1 sub-process boundaries with their own diagrams, while preserving parent-child relationships and central hierarchy metadata.

Core Features & Use Cases

  • Decompose a control participant into an independent sub-process boundary with its own collaboration, process, and domain-model artifacts.
  • Navigate, roll back, and visualize the entire process hierarchy across unlimited depth, with updated navigation links and metadata.
  • View hierarchy statistics and generation-ready stubs that are later completed by documentation-automation.

Quick Start

Decompose a control participant from a parent diagram to create a Level N+1 boundary with stub files for subsequent content generation by documentation-automation.

Frequently Asked Questions about hierarchy-management

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

FAQPage Schema
How do I decompose control participants into hierarchical sub-process boundaries?▼

Decompose control participants by splitting them into Level N+1 sub-process boundaries with their own collaboration diagrams, preserving parent-child relationships and updating central hierarchy metadata.

What is process hierarchy decomposition in EDPS collaboration diagrams?▼

Process hierarchy decomposition splits control-type participants into independent sub-process boundaries, maintaining parent-child relationships and metadata while generating stubs for documentation automation.

How do I navigate and roll back process hierarchy decompositions across multiple levels?▼

Navigate process hierarchies across unlimited depth using hierarchy tree visualizations, viewing statistics and rolling back decompositions while automatically updating navigation links and metadata.

Can I generate stub files for automated documentation when decomposing process hierarchies?▼

Decomposing a control participant generates stub files for Level N+1 boundaries, handing off these generation-ready stubs to documentation-automation for subsequent full content generation.

Does process hierarchy decomposition enforce naming conventions for sub-process boundaries?▼

Process hierarchy decomposition enforces strict naming conventions for sub-process boundaries, ensuring consistent metadata updates and maintaining accurate parent-child relationships across the entire hierarchy tree.

What are the limitations of rolling back process hierarchy decompositions?▼

Rolling back process hierarchy decompositions removes Level N+1 sub-process boundaries and their associated diagrams, which may impact downstream documentation-automation stubs and central hierarchy metadata consistency.

Related Skills

Explore More Product & Management Skills→
vladm3105vladm3105
16

charts_flow

Generate Mermaid architecture diagrams and embed SVG previews in technical documents.

Community
Advanced
reactjsreactjs
10

write

Orchestrate research, writing, and review for React documentation pages.

Official
Advanced
knopkiknopki
1

openspec-onboard

Guide users through the OpenSpec change cycle with the OpenSpec CLI.

Community
Advanced
TrecekTrecek
1

arch-lens-security

Generate Mermaid-compatible security architecture diagrams with trust boundaries and validation layers.

Community
Advanced