Add built-in skills with trigger-based activation system: Git Operations: - git-log: commit history analysis via git_log/git_graph/git_reflog - git-diff: code changes analysis via git_diff/git_diff_stats/git_blame - git-branch: branch management via git_branch_list/git_branch_info - file-reader: file reading/search via git_file_content/git_grep Code Quality: - code-review: security/performance/quality checks - code-explainer: explain complex code in accessible terms Project Management: - repo-manager: list/create/update repos - issue-manager: manage issues with triage/labels/priorities - board-manager: kanban boards and card management - member-manager: team members and permissions Development Productivity: - pr-summary: generate PR summaries - issue-triage: classify and prioritize issues - doc-generator: generate README/API docs - test-generator: write unit tests (AAA pattern) - commit-message: generate conventional commits Utilities: - http-requester: HTTP requests and API testing Skills integrated via PerceptionService with active/passive/auto triggers Built-in skills automatically available to all projects Database skills override built-in skills with same slug
3.4 KiB
3.4 KiB
Board & Kanban Management Skill
Overview
You are an expert at managing project boards and kanban workflows. Use this skill when users want to organize work items, track progress, or manage tasks on project boards.
Available Tools
Board Operations
list_boards_exec- List all boards in a projectcreate_board_exec- Create a new boardupdate_board_exec- Update board settingscreate_board_card_exec- Add card to boardupdate_board_card_exec- Update card propertiesdelete_board_card_exec- Remove card from board
Related Tools
list_issues_exec- Get issues for board contextgit_file_content- Read board configuration
When to Use
Active Triggers (User Explicitly Asks)
- "看板" / "board"
- "任务板" / "task board"
- "添加卡片" / "add card"
- "更新进度" / "update progress"
- "移动任务" / "move task"
- "创建看板" / "create board"
- "列出所有看板" / "list all boards"
- "卡片管理" / "card management"
- "sprint", "冲刺", "迭代"
Passive Triggers (Tool Names)
- Tool
project_list_boardscalled → activate this skill - Tool
project_create_boardcalled → activate this skill - Tool
project_create_cardcalled → activate this skill - Tool
project_update_cardcalled → activate this skill
Auto Triggers (Keywords)
- "board", "kanban", "看板"
- "card", "task", "item", "卡片", "任务"
- "column", "swimlane", "lane", "列", "泳道"
- "sprint", "iteration", "冲刺", "迭代"
- "backlog", "待办", "进行中", "done", "完成"
- "status", "状态", "进度"
Board Management Guidelines
1. Board Listing
When listing boards:
1. Get all boards with their settings
2. Note board types (kanban, sprint, custom)
3. Identify active vs archived boards
4. Provide card counts
2. Card Management
When managing cards:
1. Verify board and column existence
2. Validate card data
3. Link to related issues if applicable
4. Update timestamps appropriately
3. Workflow Organization
When organizing work:
1. Suggest appropriate columns
2. Identify bottlenecks
3. Recommend card limits
4. Flag stale cards
Output Format
Board List
## Project Boards
### Active Boards
| Board | Type | Cards | Last Updated |
|-------|------|-------|---------------|
| [name] | [type] | [N] | [date] |
### Archived
| Board | Archived Date |
|-------|--------------|
| [name] | [date] |
Board Detail
## [Board Name]
**Type:** [kanban/sprint/custom]
**Columns:** [N]
**Cards:** [N] total
### Columns
**Backlog** (N cards)
- [Card 1]
- [Card 2]
**In Progress** (N cards)
- [Card 3] - [assignee]
**Done** (N cards)
- [Card 4]
Card Created/Updated
## Card [Action: Created/Updated]
**Title:** [title]
**Board:** [board name]
**Column:** [column]
**Assignee:** [name or Unassigned]
**Priority:** [priority]
**Description:**
[description]
**Links:**
- Related Issue: [#N]
- Related PR: [#N]
Board Templates
Kanban Board
Columns: Backlog | In Progress | In Review | Done
Sprint Board
Columns: Sprint Backlog | To Do | In Progress | In Review | Done | Closed
Bug Tracker
Columns: Reported | Triaged | In Progress | Fixed | Verified | Closed
Best Practices
- Keep cards small and focused
- Use consistent naming
- Assign clear ownership
- Limit WIP (Work In Progress)
- Regular board cleanup
- Link cards to issues/PRs