← Back to list

secondbrain-task
by sergio-bershadsky
⭐ 3🍴 0📅 Jan 17, 2026
SKILL.md
name: secondbrain-task description: | This skill should be used when the user asks to "create task", "add todo", "track action item", "create ticket", "new task", "remind me to", "need to do", "add to backlog", or mentions needing to track work items with priority and status in their secondbrain.
Create Task
Create tracked tasks with priority, due dates, and status workflow.
Prerequisites
Verify Tasks entity is enabled:
- Check for
.claude/data/tasks/records.yaml - If not found, suggest enabling tasks via
secondbrain-initorsecondbrain-entity
Workflow
Step 1: Gather Information
Collect from user or conversation context:
- Title — Brief task description
- Description (optional) — Detailed description
- Priority — low, medium, high, critical
- Due Date (optional) — Target completion date
- Assignee (optional) — Person responsible
Step 2: Generate Task Number
Sequential ID format: TASK-XXXX (zero-padded)
- Load
.claude/data/tasks/records.yaml - Get
last_number, increment by 1 - Format as
TASK-0042
Step 3: Create Task Record
Add to .claude/data/tasks/records.yaml:
- number: 42
title: "Implement user authentication"
description: "Add OAuth2 login flow"
status: todo
priority: high
created: 2026-01-15
due_date: 2026-01-31
assignee: sergey
tags: [auth, security]
Update last_number: 42
Step 4: Create Task Document (Optional)
For complex tasks, create a document:
Filename: docs/tasks/TASK-0042-implement-authentication.md
---
id: TASK-0042
title: Implement user authentication
status: todo
priority: high
created: 2026-01-15
due_date: 2026-01-31
assignee: sergey
tags: [auth, security]
---
# TASK-0042: Implement user authentication
## Description
Add OAuth2 login flow for the application.
## Acceptance Criteria
- [ ] OAuth2 provider configuration
- [ ] Login redirect flow
- [ ] Token storage
- [ ] Logout functionality
## Notes
Implementation notes here...
Step 5: Confirm Creation
## Task Created
**ID:** TASK-0042
**Title:** Implement user authentication
**Priority:** high
**Due:** 2026-01-31
**Status:** todo
### Next Steps
- Update status as work progresses
- Add notes to the task document
- Mark complete when done
Status Workflow
todo → in_progress → done
↓
blocked → in_progress
↓
canceled
| Status | Description |
|---|---|
| todo | Not started |
| in_progress | Work in progress |
| blocked | Waiting on dependency |
| done | Completed |
| canceled | Won't be done |
Priority Levels
| Priority | Use When |
|---|---|
| critical | Urgent, blocks other work |
| high | Important, should be done soon |
| medium | Normal priority |
| low | Nice to have, no rush |
Additional Resources
references/task-workflows.md— Detailed task lifecycle, priority guidelines, and workflow patterns
Tips
- Keep titles actionable — Start with a verb (Implement, Fix, Add)
- Set realistic due dates — Better to underpromise
- Update status promptly — Keeps the backlog accurate
- Use tags — Helps filter and group related tasks
- Add acceptance criteria — Makes "done" unambiguous
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon