aboutsummaryrefslogtreecommitdiff
path: root/.ai/workflows/wrap-it-up.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-20 23:28:37 -0400
committerCraig Jennings <c@cjennings.net>2026-06-20 23:28:37 -0400
commit76e55591e2a66e8ef42ee6e4535882545ee3d33b (patch)
tree84b83f62e0ea11374ffb9e870839787391c40461 /.ai/workflows/wrap-it-up.org
parent8a50088b063a7e0e7a79e8f7aa799ee6185fd814 (diff)
downloadrulesets-76e55591e2a66e8ef42ee6e4535882545ee3d33b.tar.gz
rulesets-76e55591e2a66e8ef42ee6e4535882545ee3d33b.zip
feat(kb): wire consult + contribute KB prompts into the workflows
Recent session receipts read "promoted 0 / consulted no" across the board: the wrap-up KB-promotion check existed but fired too late, and nothing surfaced existing lessons to read. This adds the spec's four light prompts plus the read-side step it was missing. Startup gets two Phase C nudges (gated on the roam clone): a consult line listing project-relevant node titles, and a contribute line pointing at the best-practices node. Triage-intake and inbox-zero get a conditional end-of-flow capture reminder that fires only on real signal. Wrap-up gets an early reflection prompt at the top of Step 1 that feeds the existing receipt, so learnings are captured while fresh instead of reconstructed after the Summary. Ratifies the spec's five decisions and adds D6 (the read-side surfacing).
Diffstat (limited to '.ai/workflows/wrap-it-up.org')
-rw-r--r--.ai/workflows/wrap-it-up.org4
1 files changed, 4 insertions, 0 deletions
diff --git a/.ai/workflows/wrap-it-up.org b/.ai/workflows/wrap-it-up.org
index 139d612..b1560eb 100644
--- a/.ai/workflows/wrap-it-up.org
+++ b/.ai/workflows/wrap-it-up.org
@@ -33,6 +33,10 @@ The absence of =.ai/session-context.org= is the signal that the last session wra
** Step 1: Finalize the Summary
+*** Early KB reflection (capture while fresh, before the Summary)
+
+Before distilling the Summary, while the session is still fresh, ask: what did this session learn worth remembering, for yourself or a future agent? Reflect and stage any candidate durable facts — a decision and its why, an environment gotcha, a reference pointer, a transferable lesson. Self-answer silently; this adds no interactive turn (Craig already authorized the wrap). The candidates flow straight into the KB promotion check below, which does the actual writing and the receipt — this is the capture half, that is the commit half, one pipeline, one receipt. Reflecting here rather than reconstructing learnings after the Summary is the point: the early ask is what keeps the receipt from defaulting to "promoted 0" out of fatigue.
+
Read through the =* Session Log= in =.ai/session-context.org=. Populate (or refine) the =* Summary= section:
- *Active Goal* — one or two sentences describing the session's focus