← スキル一覧に戻る
hierarchy-levels
by mguttmann
Autonomous Organization Framework - A complete system for AI-assisted software development with Claude Code
⭐ 0🍴 0📅 2026年1月25日
Manusで実行SKILL.md
name: hierarchy-levels description: Organization hierarchy from strategic to execution levels with all agents
Hierarchy Levels
Das Framework organisiert Arbeit in 4 Hierarchie-Ebenen, jede mit spezifischen Agenten und Verantwortlichkeiten.
Übersicht
| Level | Focus | Time Horizon | Entscheidungen |
|---|---|---|---|
| Strategic | Vision, "warum" | Jahre | Richtung, Ziele, Ressourcen |
| Tactical | Roadmaps, "was" | Quartale | Planung, Priorisierung |
| Operational | Projekte, "wie" | Wochen/Sprints | Ausführung, Koordination |
| Execution | Tasks, "machen" | Stunden/Tage | Implementation |
Flow
VISION → STRATEGY → ROADMAP → PROJECTS → PHASES → TASKS → VERIFICATION
↑ |
└───────────────── Feedback Loop ──────────────────────────┘
Strategic Level (5 Agents)
Focus: Vision, Richtung, "Warum machen wir das?"
| Agent | Verantwortung | Entscheidungen |
|---|---|---|
| CEO | Gesamtvision, Stakeholder | Strategische Richtung |
| CFO | Budget, Finanzen | Investitionen, Kosten |
| CTO | Tech-Strategie, Architektur | Technologie-Stack |
| CPO | Produkt-Vision, Roadmap | Was wir bauen |
| CMO | Markt, Wachstum, Brand | Go-to-Market |
Use Cases:
- Neue Produktidee evaluieren
- Technologie-Stack festlegen
- Budget-Allokation
- Strategische Partnerschaften
- Markteintrittsstrategie
Typische Outputs:
- Vision Statement
- Strategy Document
- Investment Proposal
- Technology Radar
Tactical Level (5 Agents)
Focus: Quartalsplanung, "Was bauen wir wann?"
| Agent | Verantwortung | Entscheidungen |
|---|---|---|
| Product Director | Quarterly Planning, Feature-Priorisierung | Roadmap-Inhalte |
| Engineering Director | Kapazität, Standards, Teams | Ressourcen-Allokation |
| Marketing Director | Kampagnen, Launches | Marketing-Strategie |
| People Director | Hiring, Kultur, Team-Entwicklung | Team-Struktur |
| Finance Director | Budget-Tracking, Forecasting | Budget-Verteilung |
Use Cases:
- Quarterly OKRs setzen
- Roadmap für nächstes Quartal
- Team-Kapazität planen
- Cross-Team Koordination
- Release-Planung
Typische Outputs:
- Quarterly Roadmap
- OKR Document
- Capacity Plan
- Release Calendar
Operational Level (6 Agents)
Focus: Sprint-Ausführung, "Wie setzen wir das um?"
| Agent | Verantwortung | Entscheidungen |
|---|---|---|
| Product Manager | User Stories, Backlog | Story-Details |
| Engineering Manager | Sprint-Execution, Team-Lead | Sprint-Inhalt |
| Project Manager | Timeline, Risiken, Dependencies | Projekt-Planung |
| Team Lead | Technische Guidance, Mentoring | Tech-Entscheidungen |
| Scrum Master | Prozess, Ceremonies | Prozess-Verbesserung |
| Product Owner | Priorisierung, Acceptance | Fertig-Kriterien |
Use Cases:
- Sprint Planning
- Daily Standup
- Blocker lösen
- Stakeholder-Updates
- Retrospektive durchführen
Typische Outputs:
- Sprint Backlog
- PLAN.md
- Status Reports
- Retrospective Actions
Execution Level (5 Agents)
Focus: Task-Implementierung, "Machen!"
| Agent | Verantwortung | Entscheidungen |
|---|---|---|
| Architect | System Design, Patterns | Architektur-Details |
| Developer | Code schreiben, Tests | Implementation |
| Designer | UX/UI Design | Design-Details |
| QA Engineer | Testing, Quality Gates | Test-Strategie |
| Analyst | Daten-Analyse, Metriken | Analyse-Methoden |
Use Cases:
- Feature implementieren
- Bug fixen
- Tests schreiben
- UI designen
- Performance analysieren
Typische Outputs:
- Code
- Tests
- Design Mockups
- Analysis Reports
- Documentation
Support Agents (5 Agents)
Cross-cutting: Unterstützen alle Levels
| Agent | Verantwortung | Wann einsetzen |
|---|---|---|
| Researcher | Investigation, Evaluation | Neue Technologien, Optionen |
| Reviewer | Quality Gates, Code Review | PR Review, Architecture Review |
| Verifier | Goal Validation | Feature-Completion |
| Debugger | Problem-Solving | Komplexe Bugs |
| Coordinator | Kommunikation, Sync | Cross-Team Work |
Specialist Agents (5 Agents)
Domain-spezifisch: Spezialwissen
| Agent | Verantwortung | Wann einsetzen |
|---|---|---|
| Security Analyst | Security Review, Threats | Security-sensitive Code |
| Data Engineer | Data Pipelines, ETL | Daten-Architektur |
| DevOps Engineer | Infrastructure, CI/CD | Deployment, Monitoring |
| Technical Writer | Documentation | User Docs, API Docs |
| UX Researcher | User Research | User-Feedback, Usability |
Wann welches Level?
| Situation | Level | Agents |
|---|---|---|
| "Sollen wir dieses Produkt bauen?" | Strategic | CEO, CPO |
| "Welche Technologie nutzen wir?" | Strategic | CTO |
| "Was bauen wir im nächsten Quartal?" | Tactical | Product Director |
| "Wer arbeitet an welchem Projekt?" | Tactical | Engineering Director |
| "Welche Stories in den Sprint?" | Operational | Product Manager, Scrum Master |
| "Wie implementieren wir das?" | Operational | Team Lead |
| "Code schreiben" | Execution | Developer |
| "Design erstellen" | Execution | Designer |
| "Ist das Feature fertig?" | Support | Verifier |
| "Security-Problem?" | Specialist | Security Analyst |
Escalation Path
Execution → Operational → Tactical → Strategic
↑ ↑ ↑ ↑
Developer Team Lead Director CxO
Eskaliere wenn:
- Scope-Änderung nötig
- Budget-Entscheidung
- Timeline-Risiko
- Strategische Frage
- Rechtliche/Compliance-Frage
スコア
総合スコア
70/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です