msd-core/commands/msd/forensics.md at next

Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

2.2 KiB

Raw Permalink Blame History

type, name, description, argument-hint, allowed-tools, requires

type

name

description

argument-hint

allowed-tools

requires

prompt

msd:forensics

Post-mortem investigation for failed MSD workflows — diagnoses what went wrong.

[problem description]

Read

Write

Bash

Grep

Glob

phase

progress

update

Investigate what went wrong during a MSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.

Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to .planning/forensics/, presented inline, with optional issue creation.

<execution_context> @~/.claude/msd-core/workflows/forensics.md </execution_context>

**Data sources:** - `git log` (recent commits, patterns, time gaps) - `git status` / `git diff` (uncommitted work, conflicts) - `.planning/STATE.md` (current position, session history) - `.planning/ROADMAP.md` (phase scope and progress) - `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md) - `.planning/reports/SESSION_REPORT.md` (last session outcomes)

User input:

Problem description: $ARGUMENTS (optional — will ask if not provided)

Execute end-to-end.

<success_criteria>

Evidence gathered from all available data sources
At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
Structured forensic report written to .planning/forensics/report-{timestamp}.md
Report presented inline with findings, anomalies, and recommendations
Interactive investigation offered for deeper analysis
GitHub issue creation offered if actionable findings exist </success_criteria>

<critical_rules>

Read-only investigation: Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
Redact sensitive data: Strip absolute paths, API keys, tokens from reports and issues.
Ground findings in evidence: Every anomaly must cite specific commits, files, or state data.
No speculation without evidence: If data is insufficient, say so — do not fabricate root causes. </critical_rules>

2.2 KiB Raw Permalink Blame History

2.2 KiB

Raw Permalink Blame History