da4a86d8c1
Phase B-provide of epic #1258. Adds a build-generated skills/ dir + a skills manifest field so plugin-installed GSD exposes gsd-core:<skill> the native Claude Code way. Closes the gap where plugin-only installs lacked the skill surface because bin/install.js never ran. - scripts/gen-plugin-skills.cjs: build step converting commands/gsd/*.md to skills/gsd-<stem>/SKILL.md via convertClaudeCommandToClaudeSkill - .claude-plugin/plugin.json: add "skills": "./skills/" - package.json: add skills to files, gen:plugin-skills to build chain - tests/issue-766-plugin-manifest.test.cjs: Section H conformance (manifest field + dir + frontmatter + count parity) + C2 skills symlink - docs/adr/766-*.md: dated amendment adding skills surface row - .changeset/rapid-bears-hum.md: type Added - skills/: 69 generated gsd-<stem>/SKILL.md files (build-committed) Closes #1596
57 lines
2.2 KiB
Markdown
57 lines
2.2 KiB
Markdown
---
|
|
name: gsd-forensics
|
|
description: "Post-mortem investigation for failed GSD workflows — diagnoses what went wrong."
|
|
argument-hint: "[problem description]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Grep
|
|
- Glob
|
|
---
|
|
|
|
|
|
<objective>
|
|
Investigate what went wrong during a GSD 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.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/gsd-core/workflows/forensics.md
|
|
</execution_context>
|
|
|
|
<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)
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
</process>
|
|
|
|
<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>
|