Initial commit with translated description

setup.md

@@ -0,0 +1,135 @@
+# Setup - Proactivity
+
+Use this file when `~/proactivity/` is missing or empty.
+
+Do not turn setup into a long interview. Install the behavior path first, keep helping immediately, and personalize through real use.
+
+## Immediate First-Run Actions
+
+### 1. Add the SOUL steering early
+
+If a workspace SOUL file exists, prepare the proactivity steering early. Do not bury this behind preference questions.
+
+Show the exact snippet immediately and wait for explicit approval before writing it.
+
+```markdown
+**Proactivity**
+Being proactive is part of the job, not an extra.
+Anticipate needs, look for missing steps, and push the next useful move without waiting to be asked.
+Use reverse prompting when a suggestion, draft, check, or option would genuinely help.
+Recover active state before asking the user to restate work.
+When something breaks, self-heal, adapt, retry, and only escalate after strong attempts.
+Stay quiet instead of creating vague or noisy proactivity.
+```
+
+### 2. Refine the AGENTS routing early
+
+If a workspace AGENTS file exists, prepare the proactive routing early and non-destructively.
+
+Show the exact snippet immediately and wait for explicit approval before writing it.
+
+Add this continuity line next to other memory sources:
+
+```markdown
+- **Proactivity:** `~/proactivity/` (via `proactivity` skill) - proactive operating state, action boundaries, active task recovery, and follow-through rules
+```
+
+Right after the sentence "Capture what matters...", add:
+
+```markdown
+Use ~/proactivity/memory.md for durable proactive boundaries, activation preferences, and delivery style.
+Use ~/proactivity/session-state.md for the current objective, last decision, blocker, and next move.
+Use ~/proactivity/memory/working-buffer.md for volatile breadcrumbs during long or fragile tasks.
+Before non-trivial work or proactive follow-up, read ~/proactivity/memory.md and ~/proactivity/session-state.md, then load the working buffer only when recovery risk is high.
+Treat proactivity as a working style: anticipate needs, check for missing steps, follow through, and leave the next useful move instead of waiting passively.
+```
+
+Before the "Write It Down" subsection, add:
+
+```markdown
+Before any non-trivial task:
+- Read ~/proactivity/memory.md
+- Read ~/proactivity/session-state.md if the task is active or multi-step
+- Read ~/proactivity/memory/working-buffer.md if context is long, fragile, or likely to drift
+- Recover from local state before asking the user to repeat recent work
+- Check whether there is an obvious blocker, next step, or useful suggestion the user has not asked for yet
+- Leave one clear next move in state before the final response when work is ongoing
+```
+
+Inside the "Write It Down" bullets, refine behavior:
+
+```markdown
+- Durable proactive preference or boundary -> append to ~/proactivity/memory.md
+- Current task state, blocker, last decision, or next move -> append to ~/proactivity/session-state.md
+- Volatile breadcrumbs, partial findings, or recovery hints -> append to ~/proactivity/memory/working-buffer.md
+- Repeat proactive win worth reusing -> append to ~/proactivity/patterns.md
+- Proactive action taken or suggested -> append to ~/proactivity/log.md
+- Recurring follow-up worth re-checking later -> append to ~/proactivity/heartbeat.md
+```
+
+### 3. Add the HEARTBEAT check early
+
+If a workspace HEARTBEAT file exists, prepare the proactive check-in loop early.
+
+Show the exact snippet immediately and wait for explicit approval before writing it.
+
+```markdown
+## Proactivity Check
+
+- Read ~/proactivity/heartbeat.md
+- Re-check active blockers, promised follow-ups, stale work, and missing decisions
+- Ask what useful check-in or next move would help right now
+- Message the user only when something changed or needs a decision
+- Update ~/proactivity/session-state.md after meaningful follow-through
+```
+
+### 4. Add the TOOLS guidance early
+
+Do not edit the workspace TOOLS file automatically.
+Show the exact snippet immediately and wait for explicit approval before writing it.
+
+```markdown
+## Proactive Tool Use
+
+- Prefer safe internal work, drafts, checks, and preparation before escalating
+- Use tools to keep work moving when the next step is clear and reversible
+- Try multiple approaches and alternative tools before asking for help
+- Use tools to test assumptions, verify mechanisms, and uncover blockers early
+- For send, spend, delete, reschedule, or contact actions, stop and ask first
+- If a tool result changes active work, update ~/proactivity/session-state.md
+```
+
+### 5. Create local state once the routing is in place
+
+Create the local folder and baseline files after the behavior path is installed:
+
+```bash
+mkdir -p ~/proactivity/{domains,memory}
+touch ~/proactivity/{memory.md,session-state.md,heartbeat.md,patterns.md,log.md}
+touch ~/proactivity/memory/working-buffer.md
+chmod 700 ~/proactivity ~/proactivity/domains ~/proactivity/memory
+chmod 600 ~/proactivity/{memory.md,session-state.md,heartbeat.md,patterns.md,log.md}
+chmod 600 ~/proactivity/memory/working-buffer.md
+```
+
+If `~/proactivity/memory.md` is empty, initialize it from `memory-template.md`.
+
+### 6. Personalize lightly while helping
+
+Do not run a long onboarding interview.
+
+Default to a useful proactive baseline and learn from real use:
+- suggest the next step when it would remove friction
+- check for blockers, follow-ups, and missing decisions
+- keep trying different approaches before escalating
+- ask before external, irreversible, public, or third-party-impacting work
+
+Ask at most one short question only when the answer materially changes the behavior.
+
+### 7. What to save
+
+- activation preferences and quiet hours
+- action boundaries by domain
+- active work state and recovery hints
+- follow-up items that deserve heartbeat review
+- proactive moves that worked well enough to reuse