task skill
Adds new tasks, bugs, features, or inquiries to a MASTER_PLAN.md file with automatic sequential ID generation.
- GitHub stars
- 26
- Files
- 1
- Last commit
- Feb 26, 2026
- License
- MIT
- Allowed tools
- —
What does the task skill do?
task adds new tasks, bugs, features, or inquiries to a MASTER_PLAN.md file with automatic sequential ID generation.
Summary generated from the skill's SKILL.md.
About the task skill
Managing project roadmaps and tracking technical debt becomes automated when developers use this skill to log work. It allows an agent to identify, categorize, and document new tasks, bugs, features, or inquiries directly into a MASTER_PLAN.md file. When an agent receives a command like "add task" or "track this," it searches for an existing plan file in specific directories or creates a new one in a docs folder if none is found.
The tool handles the complex logic of sequential ID generation by scanning existing entries to ensure every new item receives a unique, incremented number regardless of whether it is a BUG, TASK, or FEATURE. It uses the AskUserQuestion tool to gather necessary details like priority levels from P0 to P3 and concise titles. Once information is collected, the skill updates the roadmap table and appends a detailed markdown section containing the status, description, and initial steps for the work.
What an agent can do with it
- 1Log a new software bugAn agent can record a newly discovered issue as a BUG type with a specific priority level.
- 2Initialize a project roadmapIf no tracking file exists, the skill sets up a standardized MASTER_PLAN.md structure.
- 3Generate unique sequential IDsThe skill ensures that every new entry has a unique identifier by calculating the next number in the sequence.
- 4Document major feature requestsDevelopers can add large-scale improvements to the roadmap with detailed descriptions and priority notes.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the task skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the task skill in Plugin
/plugin marketplace add endlessblink/master-plan /plugin install master-plan@master-plan
Install the task skill in Claude Code
~/.claude/skills/task/SKILL.md
$ npx degit endlessblink/master-plan/skills/task ~/.claude/skills/taskInstall the task skill in Claude Code (project)
.claude/skills/task/SKILL.md
$ npx degit endlessblink/master-plan/skills/task .claude/skills/taskInstall the task skill in Codex
~/.agents/skills/task/SKILL.md
$ npx degit endlessblink/master-plan/skills/task ~/.agents/skills/taskInstall the task skill in Gemini CLI
~/.gemini/skills/task/SKILL.md
$ npx degit endlessblink/master-plan/skills/task ~/.gemini/skills/taskInstall the task skill in Claude.ai
npx degit endlessblink/master-plan/skills/task task && zip -r task.zip task # claude.ai → Customize → Skills → + → Create skill → Upload a skill → task.zip
SKILL.md
View on GitHubTask Creator
Quickly add new tasks to MASTER_PLAN.md with automatic sequential ID generation.
Triggers
/master-plan:task- Main command- "add task", "new task", "create task", "track this", "log a bug"
Workflow
Step 1: Find MASTER_PLAN.md
Search for the plan file in order:
docs/MASTER_PLAN.mdMASTER_PLAN.mdmaster-plan.mddocs/master-plan.md
If not found: Create docs/MASTER_PLAN.md using the template structure (see "Initial Setup" section below).
Step 2: Generate Next Task ID
Read the MASTER_PLAN.md file and find all existing task IDs:
- Scan for all occurrences matching
(TASK|BUG|FEATURE|ROAD|IDEA|ISSUE|INQUIRY)-(\d+) - Extract the numeric part from each match
- Find the highest number
- Next ID = highest + 1
CRITICAL: IDs are sequential across ALL types. If TASK-42 and BUG-43 exist, the next ID is 44 regardless of type.
Immediately output to user:
Using task number: [ID]
This must happen BEFORE asking any questions.
Step 3: Gather Task Information
Use AskUserQuestion to collect:
-
Task Type (header: "Type")
TASK— New feature or improvementBUG— Bug fixFEATURE— Major new featureINQUIRY— Investigation (not a fix, just understanding something)
-
Priority (header: "Priority")
P0— Critical / BlockerP1— High priorityP2— Medium priority (Recommended)P3— Low priority / Backlog
Then ask in plain text: "What's the task title? (Keep it concise, under 50 chars)"
Optionally ask: "Any additional description? (Or just press enter to skip)"
Step 4: Add to MASTER_PLAN.md
4a. Add to Roadmap Table (if one exists)
Look for a markdown table with task IDs. Insert a new row:
| **[TYPE]-[ID]** | **[Title]** | **[Priority]** | PLANNED | - |
4b. Add Detailed Section
Add a new ### section at the appropriate place (typically at the end of the active work area, before completed tasks):
### [TYPE]-[ID]: [Title] (PLANNED)
**Priority**: [Priority]
**Status**: PLANNED (YYYY-MM-DD)
[Description if provided]
**Tasks**:
- [ ] [First step — infer from context or ask user]
For P0/P1 tasks, add a note that this is high priority.
Step 5: Confirm
Output to user:
Task added to MASTER_PLAN.md:
- **ID**: [TYPE]-[ID]
- **Title**: [Title]
- **Priority**: [Priority]
- **Status**: PLANNED
Use `/master-plan:next` to start working on it, or `/master-plan:done [ID]` when complete.
Initial Setup
If no MASTER_PLAN.md exists, create docs/MASTER_PLAN.md with this structure:
# MASTER PLAN
> Project task tracking and roadmap.
## Roadmap
| ID | Title | Priority | Status | Dependencies |
|----|-------|----------|--------|--------------|
## Active Work
<!-- New task sections are added here -->
## Completed
<!-- Done tasks are moved here -->
Also create the docs/ directory if it doesn't exist.
ID Format Reference
| Prefix | Usage |
|---|---|
TASK-XXX |
Features and improvements |
BUG-XXX |
Bug fixes |
FEATURE-XXX |
Major features |
ROAD-XXX |
Roadmap items |
IDEA-XXX |
Ideas for later |
ISSUE-XXX |
Known issues |
INQUIRY-XXX |
Investigations |
Important Rules
- NEVER reuse existing task IDs — Always scan the file first
- IDs are global — Sequential across all types (TASK, BUG, etc.)
- Use strikethrough (
~~ID~~) only when marking tasks DONE - Keep titles concise — Under 50 characters
- P0 tasks should always get an immediate detailed section
Files in this skill
1task skill questions
How do I install the task skill in Claude Code?
Run npx degit endlessblink/master-plan/skills/task ~/.claude/skills/task. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the task skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What task types can I create?
You can create TASK, BUG, FEATURE, ROAD, IDEA, ISSUE, and INQUIRY types.