원클릭으로 Manus에서 모든 스킬 실행

systematic-investigation

스타4

포크0

업데이트2026년 7월 14일 10:37

Debug, investigate, and solve complex problems using structured frameworks (5 Whys, Fishbone, OODA, First Principles, PDCA). Use for tricky bugs, failure investigation, root cause analysis, architectural decisions, pre-mortem, or untangling multi-concern situations. Also activate when stuck in circles, on vague/recurring symptoms, or "why does this keep happening." Trigger phrases: "debug this", "troubleshoot", "figure out why", "root cause", "what's going wrong", "fix this bug", "this keeps breaking", "first principles", "pre-mortem", "red team this", "challenge assumptions", "go deeper", "rethink this", "inversion".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

InNoobWeTrust

InNoobWeTrust/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Systematic Investigation

Structured problem-solving — not guess-and-check.

DEFINE → ANALYZE → SOLVE & ACT → CHALLENGE

Iron law: no fixes without root-cause investigation first.

Framework selection

Situation	Use	Phase	Deep ref
Vague symptom	5W → 5 Whys	Define → Analyze	`references/define-and-debug.md`, `root-cause-frameworks.md`
Multiple causes	Ishikawa	Analyze	`root-cause-frameworks.md`
Recurring / systemic	Iceberg	Analyze	`root-cause-frameworks.md`
Stuck on assumptions	First Principles	Analyze	`root-cause-frameworks.md`
Live incident	OODA	Solve	`solve-and-challenge.md`
Iterative improvement	PDCA	Solve	`solve-and-challenge.md`
Stakeholder report	A3	Solve	`solve-and-challenge.md`
Multi-concern mess	Kepner-Tregoe SA	Define	`define-and-debug.md`
Technical bug / test fail	Debug protocol (4 sub-phases)	All	`define-and-debug.md`

Load one deep ref at a time. Elicitation second pass: references/elicitation-methods.md. Origins: references/origins.md.

Mandatory flow

Define — 5W statement: "[Who] experiences [What] in [Where] since [When], causing [impact]." Load define-and-debug.md if tangled or technical.
Analyze — pick method from table; load root-cause-frameworks.md. Confirm root cause with evidence.
Governance capture (if AI/process gap) — note rule/skill gap for handoff / skill-author audit (advisory).
Solve — 5 Hows or OODA/PDCA; load solve-and-challenge.md. Fix root cause, not symptom. One change at a time.
Challenge — pre-mortem / adversarial vectors; PROCEED | REVISE | RETHINK. Optional: elicitation methods.
Report — use references/report-template.md when handing off or documenting.

Debug red flags (STOP)

"Quick fix now, investigate later"
Multiple fixes at once; 3+ failed fixes without re-analysis
Proposing solutions before tracing data flow
"Just try X and see"

Done checklist

Problem defined clearly (5W)
Root cause confirmed with evidence
Solution addresses root cause
Solution challenged (Phase 4)
Concrete action + verification + prevention plan
Report filled when stakeholder/handoff needs it

이 저장소의 다른 Skills

같은 저장소

codebase-exploration

InNoobWeTrust/dotfiles

Navigate and map large unfamiliar codebases. Find where behavior lives, trace feature flow and call chains, map architecture and dependency graphs, plan migrations/refactors, or answer "where is X" and "how does this work" questions. Also use for codebase scouting, hunting for specific patterns, discovering module relationships, or code archaeology. Activate on "find the code for", "how is X implemented", "navigate the codebase", "trace this", "map the architecture", or any task in an unfamiliar repo.

2026-07-154

memory

InNoobWeTrust/dotfiles

Human-inspired working + consolidated memory for agents, and the same progressive-disclosure pattern applied to docs and code. Two-tier store: unbounded short-term notes (working memory, per-branch session state, scratchpads) and size-limited long-term memory (curated facts, decisions, constraints, corrections) reached through an INDEX. A dream cycle runs on explicit request or git commit to consolidate hot short-term entries into long-term, score existing long-term entries, and propose evictions for human approval. Session checkpoints are one kind of short-term memory entry. Trigger phrases: 'remember this', 'save memory', 'checkpoint', 'save handoff', 'save context', 'what was I working on', 'resume', 'restore', 'load context', 'consolidate memory', 'dream cycle', 'prune memory', 'forget', 'evict', 'index my notes', 'structure docs', 'shard doc', 'split module', 'progressive disclosure'.

2026-07-154

multi-perspective-deliberation

InNoobWeTrust/dotfiles

Coordinate a multi-persona deliberation session to challenge assumptions, debate architectural decisions, and perform pre-mortems. Leverages concurrent delegated agents/workers when the environment supports them, or falls back to single-context simulated dialogue. Trigger phrases: 'party mode', 'deliberation', 'multi-perspective', 'get a second opinion', 'debate this', 'challenge design'.

2026-07-154

project-foundation

InNoobWeTrust/dotfiles

Bootstrap, audit, evolve, and materialize the AI-augmented project foundation (AGENTS.md, GLOSSARY.md, .agents/rules+skills core pack, Makefile, architecture, quality gates). Load for new project setup, missing skills after bootstrap, foundation drift, sync .agents from global, evolve AGENTS/GLOSSARY/architecture to match the repo, or audit project foundation. Skip only when editing a single existing rule/skill body with no pack-level change.

2026-07-154

reviewer

InNoobWeTrust/dotfiles

Multi-lens review orchestrator for code, specs, architecture, config, docs, and infrastructure. Hybrid execution: direct technical review using sub-reviewer references, or delegate to independent agents/workers for multi-perspective, audit, or specialized reviews. Sub-lenses: code-quality, design-rigor, adversarial, security, edge-case, editorial. Activate on "review", "check", "audit", "challenge", "QA", or any explicit review request.

2026-07-154

subagent-dispatch

InNoobWeTrust/dotfiles

Construct a precise, structured delegation prompt before every delegated-agent or worker launch. Use whenever you are about to delegate work to a background agent, run a task in parallel, or spawn a worker. Injects scope constraints, a structured output contract, obstacle reporting, and allowed-action boundaries directly into the input prompt to compensate for generic or unconfigured delegated-worker descriptions. Activate on: 'delegate this', 'run this in parallel', 'use the research agent', 'background task', 'spawn a worker', 'launch a subagent', 'hand this off'.

2026-07-154

name

systematic-investigation

description

Systematic Investigation

Structured problem-solving — not guess-and-check.

DEFINE → ANALYZE → SOLVE & ACT → CHALLENGE

Iron law: no fixes without root-cause investigation first.

Framework selection

Situation	Use	Phase	Deep ref
Vague symptom	5W → 5 Whys	Define → Analyze	`references/define-and-debug.md`, `root-cause-frameworks.md`
Multiple causes	Ishikawa	Analyze	`root-cause-frameworks.md`
Recurring / systemic	Iceberg	Analyze	`root-cause-frameworks.md`
Stuck on assumptions	First Principles	Analyze	`root-cause-frameworks.md`
Live incident	OODA	Solve	`solve-and-challenge.md`
Iterative improvement	PDCA	Solve	`solve-and-challenge.md`
Stakeholder report	A3	Solve	`solve-and-challenge.md`
Multi-concern mess	Kepner-Tregoe SA	Define	`define-and-debug.md`
Technical bug / test fail	Debug protocol (4 sub-phases)	All	`define-and-debug.md`

Load one deep ref at a time. Elicitation second pass: references/elicitation-methods.md. Origins: references/origins.md.

Mandatory flow

Define — 5W statement: "[Who] experiences [What] in [Where] since [When], causing [impact]." Load define-and-debug.md if tangled or technical.
Analyze — pick method from table; load root-cause-frameworks.md. Confirm root cause with evidence.
Governance capture (if AI/process gap) — note rule/skill gap for handoff / skill-author audit (advisory).
Solve — 5 Hows or OODA/PDCA; load solve-and-challenge.md. Fix root cause, not symptom. One change at a time.
Challenge — pre-mortem / adversarial vectors; PROCEED | REVISE | RETHINK. Optional: elicitation methods.
Report — use references/report-template.md when handing off or documenting.

Debug red flags (STOP)

"Quick fix now, investigate later"
Multiple fixes at once; 3+ failed fixes without re-analysis
Proposing solutions before tracing data flow
"Just try X and see"

Done checklist

Problem defined clearly (5W)
Root cause confirmed with evidence
Solution addresses root cause
Solution challenged (Phase 4)
Concrete action + verification + prevention plan
Report filled when stakeholder/handoff needs it