Menü
Use when you need to analyze cascade impact of changing a component.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need persistent looping until a task is fully complete.
Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.
Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.
Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.
| name | impact-analysis |
| description | Use when you need to analyze cascade impact of changing a component. |
| user-invocable | false |
Analyze the cascade impact of modifying a component using the project ontology's dependency graph.
/team-shinchan:impact-analysis [options]
<target> — Entity name, ID, or file path to analyze--depth <N> — Traversal depth (default: 2, max: 5)--direction outgoing|incoming|both — Direction of analysis (default: both).shinchan-docs/ontology/ontology.json exists/team-shinchan:ontology scan first."Run node ${CLAUDE_PLUGIN_ROOT}/src/ontology-engine.js related <entityId> with the specified depth.
Analyze the result:
Calculate risk level based on:
Display:
Impact Analysis: {target name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Risk Level: {HIGH|MEDIUM|LOW}
Direct Dependencies ({N}):
- {component name} ({file_path}) — {relation type}
...
Indirect Dependencies ({N}):
- {component name} ({file_path}) — via {intermediate}
...
Test Coverage:
- {test suite name} ({file_path}) — covers {component}
...
Affected Modules:
- {module name} ({N} components affected)
...
Recommendations:
- {recommendation based on risk level}
If ontology doesn't exist or target not found, suggest running scan first.