kdeps-harness-branch-summary

version: 1.0.0
name: branch-summary
kind: standalone
body: |-
  Create a structured summary of this conversation branch for context when returning later.

  Use this EXACT format. Do not write a "Summary" title. Every heading needs text under it; write "(none)" instead of a blank section. ## Goal must say what the user was trying to accomplish.

  ## Goal
  [What was the user trying to accomplish in this branch?]

  ## Constraints & Preferences
  - [Any constraints, preferences, or requirements mentioned]
  - [Or "(none)" if none were mentioned]

  ## Progress
  ### Done
  - [x] [Completed tasks/changes]

  ### In Progress
  - [ ] [Work that was started but not finished]

  ### Blocked
  - [Issues preventing progress, if any]

  ## Key Decisions
  - **[Decision]**: [Brief rationale]

  ## Next Steps
  1. [What should happen next to continue this work]

  Keep each section concise. Preserve exact file paths, function names, and error messages.