tegwick
2b36fc187d
T01 — Reviewed the generated integration files. Resolved the
{CREDENTIAL_ROUTING} placeholder in AGENTS.md from the fleet canon, refreshed
the SCOPE.md repository layout (stale after registration), and replaced the
README stub with orientation and entry points.
T02 — Documented the developer workflow in AGENTS.md. This is a Markdown-only
spec repository: nothing to install, build, or run, and no test suite. In place
of a toolchain, added a six-point verification checklist covering prompt/spec
coupling, the closed 5-tuple, example-record arithmetic, cross-references,
version discipline, and the append-only rule for history/. The signature
validation command is verified working — all nine example signatures sum to 100.
T03 — Seeded PQRST-WP-0002 "Validate spec v0.1 against real sessions and cut
v0.2": pilot the closing prompt unassisted on at least eight real sessions,
decide the record-storage boundary SCOPE.md leaves open, then revise. v0.1 was
consolidated from two drafts neither of which had been applied to a session, so
the open questions are empirical rather than editorial.
WP-0001 marked finished with DoR/DoD assessments (clears C-34). No open
residuals — the follow-on work is carried by PQRST-WP-0002.
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
1.6 KiB
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.