Structured Problem Solving — community Structured Problem Solving, community, ide skills

v1.0.0
GitHub

このスキルについて

高度なAIエージェントが複雑なタスクを体系的に解決するために、4つの段階にわたるワークフロー・アプローチを必要とする場合に最適 Zwingt den Agenten, Aufgaben in einem strukturierten, 4-phasigen Workflow anzugehen (Analysis -> Concept -> Review -> Implementation).

BenniKiel BenniKiel
[0]
[0]
Updated: 3/6/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
20
Canonical Locale
de
Detected Body Locale
de

高度なAIエージェントが複雑なタスクを体系的に解決するために、4つの段階にわたるワークフロー・アプローチを必要とする場合に最適 Zwingt den Agenten, Aufgaben in einem strukturierten, 4-phasigen Workflow anzugehen (Analysis -> Concept -> Review -> Implementation).

このスキルを使用する理由

エージェントが早期のコーディングを防ぎ、複雑なタスクを体系的に解決できるようにし、関連するドキュメント、既存のコード、そしてアーキテクチャの分析を含む問題解決への体系的なアプローチを提供し、同時に制約と要件を理解する

おすすめ

高度なAIエージェントが複雑なタスクを体系的に解決するために、4つの段階にわたるワークフロー・アプローチを必要とする場合に最適

↓ 実現可能なユースケース for Structured Problem Solving

早期のコーディングを防ぐために複雑なタスクを分析する
開発者向けに問題解決のための体系的なアプローチを生成する
制約と要件を特定するために既存のコードとアーキテクチャをデバッグする

! セキュリティと制限

  • 関連するドキュメントと既存のコードへのアクセスが必要
  • 制約と要件の理解が必要
  • 体系的なアプローチを必要とする複雑なタスクのみに限定

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is Structured Problem Solving?

高度なAIエージェントが複雑なタスクを体系的に解決するために、4つの段階にわたるワークフロー・アプローチを必要とする場合に最適 Zwingt den Agenten, Aufgaben in einem strukturierten, 4-phasigen Workflow anzugehen (Analysis -> Concept -> Review -> Implementation).

How do I install Structured Problem Solving?

Run the command: npx killer-skills add BenniKiel/S.A.G.E.--Systematic-Agentic-Guidance-Environment-/Structured Problem Solving. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for Structured Problem Solving?

Key use cases include: 早期のコーディングを防ぐために複雑なタスクを分析する, 開発者向けに問題解決のための体系的なアプローチを生成する, 制約と要件を特定するために既存のコードとアーキテクチャをデバッグする.

Which IDEs are compatible with Structured Problem Solving?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for Structured Problem Solving?

関連するドキュメントと既存のコードへのアクセスが必要. 制約と要件の理解が必要. 体系的なアプローチを必要とする複雑なタスクのみに限定.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add BenniKiel/S.A.G.E.--Systematic-Agentic-Guidance-Environment-/Structured Problem Solving. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use Structured Problem Solving immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

Structured Problem Solving

Install Structured Problem Solving, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Structured Problem Solving Skill

Dieser Skill verhindert voreiliges Coden und stellt sicher, dass komplexe Aufgaben methodisch und fehlerfrei gelöst werden.

Wende diesen 4-Phasen-Workflow bei jeder Aufgabe an, die über triviale Code-Änderungen oder simple Fixes hinausgeht:

1. Analysis (Kontext aufbauen)

  • Lies die relevanten Dokumentationen im docs/ Ordner (siehe continuous_documentation Skill).
  • Analysiere den bestehenden Code und die Architektur. Verstehe die Constraints und das Problem vollständig, bevor du über Lösungen nachdenkst.

2. Conceptualization (Entwurf)

  • Formuliere einen klaren Plan, wie du das Problem architektonisch lösen wirst.
  • Halte dich an die Architektur-Standards des Projekts (SSOT, bestehende Patterns).
  • Erstelle bei neuen Systemen einen ersten Entwurf des System-Dokuments (gemäß system_design_standards).

3. User Review Gate (Zwingender Stopp)

  • Bevor du Code schreibst, MUSST du stoppen.
  • Präsentiere dem User dein Konzept (Implementation Plan).
  • Frage explizit nach Erlaubnis: "Bist du mit diesem Konzept einverstanden? Darf ich mit der Implementierung beginnen?"
  • Gehe erst zur nächsten Phase über, wenn der User sein klares "Okay" gegeben hat.

4. Implementation & Auto-Update

  • Setze dein Konzept im Code um.
  • Halte Best Practices ein und schreibe sauberen Code.
  • Iterative Design Loops: Wenn du während der Implementierung auf harte Blocker stößt (z.B. Engine-Restriktionen), die dein Konzept ungültig machen, MUSST du mit dem Coding aufhören. Kehre zu Phase 2 (Conceptualization) zurück, korrigiere die docs/ und frage den User nach einem erneuten Approval.
  • Sobald die Implementierung erfolgreich abgeschlossen ist, aktualisiere zwingend die zugehörigen Markdown-Dateien in docs/ (Epilog Phase des continuous_documentation Skills).

関連スキル

Looking for an alternative to Structured Problem Solving or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者