Menü
Accurate, auditable execution journal for each working session.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Rules and strategies for managing agent context window size, avoiding bloat, and preserving signal-to-noise ratio.
Standard patterns for error handling, retry logic, circuit breakers, and graceful degradation.
Detect and remove contradictions across agent policies before execution.
Multi-step tool workflows via code orchestration to reduce latency, context pollution, and token overhead.
Bind project-specific prompts to local schema and workflow artifacts while keeping the harness core generic and globally reusable.
Operational session protocol for task-scoped leases, reconciliation, checkpoints, inspection, queue promotion, and handoff across long-running work.
| name | session-logging |
| description | Accurate, auditable execution journal for each working session. |
Maintain an accurate, auditable execution journal for each working session.
sessions-<ISO-date>.md
[mX/iY] references)# Session — <ISO-date>
## Status
- M1: in_progress (2/3 issues done)
- M2: todo
## Work Completed
- [M1/I1] Set up project scaffold ✅
- [M1/I2] Implement core module ✅
- [M1/I3] Unit tests — in progress
## Completion Gate Passed
- M1/I1: ✅ 2 consecutive clean passes (run 1: 0 errors, run 2: 0 errors)
- M1/I2: ✅ 2 consecutive clean passes (run 1: 0 errors, run 2: 0 errors)
## Decisions Made
- Chose adapter pattern over inheritance for extensibility (interaction-loop option 1)
## Blockers
- None
## GitHub Sync
- Created: #12, #13, #14
- Closed: #12, #13
- Updated: #14 (status → in-progress)
## Branch
`feature/core-module`
## Date
<ISO-8601 timestamp>
github-sync — ensure the GitHub Sync section in the session log is aligned with actual GitHub milestone/issue stateWhen using the harness-lifecycle pattern, every session must append a structured handoff block to progress.md before ending. This is the cross-session memory that allows the next context window to quickly get up to speed.
## Session [N] — YYYY-MM-DD
### Done
- [Feature/task description with concrete outcome]
### Next
- [Highest-priority incomplete feature to pick up]
### Blockers
- [Any issues that prevent progress, or "None"]
feature_list.json.Done section must reference specific features or issue IDs.Next section must point to a single, actionable next step.progress.md