taskmaster-skill
Use when managing complex project plans, tracking multi-phase task progress, or prioritizing development tasks
Best use case
taskmaster-skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when managing complex project plans, tracking multi-phase task progress, or prioritizing development tasks
Teams using taskmaster-skill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/taskmaster-skill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How taskmaster-skill Compares
| Feature / Agent | taskmaster-skill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when managing complex project plans, tracking multi-phase task progress, or prioritizing development tasks
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# TaskMaster Skill
> Agent-optimized task management system for AgentFabric.
## Overview
A structured task management system for organizing, tracking, and executing multi-phase development plans through agent-optimized CLI workflows.
## When to Use
- Managing complex project plans with interdependent tasks
- Tracking multi-phase task progress across milestones or sprints
- Prioritizing development tasks based on dependencies and readiness
- Coordinating sequential work that requires structured start, verify, and archive workflows
**Do not use when:**
- Simple single-step tasks without dependencies
- Informal tracking where a basic todo list is sufficient
- Projects not requiring configured plan directories or CLI tooling
---
## Setup
### Prerequisites
- Node.js 22+
- Working directory: `docs/plans/`
### Installation
#### Option 1: Direct Node.js (Agent Recommended)
```bash
cd docs/plans/taskmaster-skill/cli
npm install
```
Then use CLI via:
```bash
node cli/task.js <command>
```
#### Option 2: Shortcut Scripts (Install Dependencies Automatically)
```bash
cd docs/plans
# Windows
taskmaster-skill\task.bat <plan> <command>
# Linux/Mac
./taskmaster-skill/task.sh <plan> <command>
```
### Quick Start
```bash
# View all plans
node cli/task.js plans
# Check progress
node cli/task.js progress mvp_v1
# List tasks
node cli/task.js list mvp_v1
# List ready-to-start tasks (dependencies completed)
node cli/task.js ready mvp_v1
node cli/task.js ready mvp_v1 --limit 20
```
### Configuration (REQUIRED)
**Before using TaskMaster, you MUST configure the plan mapping:**
#### Step 1: Copy template
```bash
cp config.json.template config.json
```
#### Step 2: Edit config.json
```json
{
"version": "1.0.0",
"plans": {
"mvp_v1": {
"path": "E:\\Agent\\agent-fabric\\docs\\plans\\mvp_v1",
"description": "AgentFabric MVP v1 实施计划"
}
},
"settings": {
"defaultPlan": "mvp_v1",
"autoCreatePlan": false,
"logRetentionDays": 30
}
}
```
**Replace the path with your actual plan directory (absolute path).**
#### Step 3: Verify configuration
```bash
# List configured plans
node cli/task.js config list
# Add additional plans if needed
node cli/task.js config add <name> <path> --description "<desc>"
# Set default plan
node cli/task.js config set-default <name>
```
---
## Documentation Index
### Agent Instruction Manuals
| Document | Purpose | When to Use |
|----------|---------|-------------|
| **[COMMANDS.md](./COMMANDS.md)** | Complete command specifications | Need detailed syntax for any command |
| **[WORKFLOWS.md](./WORKFLOWS.md)** | Standard operation procedures | User asks to start/complete/audit tasks |
| **[BEST_PRACTICES.md](./BEST_PRACTICES.md)** | Operational rules and constraints | Need to validate operation against rules |
### Reference Data
| Document | Purpose | When to Use |
|----------|---------|-------------|
| **[DATA_FORMAT.md](./DATA_FORMAT.md)** | JSON schema specifications | Need to parse or construct data |
| **[TROUBLESHOOTING.md](./TROUBLESHOOTING.md)** | Error codes and resolution procedures | Command returns error |
### Quick Reference
| Document | Purpose | When to Use |
|----------|---------|-------------|
| **[EXAMPLES.md](./EXAMPLES.md)** | Scenario-based execution patterns | User intent matches example scenario |
| **[TEMPLATES.md](./TEMPLATES.md)** | Copy-paste command templates | Need ready-to-use command |
---
## Quick Decision Map
```
User Request
|
+-- "查看/查询/了解 (View/Query/Understand)..." ──► Read COMMANDS.md "Query Commands" section
+-- "有哪些任务可以开始 (What tasks can I start)" ──► Read COMMANDS.md "ready" command
+-- "开始/做...任务 (Start/Do...task)" ──► Read WORKFLOWS.md "Start Task Workflow"
+-- "完成/做完了 (Complete/Done)..." ──► Read WORKFLOWS.md "Complete Task Workflow"
+-- "添加/新建 (Add/Create)...task" ──► Read COMMANDS.md "add" + EXAMPLES.md "Adding New Task"
+-- "归档 (Archive)..." ──► Verify done + verified ──► Read COMMANDS.md "archive"
+-- "检查/核验 (Check/Verify)..." ──► Read COMMANDS.md "verify"
+-- "遇到问题/报错 (Encounter problem/error)..." ──► TROUBLESHOOTING.md
```
---
## Command Syntax
All commands follow this pattern:
```bash
node cli/task.js <command> [options]
```
Or via shortcut scripts:
```bash
# Windows
taskmaster-skill\task.bat <plan> <command>
# Linux/Mac
./taskmaster-skill/task.sh <plan> <command>
```
## Execution Rules
**ALWAYS:**
1. Check dependencies before `start` (run `deps` first)
2. Verify before `archive` (run `verify` first)
3. Parse command output to determine next action
4. Confirm with user for `--force` operations
**NEVER:**
1. Skip `verify` before `archive` (unless user explicitly confirms `--force`)
2. Assume task ID without confirming
3. Ignore error messages in command output
---
## File Locations
```
docs/plans/
├── taskmaster-skill/
│ ├── cli/task.js # CLI entry point
│ ├── config.json # Plan configurations
│ ├── logs/ # Operation logs
│ │ ├── operations.log
│ │ └── operations.jsonl
│ └── *.md # This documentation
│
└── <plan-name>/
├── data.json # Task data (JSON format)
└── README.md # Plan description
```
---
## Version
- CLI Version: 1.1.0
- Data Format: 1.0.0
- Last Updated: 2026-03-04Related Skills
unity-mcp
Use when controlling Unity editor via AI, automating scene operations, or programmatically generating Unity assets and scripts
ue5-umg
Use when building HUDs, menus, inventory screens, settings panels, or any widget-based interface in Unreal Engine 5. Also use when connecting C++ logic to UMG Blueprint visuals, handling gamepad or keyboard focus navigation, managing UI state, creating widget animations, or troubleshooting UMG performance issues like frame drops, hitches, or widget memory leaks.
research-to-practice
Use when applying academic research to practical workflows, optimizing existing processes based on papers, or extracting actionable insights from research
requirement-clarification
Use when receiving ambiguous instructions, preparing for state-changing operations, or needing explicit user confirmation
paper-first-principles
Use when converting academic papers into engineer-friendly documentation, extracting design patterns from research, or preparing technical knowledge sharing
mvp-design
Use when designing new modules from scratch, creating minimal viable prototypes, or establishing architectural decisions before implementation
msvc-build
Use when compiling MSVC C++ projects, debugging build errors, or performing clean and incremental builds
layered-first-principles-teaching
Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure
knowledge-base-cache
Use when managing large knowledge bases, reducing API costs, or implementing multi-tier caching for frequent queries
kimicode-vision-bridge
Use when the current Agent LLM cannot process images directly and visual analysis is needed — bridges images through KimiCode CLI print mode to a multimodal Kimi model for text description
hexo-blog-update
Use when creating, editing, or publishing Hexo blog posts
git-workflow
Use when committing code, pushing changes, or managing Git operations that require safety checks