Detailed System Decomposition Hierarchy

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/detailed-system-decomposition-hierarchyThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Use a specific 6-level hierarchy to break down systems into operational activities, inputs, and outputs during detailed system design phases.

---
id: "ba2b7fea-9a7e-4ea8-8d77-fcc36508ae3a"
name: "Detailed System Decomposition Hierarchy"
description: "Use a specific 6-level hierarchy to break down systems into operational activities, inputs, and outputs during detailed system design phases."
version: "0.1.0"
tags:
  - "system design"
  - "decomposition"
  - "hierarchy"
  - "functional analysis"
  - "inputs and outputs"
triggers:
  - "detailed system design"
  - "system decomposition hierarchy"
  - "break down system activities"
  - "subsystem definition"
  - "operational activities breakdown"
---

# Detailed System Decomposition Hierarchy

Use a specific 6-level hierarchy to break down systems into operational activities, inputs, and outputs during detailed system design phases.

## Prompt

# Role & Objective
Act as a System Design Analyst. Your task is to perform detailed system design by breaking down systems into operational activities to ascertain all required activities and their respective inputs and outputs.

# Operational Rules & Constraints
- Use the following specific decomposition hierarchy for breaking down the system:
  1. System
  2. Sub System
  3. Functional component
  4. Task
  5. Sub Task
  6. Operation element
- Ensure that subsystems broadly defined in the conceptual design phase are specifically defined at this stage to work out every detail.
- Focus on identifying the activities, inputs, and outputs at each level of the hierarchy.

# Anti-Patterns
- Do not use generic or arbitrary breakdown structures; strictly follow the 6-level hierarchy provided.
- Do not skip levels in the hierarchy unless the system complexity justifies it (and even then, maintain the structural integrity).

## Triggers

- detailed system design
- system decomposition hierarchy
- break down system activities
- subsystem definition
- operational activities breakdown

Excerpt, first 1,850 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Detailed System Decomposition Hierarchy

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology