kdeps-harness-branch-summary
v1.0.0kdeps harness: branch-summary
set harness / shelf context
PurposeThe text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
LLM context: ~214 tokens when loaded (prompt or tool definition)
Where it runs
Part of the harness set, used in workflow and agent mode. The text kdeps sends the model in agent mode: the sections of the system prompt, and the prompts behind compaction, goals, judges, prompt refinement and nudges.
- you type a prompt
- the agent loop builds the request
- the harness sections become the system promptharness/branch-summary
- the model answers
- the loop runs tools or replies
Loaded by: kdeps (agent loop), /settings, kdeps run, kdeps konfig export, kdeps knowledge build, kdeps konfig import
In the code: kdeps (agent loop)agent.Newagent.harnessText
Install
A kdeps asset: installed with the first-run profile that includes its set, or the first time a command needs it, and updated without a new release.
Pin a version with kdeps install harness/branch-summary@<version>.
Contents
- name
- branch-summary
- kind
- standalone
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.
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.
Versions
| Version | Published | Status |
|---|---|---|
| 1.0.0 | 10/11/2026 | active |
Details
- Author
- kdeps
- License
- Apache-2.0
- Latest Version
- 1.0.0
- Published
- 10/11/2026