Clawlist - Task Mastery
A systematic workflow for planning, executing, and tracking any task — from one-off projects to infinite monitoring loops.
When to Use This Skill
ALWAYS use clawlist when:
- - Starting any new project or initiative
- Setting up long-running monitoring
- Breaking down complex goals
- You need to track progress across sessions
- Managing infinite tasks (research, monitoring, engagement)
Long-Running & Infinite Task Examples
Example: Moltbook Engagement (Infinite)
- - Type: Infinite loop
- Schedule: Every 30 minutes
- Goal: Engage with community, build presence
- Checkpoints: Check feed, check DMs, create content
Example: GitHub Monitoring (Long-Running)
- - Type: Continuous
- Schedule: Every 4 hours
- Goal: Monitor repos, triage issues, implement
- Checkpoints: Inbox zero, PR review, implementation
The Clawlist Workflow
Uses standalone skills in sequence:
- 1. brainstorming → Clarify intent, explore approaches
- write-plan → Create detailed plan with checkpoints
- doing-tasks → Execute with skill discipline
- verify-task → Confirm completion
For parallel work, insert dispatch-multiple-agents between write-plan and doing-tasks.
Ongoing Tasks File
Location: INLINECODE0
Tracks all long-running and infinite tasks. Updated by heartbeat to:
- - Check task health
- Detect blockers
- Execute due tasks
- Summarize status
Task Types
| Type | Duration | Tracking | Example |
|---|
| One-off | Minutes-hours | Context only | Fix a bug |
| Project |
Days-weeks | Context + completion doc | Build feature |
|
Long-running | Ongoing |
ongoing-tasks.md | GitHub monitoring |
|
Infinite | Forever |
ongoing-tasks.md | Moltbook engagement |
Integration with Heartbeat
Heartbeat reads ongoing-tasks.md every check to:
- - Execute due infinite tasks
- Detect and report blockers
- Update health status (🟢🟡🔴)
- Ping user if intervention needed
Quick Reference
CODEBLOCK0
Sub-Skills
- - brainstorming - Phase 1: Clarify
- write-plan - Phase 2: Plan
- doing-tasks - Phase 3: Execute
- dispatch-multiple-agents - Parallel execution
- verify-task - Phase 4: Verify
技能名称: clawlist
详细描述:
Clawlist - 任务精通
一个系统化的工作流程,用于规划、执行和跟踪任何任务——从一次性项目到无限监控循环。
何时使用此技能
在以下情况下始终使用 clawlist:
- - 启动任何新项目或计划时
- 设置长期运行的监控时
- 分解复杂目标时
- 需要跨会话跟踪进度时
- 管理无限任务(研究、监控、互动)时
长期运行与无限任务示例
示例:Moltbook 互动(无限)
- - 类型: 无限循环
- 计划: 每 30 分钟
- 目标: 与社区互动,建立存在感
- 检查点: 查看信息流、查看私信、创建内容
示例:GitHub 监控(长期运行)
- - 类型: 持续进行
- 计划: 每 4 小时
- 目标: 监控仓库、分类问题、实施
- 检查点: 收件箱清零、PR 审查、实施
Clawlist 工作流程
按顺序使用独立技能:
- 1. brainstorming → 明确意图,探索方法
- write-plan → 创建包含检查点的详细计划
- doing-tasks → 以技能纪律执行
- verify-task → 确认完成
对于并行工作,在 write-plan 和 doing-tasks 之间插入 dispatch-multiple-agents。
持续任务文件
位置: memory/tasks/ongoing-tasks.md
跟踪所有长期运行和无限任务。由心跳更新以:
- - 检查任务健康状态
- 检测阻塞项
- 执行到期任务
- 总结状态
任务类型
| 类型 | 持续时间 | 跟踪方式 | 示例 |
|---|
| 一次性 | 分钟-小时 | 仅上下文 | 修复一个 Bug |
| 项目 |
天-周 | 上下文 + 完成文档 | 构建功能 |
|
长期运行 | 持续进行 | ongoing-tasks.md | GitHub 监控 |
|
无限 | 永久 | ongoing-tasks.md | Moltbook 互动 |
与心跳集成
心跳每次检查时读取 ongoing-tasks.md 以:
- - 执行到期的无限任务
- 检测并报告阻塞项
- 更新健康状态(🟢🟡🔴)
- 如需干预则通知用户
快速参考
新任务
↓
brainstorming → write-plan → doing-tasks → verify-task
↓
dispatch-multiple-agents(如果并行)
↓
更新 ongoing-tasks.md(如果长期运行)
子技能
- - brainstorming - 阶段 1:明确
- write-plan - 阶段 2:规划
- doing-tasks - 阶段 3:执行
- dispatch-multiple-agents - 并行执行
- verify-task - 阶段 4:验证