e81592878e
* feat(#2789): trim skill description anti-patterns; enforce 100-char budget - Trim descriptions in all commands/gsd/*.md files over 100 chars - Remove flag documentation from descriptions (belongs in argument-hint) - Remove Triggers: keyword stuffing - Add scripts/lint-descriptions.cjs — fails on descriptions > 100 chars - Add npm script: lint:descriptions - Add tests/enh-2789-description-budget.test.cjs Closes #2789 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs(#2789): add CHANGELOG entry for description budget lint * docs(#2789): update COMMANDS.md descriptions; add skill description standards note Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
57 lines
2.3 KiB
Markdown
57 lines
2.3 KiB
Markdown
---
|
|
type: prompt
|
|
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/get-shit-done/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>
|
|
Read and execute the forensics workflow from @~/.claude/get-shit-done/workflows/forensics.md 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>
|