47a8b40fdb
TREE(74): training modules, entity profiles, 2890 references, keyword indices SPROUT(42): knowledge pages, project docs, curated source material SEED(164): daily notes, raw session logs, unprocessed material Updated AUDIT_MANIFEST.json with growth classifications.
3.0 KiB
3.0 KiB
pageType, id, title, sourceType, sourcePath, ingestedAt, updatedAt, status, growth
| pageType | id | title | sourceType | sourcePath | ingestedAt | updatedAt | status | growth |
|---|---|---|---|---|---|---|---|---|
| source | source.tasks-channel-guide | tasks-channel-guide | local-file | /home/topher/.openclaw/workspace-2890-bot/docs/tasks-channel-guide.md | 2026-05-02T21:24:08.799Z | 2026-05-02T21:24:08.799Z | active | seed |
tasks-channel-guide
Source
- Type:
local-file - Path:
/home/topher/.openclaw/workspace-2890-bot/docs/tasks-channel-guide.md - Bytes: 2388
- Updated: 2026-05-02T21:24:08.799Z
Content
# 🦅 Team 2890 — Task Board Guide
Welcome to the **#tasks** channel! This is where Team 2890 tracks what we're working on. It's dead simple — here's how to use it.
---
## ✅ The Golden Rule
**If you're working on something, it goes on the board.** If it's done, it moves to Done. No exceptions — the board only works if it reflects reality.
---
## 🧱 The Board Lanes
| Lane | Meaning |
|------|---------|
| **Backlog** | Needs to be done, not actively being worked |
| **In Progress** | Someone is actively working on it right now |
| **Review** | Done but needs someone else to check it |
| **Done** | Verified complete, ship it |
---
## ⚡ Quick Command Reference
### Adding a Task
```
!task add Fix the shooter lock jitter $programming $urgent
!task add Order replacement swerve modules $parts
```
The bot will ask you which lane if you don't specify.
### Moving a Task
```
!task done <task-id> ← moves to Done
!task move <task-id> → in-progress ← moves to a lane
```
### Viewing the Board
```
!task list ← shows all lanes at a glance
!task list in-progress ← shows just that lane
!task <task-id> ← shows full details of one card
```
### Sprint Digest
```
!board post ← bot posts live board summary (pinned)
!standup start ← opens a standup thread
```
---
## 📋 Task Anatomy
A good task has:
- **A specific thing to do** — "Fix" not "maybe fix someday"
- **A #tag** — programming / electrical / mechanical / parts / scouting / docs
- **A person** — you (the author) are auto-assigned
Bad: "work on shooter"
Good: "Fix shooter lock jitter — investigate command timing delays $programming"
---
## 💡 Formatting Tips
- **Priority** auto-detected from $urgent (high), $low (low), or leave it (medium)
- **Your name** is captured from your Discord username automatically
- **No task ID?** Use `!task list` to find the ID, or just ask the bot "what are we working on?"
---
## 🚫 Don't
- Don't post tasks as plain text without `!task` — the bot won't track them
- Don't assign tasks to people who aren't here
- Don't put everything in Backlog — if someone's actively working it, it should be **In Progress**
- Don't close a task until it's actually verified done
---
## 🎯 Got Questions?
Ask in the channel and the bot or any mentor will help you out.
Notes
Related
- No related pages yet.