update shutdown skill for examination of conscience
This commit is contained in:
parent
6d41e0596d
commit
3ea550ce8a
2 changed files with 45 additions and 7 deletions
|
|
@ -49,9 +49,22 @@ Then say:
|
|||
|
||||
Ask:
|
||||
|
||||
> "What's one thing you'd do differently if you had today over again?"
|
||||
> "Is there anything you could have done better today?"
|
||||
|
||||
Wait for a response. Acknowledge it briefly. No need to problem-solve or offer advice unless asked.
|
||||
If the user gives you an answer for what could have been improved, then add their reply to the user's journal with: `scripts/add_improvement_journal_entry "USER'S REPLY"`
|
||||
|
||||
If the user responds that nothing needed improvement from today, ask this follow-up question
|
||||
|
||||
> "How would you like to raise the bar?"
|
||||
|
||||
Then enter the user's reply into tomorrow's daily note. (filename dn_yymmdd.md where yymmdd is tomorrow's date)
|
||||
|
||||
Put their ansewr into this part of the file:
|
||||
```md
|
||||
# Today I *get* to
|
||||
raise the bar: USER'S REPLY
|
||||
## meetings
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -78,11 +91,6 @@ Take their input and create each task with `vik task create "Task title" d+1` so
|
|||
## Rules
|
||||
|
||||
- Never skip the victory lap. It's the most important step.
|
||||
- Keep the whole routine under 10 minutes. If a step is going long, gently redirect.
|
||||
- Don't create tasks beyond what Connor asks for. Just capture what he says.
|
||||
- Always end with the build/kaizen task. If Connor doesn't have one, prompt with: "Even something small — a shortcut, a template, a note that saves you time later."
|
||||
- Create tasks in Vikunja with `vik task create`, don't just echo them back.
|
||||
|
||||
---
|
||||
|
||||
*Customized in Video 7 via the assembler.*
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue