diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-20 23:28:37 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-20 23:28:37 -0400 |
| commit | 76e55591e2a66e8ef42ee6e4535882545ee3d33b (patch) | |
| tree | 84b83f62e0ea11374ffb9e870839787391c40461 /.ai/workflows/triage-intake.org | |
| parent | 8a50088b063a7e0e7a79e8f7aa799ee6185fd814 (diff) | |
| download | rulesets-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/triage-intake.org')
| -rw-r--r-- | .ai/workflows/triage-intake.org | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/.ai/workflows/triage-intake.org b/.ai/workflows/triage-intake.org index 9e9e3dd..7241017 100644 --- a/.ai/workflows/triage-intake.org +++ b/.ai/workflows/triage-intake.org @@ -167,6 +167,10 @@ If Craig has been silent for a while after Phase D and the surface looks closed- This rule prevents the failure mode where the workflow self-declares done and the next exchange has to relitigate what state things are in. +*** KB capture (only if the sweep surfaced something durable) + +If this sweep surfaced a durable, cross-project fact — a recurring pattern across sources, a reference pointer worth keeping, an environment gotcha — consider writing it to the agent KB as one =:agent:= node (see the best-practices node and =knowledge-base.md=; personal projects only, work never writes). One line of judgment, not a step: an all-quiet sweep surfaces nothing and writes nothing. Never blocking, never padded onto a no-signal run. + * Auto mode (unattended monitoring) |
