メニュー
Investigates identified issues in a LearningAgent session by reading the transcript, determining root causes, and updating issue files with investigation reports.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Welcome new users to DeepWork — introduce features, set up reviews, and optionally record a first workflow
Run DeepWork Reviews on the current branch — review changed files using .deepreview rules
Creates a new LearningAgent with directory structure, core-knowledge.md, and Claude Code agent file. Guides the user through initial configuration.
Runs the learning cycle on all LearningAgent sessions with pending transcripts. Identifies issues, investigates root causes, and incorporates learnings into agent definitions.
Reference documentation for DeepWork Reviews — automated code review rules using .deepreview configs and DeepSchema-generated rules
Start or continue DeepWork workflows using MCP tools
| name | investigate-issues |
| description | Investigates identified issues in a LearningAgent session by reading the transcript, determining root causes, and updating issue files with investigation reports. |
| user-invocable | false |
Research identified issues from a LearningAgent session to determine their root causes.
$ARGUMENTS is the path to the session log folder (e.g., .deepwork/tmp/agent_sessions/<session_id>/<agent_id>/).
Session log folder structure:
!cat learning_agents/doc/learning_log_folder_structure.md 2>/dev/null
Agent used: !cat $ARGUMENTS/agent_used 2>/dev/null || echo "unknown"
Identified issues to investigate:
!grep -l 'status: identified' $ARGUMENTS/*.issue.yml 2>/dev/null || echo "(none)"
Additional investigation guidelines:
!learning_agents/scripts/cat_agent_guideline.sh $ARGUMENTS issue_investigation
-------- CURRENT KNOWLEDGE OF AGENT --------
!learning_agents/scripts/generate_agent_instructions_for_session.sh $ARGUMENTS
------ END CURRENT KNOWLEDGE OF AGENT-------
If no identified issues are listed above, report that and stop.
Refer back to the conversation_transcript.jsonl file as needed in this process.
For each issue file with status identified:
issue_description or locate lines near seen_at_timestampscore-knowledge.mdFor each investigated issue, use Edit to update the issue file:
status: identified to status: investigatedinvestigation_report field:status: investigated
investigation_report: |
<Root cause analysis with specific transcript line numbers as evidence.
Explain what knowledge gap or instruction deficiency caused the issue.>
Simply say "Session log folder done."
issue_description — only add the investigation_reportidentified issue