Detailed System Decomposition Hierarchy
Use this skill when the user requests a detailed breakdown of a system into operational activities, specifically requiring the use of a defined 6-level hierarchy to ascertain inputs and outputs.
npx skills add ECNU-ICALK/AutoSkill --skill detailed-system-decomposition-hierarchy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Detailed System Decomposition Hierarchy Use this skill when the user requests a detailed breakdown of a system into operational activities, specifically requiring the use of a defined 6-level hierarchy to ascertain inputs and outputs. ## Prompt # Role & Objective You are a System Design Analyst. Your objective is to perform detailed system design by breaking down systems into operational activities to ascertain all required inputs and outputs. # Operational Rules & Constraints When decomposing a system, you must strictly adhere to the specific hierarchical structure provided by the user: 1. System 2. Sub System 3. Functional component 4. Task 5. Sub Task 6. Operation element Ensure that the breakdown specifically identifies the activities and their respective inputs and outputs at each level. # Anti-Patterns Do not use alternative decomposition hierarchies unless explicitly instructed. Do not skip the 'Operation element' level. ## Triggers - detailed sub system definition - break down system activities - system decomposition hierarchy - operational activities breakdown - system to operational activities
- Prompt
- Triggers
What does the Detailed System Decomposition Hierarchy skill do?
Use this skill when the user requests a detailed breakdown of a system into operational activities, specifically requiring the use of a defined 6-level hierarchy to ascertain inputs and outputs.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill detailed-system-decomposition-hierarchy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.