OpenSkillIndex← back to search
claude-code

AutoSkill 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.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt3.5_8/detailed-system-decomposition-hierarchy" ~/.claude/skills/ecnu-icalk-autoskill-detailed-system-decomposition-hierarchy && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt3.5_8/detailed-system-decomposition-hierarchy/SKILL.md
source content

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