The hall-side work is done: CLOSING.md specifies the closing routine and is reachable from README, ENTRY and AGENTS; entries carry a validated PQRST record in frontmatter and body; make check enforces it for agent seats from 2026-09-06 with human seats exempt and existing seats grandfathered; the one manual estimate is normalised. Remaining here: the pilot (T01), the storage decision (T02) — which the hall integration now makes concrete — and cutting v0.2 (T03). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SQ6oF1DtVDKcD1FCpvRVLx Assistant: claude-code Assistant-Model: opus Assistant-Process: 272883@bnt-lap001 Assistant-Session: f40c8f53-fb65-4980-9d29-bcdb3dd946f7 |
||
|---|---|---|
| history | ||
| spec | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| INTENT.md | ||
| PqrstPrompt.md | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
pqrst-practice
A lightweight retrospective audit for closing agentic coding sessions: a forced 100% allocation of a session's effective engineering effort across five stable dimensions — Problem, Quality, Research, Security, Task organization.
Where did the effective engineering effort of this session actually go?
Start here
| I want to… | Read |
|---|---|
| Close a session right now | PqrstPrompt.md — paste it, done |
| Understand the model | spec/PqrstEstimationPractice.md (v0.1) |
| Know why it exists, and what it must not become | INTENT.md |
| Know what belongs in this repo | SCOPE.md |
| Work in this repo as an agent | AGENTS.md |
What a record looks like
PQRST-Estimate
P: 25%
Q: 15%
R: 45%
S: 0%
T: 15%
Sum: 100%
Confidence: medium
Signature: P25 Q15 R45 S0 T15
Dominant factors: Existing auth middleware was undocumented and contradicted the
README, so most attention went to reconstructing the request path before
changing behavior.
The numbers are the index. The Dominant factors sentence is the content — a
signature stored without it is not auditable.
What this is not
Not a productivity score, not telemetry, not a planning target. There is no good profile: an exploration session is R-heavy, a hardening session Q-heavy, a credential integration S-heavy. The practice fails the moment anyone tries to score well on it.
This repository defines the practice and supplies the prompt. Collectors,
validators, dashboards, and record storage belong elsewhere — see
SCOPE.md.