Skip to content
Back to skills

Detailed System Decomposition Hierarchy

ASecurity

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

  • 581 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 30, 2026
education

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ECNU-ICALK/AutoSkill --skill detailed-system-decomposition-hierarchy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Detailed System Decomposition Hierarchy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Detailed System Decomposition Hierarchy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ecnu-icalk-detailed-system-decomposition-hierarchy/badge)](https://www.skillsdirectory.com/skills/ecnu-icalk-detailed-system-decomposition-hierarchy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.