forge-openclaw-plugin 0.2.26 → 0.2.27

package/skills/forge-openclaw/psyche_entity_playbooks.md

@@ -9,6 +9,8 @@ Forge without turning the conversation into a worksheet.
 
 - Sound like a careful, grounded therapist who is helping the person clarify their own
   experience, not like a schema form and not like a lecturer.
+- Name the emotional center or lived stake in plain language before the next question
+  whenever that would help the user feel accurately understood.
 - Stay collaborative. Do not claim certainty about what a belief, pattern, or mode
   "really is".
 - Start from lived experience before abstraction.
@@ -36,6 +38,8 @@ Forge without turning the conversation into a worksheet.
   improves understanding and leave the others for later.
 - Before the next question, reflect back what you just heard in one or two sentences so
   the user can feel understood and correct you if needed.
+- When the material is charged, ask permission before moving from understanding into
+  naming, challenging, or solution-finding.
 - Before you ask for change, naming, or repair, usually ask what the experience is
   trying to protect, prevent, or hold onto.
 - The warmth should come from accuracy and steadiness, not from extra softness,
@@ -49,6 +53,10 @@ Forge without turning the conversation into a worksheet.
   already grounded enough that it will deepen rather than blur the picture.
 - Before you ask for the user's preferred fix, understand what the response is trying
   to protect, achieve, or prevent.
+- If several Psyche entities are visible at once, choose the clearest primary
+  container first and hold the others lightly until the user wants to map them.
+- When the user has said enough for an accurate working formulation, stop deepening and
+  help them name it cleanly.
 
 ## Therapist micro-skills
 
@@ -58,6 +66,10 @@ Reflect:
 
 - briefly mirror the user's felt sense, stake, or sequence in plain language
 
+Contain:
+
+- give a short summary that makes the moment feel holdable before you deepen or name it
+
 Locate:
 
 - ask where this shows up most clearly: the last moment, the first cue, the body
@@ -86,6 +98,23 @@ Connect:
 - when another record is clearly present, ask whether the user wants to link it now,
   save it separately later, or just keep it in the note/context for now
 
+## Therapeutic Direction Check
+
+Before each follow-up, quickly decide what therapeutic job the next question should do.
+
+1. Contain: does the user first need a short accurate summary so the experience feels
+   held?
+2. Locate: do you still need the concrete moment, cue, body signal, or sequence?
+3. Deepen: is the next useful lane situation, meaning, protection, cost, longing, or
+   naming?
+4. Formulate: is the experience coherent enough that a candidate sentence or title
+   would now help?
+5. Connect: is there an adjacent value, belief, mode, pattern, note, or task that is
+   clear enough to link without derailing the main work?
+
+If the answer is formulate or connect, do not ask another exploratory question first
+unless something still feels materially unclear.
+
 ## First-turn rule
 
 When the user wants help understanding a Psyche issue before saving it:
@@ -113,6 +142,51 @@ opening:
 - one missing-detail question
 - then move toward the write instead of forcing exploration
 
+## Therapeutic turn shapes
+
+Keep the pacing human and intentional.
+
+Opening turn:
+
+- one short reflection that names the felt stake
+- one grounded question about the nearest real moment
+
+Middle turn:
+
+- reflect what became clearer
+- name the function, fear, cost, or longing that seems most central now
+- ask one question that deepens only that lane
+
+Naming turn:
+
+- offer one careful sentence or title when the experience is coherent enough
+- ask whether it feels true, too sharp, or still incomplete
+
+Closing turn:
+
+- summarize the working formulation in the user's language
+- ask whether it feels true enough to save and whether anything adjacent should be
+  linked
+- if the user says it lands, move toward the write instead of reopening exploration
+
+## Name, Define, Connect
+
+Use this checkpoint once the material is coherent enough.
+
+Name:
+
+- offer one careful sentence or title that captures the core lived meaning
+
+Define:
+
+- clarify what makes this belief, pattern, mode, value, behavior, or report distinct
+  from nearby possibilities
+
+Connect:
+
+- only after the primary formulation feels steady, ask whether an adjacent value,
+  belief, mode, pattern, note, or task should be linked or mapped separately
+
 ## Lane chooser
 
 After each real answer, choose the next best lane. Do not mix several lanes at once.
@@ -163,7 +237,7 @@ Link lane:
 A strong follow-up usually has three parts:
 
 1. one short reflection grounded in the user's words
-2. one sentence naming what feels most important so far
+2. one sentence naming what feels most threatened, protected, or important so far
 3. one focused next question
 
 Example shape:
@@ -182,11 +256,17 @@ Another strong shape when the user is getting abstract:
 - Do not front-load a finished case formulation.
 - Do not introduce replacement beliefs, softer reframes, or tidy interpretations until
   the user has answered at least one real exploratory question.
+- Do not ask for evidence, alternative beliefs, or repair plans before the user has had
+  a fair chance to feel that the original experience was captured accurately.
+- Do not make the user prove the experience before you have helped them feel that you
+  understood it.
 - Help the user recognize the experience before you help them improve it.
 - When the user is close to the feeling but far from the wording, offer one careful
   candidate sentence or title and ask whether it fits.
 - If nuance matters, preserve it in a linked Markdown `note` instead of forcing every
   detail into normalized fields.
+- Do not widen into adjacent entities until the current one has a working sentence the
+  user recognizes.
 - Before saving, give a short working summary in the user's own language and ask
   whether it feels true enough.
 - A good final check is often:
@@ -215,6 +295,7 @@ Sometimes the user asks to save a Psyche entity directly.
 If the entity is already clear:
 
 - reflect briefly
+- name the core meaning in the user's language
 - ask only for the one missing structural detail
 - save without forcing extra exploration
 
@@ -224,6 +305,8 @@ If the entity is not yet clear:
 - prefer a question about the most recent example, the protective job, or the core
   meaning
 - then move toward naming and save
+- once the user accepts the wording, do not reopen deeper exploration unless they ask
+  for it
 
 ## Psyche update loop
 
@@ -236,6 +319,9 @@ from scratch.
 4. Ask for one concrete recent example if the update is abstract or sweeping.
 5. Then change only the parts the new understanding actually affects.
 
+If the update is mostly about wording, offer one revised sentence yourself and ask
+whether it lands more accurately before you reopen the whole exploration.
+
 Good update opener:
 
 - "Before we change it, what feels newly true about this now, and what still feels basically right?"
@@ -254,10 +340,11 @@ Aim: clarify a direction to live toward, not a goal to complete.
 Arc:
 
 1. Ask when the pull or absence of the value felt noticeable recently.
-2. Ask how living it would look in ordinary behavior.
-3. Separate the value from a performance target.
-4. Ask what gets in the way.
-5. Land on one concrete expression or committed action.
+2. Reflect the longing, pain, or importance that makes the value alive right now.
+3. Ask how living it would look in ordinary behavior.
+4. Separate the value from a performance target.
+5. Ask what gets in the way.
+6. Land on one concrete expression or committed action.
 
 Helpful follow-up lanes:
 
@@ -367,9 +454,12 @@ Arc:
 1. Ask what the experience starts telling the user in that moment.
 2. Help condense it into one belief sentence in the user's own language.
 3. Clarify whether it is `absolute` or `conditional`.
-4. Ask how true it feels from `0` to `100`.
-5. Gather one or two pieces of supporting evidence and one or two strains against it.
-6. Ask where the rule feels learned, reinforced, or familiar.
+4. Ask how true it feels from `0` to `100` only if that helps the user feel the force
+   of it more clearly.
+5. Ask where the rule feels learned, reinforced, or familiar if that would deepen the
+   formulation.
+6. Gather supporting or weakening evidence only if the user wants fuller examination
+   or if the wording is still fuzzy.
 7. Offer a more flexible alternative only if the user wants that and only after the
    belief itself is clear.
 
@@ -378,8 +468,8 @@ Helpful follow-up lanes:
 - the feared consequence inside the belief
 - what the moment seems to prove
 - how old or familiar the rule feels
-- evidence for
-- evidence against
+- evidence for only if the user wants to examine it
+- evidence against only if the user wants to examine it
 - whether the user wants help drafting a more flexible version
 
 Likely linked entities:
@@ -392,7 +482,7 @@ Ready to save when:
 
 - the belief can be written as one sentence
 - `beliefType` is clear
-- there is at least some confidence and one piece of supporting or weakening evidence
+- the emotional meaning of the sentence is clear enough to recognize later
 
 Preferred opening question:
 
@@ -411,6 +501,8 @@ Arc:
 5. Choose the mode family only after the lived description is clearer.
 6. Ask when it first became necessary or familiar.
 7. Ask what a healthier relationship to the mode would require.
+8. Offer one candidate formulation yourself when the user has the experience but not
+   the wording.
 
 Helpful follow-up lanes:
 
@@ -446,7 +538,9 @@ Arc:
 2. Ask what the part is feeling, saying, stopping, or pushing for.
 3. Ask what it fears and what it seems to need.
 4. Reflect the answers before suggesting interpretations.
-5. Offer one or two candidate mode labels only after enough evidence exists.
+5. Ask permission before moving from exploration into candidate labels if the material
+   still feels charged.
+6. Offer one or two candidate mode labels only after enough evidence exists.
 
 Helpful follow-up lanes:
 
@@ -480,11 +574,13 @@ Arc:
 
 1. Anchor the report in one specific episode.
 2. Ask what happened as concretely as possible.
-3. Ask what emotions, thoughts, and body signals showed up.
-4. Ask what the user did next and what happened after.
-5. Ask what helped short term and what the consequences were later.
-6. Ask what pattern, belief, mode, or value seems most active here.
-7. Ask what would help next time only after the episode itself is clear.
+3. If the episode still feels hot or confusing, stay with one slice before trying to
+   cover the whole chain.
+4. Ask what emotions, thoughts, and body signals showed up.
+5. Ask what the user did next and what happened after.
+6. Ask what helped short term and what the consequences were later.
+7. Ask what pattern, belief, mode, or value seems most active here.
+8. Ask what would help next time only after the episode itself is clear.
 
 Helpful follow-up lanes: