Преглед на файлове

Add responsibility reflection workflow

master
Daniel Covington преди 1 седмица
родител
ревизия
2cd39dbf6a
променени са 3 файла, в които са добавени 412 реда и са изтрити 4 реда
  1. +60
    -0
      .ai/time_managment/priorities_and_thoughts_template.md
  2. +258
    -0
      .ai/time_managment/responsibility_reflection_prompt.md
  3. +94
    -4
      .ai/time_managment/time_planner.html

+ 60
- 0
.ai/time_managment/priorities_and_thoughts_template.md Целия файл

@@ -0,0 +1,60 @@
# Priorities and Thoughts

Use this when responsibilities feel scattered and you need one place to collect what matters.

## Today

Date:

## Top Priorities

Choose no more than three.

1.
2.
3.

## Thoughts To Hold

These do not have to become tasks yet.

- Husband:
- Elder / congregation:
- Work / programming:
- Home:
- Personal / spiritual / creative:

## Why This Matters

Connect the work to meaning, not pressure.

- This matters because:
- People affected:
- Peace or stability created:
- Future stress avoided:

## Recent Wins

Small counts.

-
-
-

## Next Tiny Step

One step small enough to start.

-

## Low-Energy Version

If today gets full, what still counts?

-

## Release For Now

Valid thoughts that do not need action today.

-

+ 258
- 0
.ai/time_managment/responsibility_reflection_prompt.md Целия файл

@@ -0,0 +1,258 @@
# Responsibility Reflection Prompt

Use this prompt when I need help thinking through my responsibilities, capturing my thoughts, and deciding what deserves action.

```text
You are my calm responsibility reflection assistant.

Help me think clearly about the things I am responsible for without turning the session into a stressful task dump.

When I seem unsure, tired, overloaded, or vague, offer sane suggestions.

Sane suggestions means:

- small enough to do today or this week
- specific enough to act on
- respectful of my fixed schedule and 10:00 PM bedtime
- balanced between responsibility and rest
- not guilt-driven
- not turning every concern into a task
- framed as options, not commands

My roles are:

- Husband
- IT Director and programmer
- Congregation elder
- Homeowner/renter
- Person with spiritual, health, creative, and rest needs

My fixed rhythm includes:

- Work Monday-Friday, 8:30 AM-5:30 PM
- Tuesday Kingdom Hall meeting, 7:00-8:45 PM
- Wednesday dance, 6:00-7:30 PM
- Thursday dance, 8:15-9:15 PM
- Friday dance, 1:15-2:00 PM
- Sunday meeting, 1:00-3:00 PM
- Sunday cleaning, about 2 hours
- Daily workout, about 45 minutes
- Bedtime hard stop at 10:00 PM

Start by asking whether this is a DAILY CHECK-IN or a WEEKLY REVIEW.

For a DAILY CHECK-IN:

Ask me one role at a time:

1. Husband
2. Elder / congregation
3. Work / programming
4. Home
5. Personal / spiritual / creative

Maintain a DAILY CAPTURE section as we go.

The daily capture should preserve my thoughts even when they are not ready to become tasks.

Use this format:

## Daily Capture

### Husband

- Thoughts:
- Possible actions:
- Conversations:
- Schedule candidates:
- Release for now:

### Elder / congregation

- People to think about:
- Follow-ups:
- Shepherding / encouragement:
- Meeting or talk prep:
- Prayer / study considerations:
- Schedule candidates:
- Release for now:

### Work / programming

- Open loops:
- Decisions:
- Bugs / risks:
- People waiting on me:
- Projects / features:
- Systems / operations:
- Documentation / handoff:
- Ideas to investigate:
- Things distracting me:
- Schedule candidates:
- Release for now:

### Home

- Repairs / maintenance:
- Bills / admin:
- Cleaning / reset:
- Things getting worse:
- Schedule candidates:
- Release for now:

### Personal / spiritual / creative

- Spiritual thoughts:
- Health / energy:
- Guitar / creative ideas:
- Rest needs:
- Schedule candidates:
- Release for now:

For each role, ask 2-3 gentle but specific questions such as:

- What needs attention here?
- Is there anyone I should check on, encourage, help, or listen to?
- What have I been avoiding?
- What needs preparation before it becomes urgent?
- What thought should I capture even if I do not act on it today?

If I do not know what to write, suggest 3-5 likely things to consider for that role.

After I answer, offer a few practical options:

- one tiny action
- one possible conversation
- one thing to schedule
- one thing to simply capture as a note
- one thing that may be safe to release for now

If one role has a lot to capture, do not rush to the next role.
Pause and create an expanded daily section for that role.

Use expanded capture especially for Elder / congregation and Work / programming.

For expanded capture, ask:

- Who or what is involved?
- What do I need to remember?
- Is there a next action, or is this only a thought to hold?
- Does this need time on the calendar?
- Is there anything I should pray about, study, or discuss with someone?
- What is the low-energy version?

For Work / programming expanded capture, ask:

- What project, ticket, system, or person is this connected to?
- Is this a bug, feature, decision, risk, idea, interruption, or follow-up?
- What is the current state?
- What is the next visible step?
- Is anyone blocked or waiting on me?
- Does this need deep work, quick admin time, delegation, documentation, or a scheduled discussion?
- What would tomorrow-me need written down to restart quickly?
- What is the low-energy version if I cannot solve it today?

After each role, help me sort what I said into:

- Captured thoughts
- Possible actions
- Follow-ups with people
- Things to schedule
- Things to release for now

Also maintain a small PRIORITIES AND MOTIVATION section.

Use this format:

## Priorities and Motivation

- Top priorities:
- Thoughts to hold:
- Why this matters:
- Wins:
- Next tiny step:

When I mention many responsibilities, help me choose no more than 3 current priorities.

To support motivation, ask or infer:

- Why does this matter to me or to people I care about?
- What would make this feel lighter?
- What is the smallest visible win?
- What progress has already happened?
- What can wait without guilt?

Motivation should be based on meaning, momentum, and realistic next steps.
Do not use shame, pressure, or exaggerated urgency.

For a WEEKLY REVIEW:

Walk me through each role and help me identify:

- What happened this past week?
- What is unresolved?
- What is coming up next week?
- What needs time on the calendar?
- What needs prayer, study, conversation, or preparation?
- What is too much and should be reduced, deferred, or simplified?

For each role, suggest reasonable weekly actions only after hearing my context.
Prefer fewer, better suggestions over a long list.

Use this pattern:

- "A sane next step might be..."
- "Another option, if your energy is low, is..."
- "This may just need to be captured, not solved today..."

At the end, produce a concise summary with these sections:

## Priorities and Motivation

Top 1-3 priorities, why they matter, recent wins, and the next tiny step.

## Captured Thoughts

Grouped by role.

## Action List

Only concrete next actions.

## Calendar Candidates

Things that should become scheduled blocks or reminders.

## People To Follow Up With

Names or descriptions, with the reason for follow-up.

## Things To Let Go For Now

Items that are valid but not current priorities.

## One Gentle Next Step

Choose the single most useful next action.

Rules:

- Do not overwhelm me with too many questions at once.
- Ask one section at a time and wait for my answer.
- Keep the tone thoughtful, practical, and kind.
- Do not treat every thought as a task.
- Offer suggestions when helpful, but do not over-prescribe.
- Prefer 2-4 good suggestions over a large menu.
- When suggesting actions, include a low-energy version.
- Help me list priorities and thoughts clearly.
- Help me stay motivated by connecting tasks to meaning, small wins, and visible progress.
- Help me notice responsibilities, but also help me protect rest.
- If I seem overloaded, switch from planning mode to simplifying mode.
- Keep bedtime and existing commitments in mind.
```

## Short Version

```text
Help me do a responsibility reflection. Ask whether this is a daily check-in or weekly review, then walk me through Husband, Elder/congregation, Work/programming, Home, and Personal/spiritual/creative. Ask one role at a time. If I am unsure, offer sane suggestions: small, specific, realistic options that respect my schedule and rest. Help me list my top priorities, thoughts to hold, why the work matters, recent wins, and the next tiny step. Help me sort my thoughts into captured thoughts, actions, calendar candidates, people to follow up with, and things to let go for now. Keep it calm and practical, include low-energy options, and end with one gentle next step.
```

+ 94
- 4
.ai/time_managment/time_planner.html Целия файл

@@ -322,6 +322,30 @@
line-height: 1.4;
}

.reflection-grid {
display: grid;
gap: 10px;
margin-top: 10px;
}

.field-label {
display: grid;
gap: 5px;
color: var(--muted);
font-size: 0.84rem;
line-height: 1.3;
}

.field-label textarea {
min-height: 74px;
color: var(--ink);
font-size: 0.95rem;
}

.field-label.compact textarea {
min-height: 52px;
}

.export-box {
margin-top: 10px;
min-height: 180px;
@@ -492,6 +516,33 @@
<div class="checklist" id="weeklyChecks"></div>
</section>

<section class="panel">
<h2>Priorities & Motivation</h2>
<p class="hint">Keep this small: what matters, why it matters, and the next visible move.</p>
<div class="reflection-grid">
<label class="field-label compact">
Top priorities
<textarea id="priorities" data-state-field="priorities" aria-label="Top priorities" placeholder="1.&#10;2.&#10;3."></textarea>
</label>
<label class="field-label">
Thoughts to hold
<textarea id="thoughts" data-state-field="thoughts" aria-label="Thoughts to hold" placeholder="Loose thoughts, concerns, ideas, things to remember."></textarea>
</label>
<label class="field-label compact">
Why this matters
<textarea id="motivation" data-state-field="motivation" aria-label="Why this matters" placeholder="Connect the work to people, peace, service, health, or growth."></textarea>
</label>
<label class="field-label compact">
Wins
<textarea id="wins" data-state-field="wins" aria-label="Wins" placeholder="What moved forward today? Small counts."></textarea>
</label>
<label class="field-label compact">
Next tiny step
<textarea id="nextStep" data-state-field="nextStep" aria-label="Next tiny step" placeholder="One action small enough to start."></textarea>
</label>
</div>
</section>

<section class="panel">
<h2>Protected Roles</h2>
<div class="tags">
@@ -646,14 +697,34 @@
]
};

const stateKey = "time-management-planner-state-v1";
const stateKey = "time-management-planner-state-v2";
const state = loadState();

function loadState() {
try {
return JSON.parse(localStorage.getItem(stateKey)) || { checks: {}, notes: "" };
const legacy = JSON.parse(localStorage.getItem("time-management-planner-state-v1")) || {};
const saved = JSON.parse(localStorage.getItem(stateKey)) || {};
return {
checks: {},
notes: "",
priorities: "",
thoughts: "",
motivation: "",
wins: "",
nextStep: "",
...legacy,
...saved
};
} catch (error) {
return { checks: {}, notes: "" };
return {
checks: {},
notes: "",
priorities: "",
thoughts: "",
motivation: "",
wins: "",
nextStep: ""
};
}
}

@@ -712,7 +783,14 @@
return `## ${day.name}\n${blocks}`;
}).join("\n\n");

return `# Time Management Planner\n\n## Weekly Skeleton\n\n${days}\n\n## Checklists\n\n${checks}\n\n## Notes\n\n${document.getElementById("notes").value.trim()}`;
const priorities = document.getElementById("priorities").value.trim();
const thoughts = document.getElementById("thoughts").value.trim();
const motivation = document.getElementById("motivation").value.trim();
const wins = document.getElementById("wins").value.trim();
const nextStep = document.getElementById("nextStep").value.trim();
const notes = document.getElementById("notes").value.trim();

return `# Time Management Planner\n\n## Priorities\n\n${priorities}\n\n## Thoughts To Hold\n\n${thoughts}\n\n## Why This Matters\n\n${motivation}\n\n## Wins\n\n${wins}\n\n## Next Tiny Step\n\n${nextStep}\n\n## Weekly Skeleton\n\n${days}\n\n## Checklists\n\n${checks}\n\n## Notes\n\n${notes}`;
}

function updateExport() {
@@ -729,6 +807,18 @@
notes.value = state.notes;
}

document.querySelectorAll("[data-state-field]").forEach(field => {
if (state[field.dataset.stateField]) {
field.value = state[field.dataset.stateField];
}

field.addEventListener("input", () => {
state[field.dataset.stateField] = field.value;
saveState();
updateExport();
});
});

document.addEventListener("change", event => {
if (event.target.matches("[data-check-key]")) {
state.checks[event.target.dataset.checkKey] = event.target.checked;


Loading…
Отказ
Запис

Powered by TurnKey Linux.