| name | work |
| description | Work with tasks: view ready, pick, execute with Context7 docs, close. Full lifecycle with MCP documentation lookup. |
| version | 1.0.0 |
Work with Tasks
Skill для работы с задачами: просмотр, выбор, выполнение с обязательным использованием Context7 для актуальной документации.
Usage
Invoke via: /work or "покажи задачи" or "что делать"
Optional arguments:
/work — показать готовые задачи (default: 20)/work -n 50 — показать больше задач/work -l frontend — только frontend задачи/work pick — автовыбор задачи по приоритету/work defer buh-xxx +3m — отложить задачу на 3 месяца/work deferred — показать отложенные задачи
CRITICAL: Context7 MCP — MANDATORY
Before implementing ANY task, query Context7 for up-to-date documentation on involved libraries.
Skip only for trivial changes that don't touch library APIs (typos, comments, config values).
How to use (2-step)
1. mcp__context7__resolve-library-id — resolve library name to ID
2. mcp__context7__query-docs — query docs by resolved ID + topic
When delegating to subagents — fetch docs first, include in delegation context.
Step 1: Show Ready Tasks
Показать готовые задачи:
LIMIT="${1:--n 20}"
bd ready $LIMIT 2>/dev/null | head -30
echo ""
echo "---"
TOTAL=$(bd ready -n 100 2>/dev/null | wc -l)
echo "Total ready: $TOTAL tasks"
If no tasks:
No ready tasks found.
Options:
1. /process-issues — import from GitHub Issues
2. bd create --title='Task title' --type=task --priority=2 — create manually
Step 2: Task Selection Workflow
Option A: User Selects Task
User says: "возьми buh-xxx" or provides task ID
bd show buh-xxx
bd update buh-xxx --status in_progress
Option B: Auto-Pick by Priority
User says: /work pick or "выбери задачу"
TASK=$(bd ready -n 1 --sort priority 2>/dev/null | head -1 | grep -oP 'buh-[a-z0-9]+')
if [ -n "$TASK" ]; then
echo "Selected: $TASK"
bd show $TASK
bd update $TASK --status in_progress
else
echo "No tasks available"
fi
Step 3: Working on Task
Rules
- Read task description before starting
- Query Context7 for any libraries involved (MANDATORY)
- Gather context — read related files, understand scope
- Delegate to subagent if complex (see AGENTS.md), include Context7 docs in delegation
- Verify changes — type-check, build
- Close task when done
Execution Pattern
1. bd show buh-xxx — read full description
2. Context7: resolve + query — get docs for involved libraries (MANDATORY)
3. Gather context — read files, search codebase
4. Implement — delegate or execute directly
5. Verify — npm run type-check && npm run build
6. bd close buh-xxx — mark complete
7. git commit && git push — commit changes
Context7 in delegation (MANDATORY)
When delegating to subagents, ALWAYS include Context7 docs:
Task: Fix/implement <description>
Issue: <title>
Context7 Documentation:
<paste relevant docs fetched from Context7 here>
Files to modify:
- <path1>: <what to change>
- <path2>: <what to change>
Validation: Run `npm run type-check` after changes
Subagent Selection
| Domain | Subagent | When |
|---|
| DB/migrations | database-architect | Schema changes, RLS |
| UI components | nextjs-ui-designer | New pages, components |
| Backend services | fullstack-nextjs-specialist | APIs, workers, services |
| Telegram bot | telegraf-bot-middleware-specialist | Bot handlers, middleware |
| SLA/monitoring | sla-backend-specialist | SLA timers, alerts |
| TypeScript types | typescript-types-specialist | Complex types, generics |
| Bug investigation | problem-investigator | Complex root cause |
| Security | vulnerability-fixer | Auth, XSS, injection |
| Performance | performance-optimizer | Slow queries, rendering |
Step 4: Closing Task
bd close buh-xxx --reason="Fixed: description of what was done"
GITHUB_REF=$(bd show buh-xxx 2>/dev/null | grep -oP 'external-ref.*gh-\K[0-9]+' | head -1)
if [[ -n "$GITHUB_REF" ]]; then
gh issue close $GITHUB_REF --comment "Fixed in Beads task buh-xxx"
fi
Integration with /process-issues
When no local tasks → suggest importing from GitHub:
User: /work
Codex: No ready tasks.
Options:
1. /process-issues — Check GitHub for new issues
2. bd create --title="..." --type=task --priority=2 — Create task manually
User: /process-issues
Codex: [Processes GitHub issues, creates Beads tasks with external-ref]
User: /work
Codex: Found 3 ready tasks:
1. [P1] buh-abc: Fix auth bug (gh-45)
2. [P2] buh-def: Add feature X (gh-52)
...
Task Sources
| Source | How to Create | External Ref |
|---|
| GitHub Issue | /process-issues | gh-123 |
| Manual | bd create --title="Title" --type=task --priority=2 | none |
| Emergent (found at work) | bd create --title="Found bug" --type=bug --deps discovered-from:buh-x | none |
Defer Tasks (Откладывание)
Отложенные задачи скрыты из bd ready до указанной даты.
Отложить задачу
bd update buh-xxx --defer "+1w"
bd update buh-xxx --defer "+2w"
bd update buh-xxx --defer "+3m"
bd update buh-xxx --defer "2026-03-01"
bd update buh-xxx --defer "next monday"
bd update buh-xxx --defer ""
Массовое откладывание
for id in buh-aaa buh-bbb buh-ccc; do
bd update $id --defer "+3m"
done
Посмотреть отложенные
bd ready --include-deferred
Quick Reference
bd ready -n 20
bd list --status=in_progress
bd show buh-xxx
bd update buh-xxx --status in_progress
bd close buh-xxx --reason="..."
bd create --title="Title" --type=task --priority=2
bd create --title="Bug" --type=bug --priority=1 --external-ref="gh-99"
bd ready -l frontend
bd ready -l backend
bd update buh-xxx --defer "+3m"
bd update buh-xxx --defer ""
bd ready --include-deferred
Verification Checklist
Before closing any task:
