feat: add daily-routine skill and role definitions
daily-routine skill: - plan-schedule: daily planning workflow (review workload, create slots, coordinate with other agents) - task-handson: task execution workflow (acknowledge slot, find right skill workflow, execute) - slot-complete: post-slot workflow (record results, check overdue, defer or pick next) Role definitions (6 roles): - developer, manager, operator, mentor, secretary, agent-resource-director - Each defines responsibilities, capabilities, boundaries, escalation rules, and memory practice Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
71
daily-routine/workflows/plan-schedule.md
Normal file
71
daily-routine/workflows/plan-schedule.md
Normal file
@@ -0,0 +1,71 @@
|
||||
# Plan Schedule
|
||||
|
||||
When woken up for daily planning (typically 01:00 UTC). You receive your suggested workload for the day.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Review Suggested Workload
|
||||
|
||||
Read the suggested workload provided in your wakeup message. This includes:
|
||||
- Number of oncall slots to schedule
|
||||
- Number of task slots to schedule
|
||||
|
||||
This was designed by agent-resource-director for your specific role and capacity.
|
||||
|
||||
### 2. Review Existing Schedule
|
||||
|
||||
Check if any slots have already been planned for today:
|
||||
|
||||
```bash
|
||||
hf calendar show --date today
|
||||
```
|
||||
|
||||
### 3. Review Pending Tasks
|
||||
|
||||
List tasks assigned to you or that you've claimed:
|
||||
|
||||
```bash
|
||||
hf tasks list --assignee me --status open
|
||||
```
|
||||
|
||||
### 4. Plan Slots
|
||||
|
||||
Create slots for today. Distribute them within the work period:
|
||||
|
||||
```bash
|
||||
hf calendar slot create --type work --time HH:MM --duration <min> --event-data '{"task_id": <id>}'
|
||||
hf calendar slot create --type oncall --time HH:MM --duration <min>
|
||||
```
|
||||
|
||||
For each task slot, note which HF task you intend to work on.
|
||||
|
||||
### 5. Assess Collaboration Needs
|
||||
|
||||
Review your planned work — does any task require discussion with other agents?
|
||||
|
||||
If yes:
|
||||
- Check the shared daily planning channel
|
||||
- Propose discussion time with relevant agents
|
||||
- Agree on a time slot
|
||||
|
||||
### 6. Write Daily Plan to Memory
|
||||
|
||||
Append a brief summary to your daily note:
|
||||
|
||||
```
|
||||
memory/YYYY-MM-DD.md:
|
||||
## Daily Plan
|
||||
- N task slots, M oncall slots scheduled
|
||||
- Tasks to work on: [list]
|
||||
- Discussions planned: [list or none]
|
||||
```
|
||||
|
||||
### 7. Confirm Readiness
|
||||
|
||||
Once your schedule is submitted, you're done with planning. Set your status:
|
||||
|
||||
```bash
|
||||
hf agent status --set idle
|
||||
```
|
||||
|
||||
Wait for your first slot to be triggered by the wakeup mechanism.
|
||||
63
daily-routine/workflows/slot-complete.md
Normal file
63
daily-routine/workflows/slot-complete.md
Normal file
@@ -0,0 +1,63 @@
|
||||
# Slot Complete
|
||||
|
||||
When you have finished working on the current slot.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Record Results
|
||||
|
||||
Update the task status if applicable:
|
||||
|
||||
```bash
|
||||
hf tasks update --id <task_id> --status <completed|in-progress|blocked>
|
||||
```
|
||||
|
||||
Update the slot:
|
||||
|
||||
```bash
|
||||
hf calendar slot update --id <slot_id> --status finished
|
||||
```
|
||||
|
||||
### 2. Write to Memory
|
||||
|
||||
Append a brief work summary to your daily note (`memory/YYYY-MM-DD.md`):
|
||||
|
||||
```
|
||||
## Slot <slot_id> — <task summary>
|
||||
- What was done: ...
|
||||
- Key decisions: ...
|
||||
- Output: commit <hash>, PR #<num>, file <path>, etc.
|
||||
- Blockers: ... (if any)
|
||||
```
|
||||
|
||||
### 3. Check for Overdue Slots
|
||||
|
||||
Before going idle, check if there are overdue slots:
|
||||
|
||||
```bash
|
||||
hf calendar show --date today --status not-started
|
||||
```
|
||||
|
||||
For each overdue slot, decide:
|
||||
- **Defer**: reschedule to a later time today (if work period allows)
|
||||
- **Skip**: if no longer relevant
|
||||
|
||||
```bash
|
||||
hf calendar slot update --id <slot_id> --status deferred --time HH:MM
|
||||
```
|
||||
|
||||
### 4. Decide Next Action
|
||||
|
||||
If there are more ready slots within the work period:
|
||||
- Pick the highest priority one
|
||||
- Follow `task-handson` workflow for it
|
||||
- Do NOT set status to idle yet
|
||||
|
||||
If no more slots, or work period is ending:
|
||||
- Set status to idle:
|
||||
|
||||
```bash
|
||||
hf agent status --set idle
|
||||
```
|
||||
|
||||
Your session can end. You will be woken up again if new slots become due.
|
||||
55
daily-routine/workflows/task-handson.md
Normal file
55
daily-routine/workflows/task-handson.md
Normal file
@@ -0,0 +1,55 @@
|
||||
# Task Handson
|
||||
|
||||
When a task slot is due and you are woken up to work on it.
|
||||
|
||||
## Process
|
||||
|
||||
### 1. Acknowledge Slot
|
||||
|
||||
Set your status to busy:
|
||||
|
||||
```bash
|
||||
hf agent status --set busy
|
||||
```
|
||||
|
||||
Update the slot status:
|
||||
|
||||
```bash
|
||||
hf calendar slot update --id <slot_id> --status ongoing
|
||||
```
|
||||
|
||||
### 2. Identify the Task
|
||||
|
||||
Read the slot's event data to find the associated task:
|
||||
|
||||
```bash
|
||||
hf calendar slot show --id <slot_id>
|
||||
```
|
||||
|
||||
If the slot has an associated task_id, load the task details:
|
||||
|
||||
```bash
|
||||
hf tasks show --id <task_id>
|
||||
```
|
||||
|
||||
### 3. Find the Right Workflow
|
||||
|
||||
Based on the task type and your role, find the appropriate skill workflow:
|
||||
- Code implementation → your role's development workflow
|
||||
- Code review → git-hangman-lab PR review workflow
|
||||
- Deployment → operator deployment workflow
|
||||
- Skill maintenance → claw-skills improve/create workflow
|
||||
- Administrative → role-specific administrative workflow
|
||||
|
||||
If no specific workflow applies, work on the task directly using your tools and judgment.
|
||||
|
||||
### 4. Execute
|
||||
|
||||
Follow the identified workflow to completion. During execution:
|
||||
- Use appropriate tools for your task
|
||||
- Commit code changes with meaningful messages
|
||||
- Update task comments with progress if the work is substantial
|
||||
|
||||
### 5. Complete Slot
|
||||
|
||||
When done, follow the `slot-complete` workflow.
|
||||
Reference in New Issue
Block a user