Task Expert
Productivitytask-expertTask Expert is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
'Task as Code' management expert. Responsible for maintaining task files in the todos/ directory, ensuring continuous task IDs, clear statuses, and adherence to specifications.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/task-expert-indenscale-typedown/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/task-expert, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Task Expert
This skill provides guidance on following the Task as Code philosophy. In this system, conversations are fluid, but tasks are persistent. All non-trivial changes must be documented in task files.
Core Workflow
1. Task Identification and Creation
When a specific requirement or bug is identified, a new task should be immediately created in the todos/zh/active/ directory.
- ID Allocation: Find the current maximum
TASK-XXXXnumber and increment it by 1. - File Naming:
TASK-{ID}-{slug}.md(lowercase, hyphen-separated). - Front matter: Must include
id,type,status,title,created_at,author.
2. Develop and Document
During task execution, the task file is the "Source of Truth":
- Context: Record background information in the file.
- Objectives: Define clear deliverables.
- Plan: Maintain a task list (Checkboxes) in the file.
- Thought: Record key design decisions or technical pivots.
3. Task Archiving
When a task status changes to done or cancelled:
- Update the
statusin the Front matter. - Move the file from
active/toarchive/.
File Format Standards
Task files must use the following structure:
---
id: TASK-XXXX
type: task
status: active # active | done | cancelled
title: "Task Title"
created_at: 202X-XX-XX
author: [Your Name]
---
# TASK-XXXX: [Task Title]
## Background
[Briefly explain why this task is needed]
## Objectives
- [ ] Objective 1
- [ ] Objective 2
## Workflow/Notes
[Record thoughts, command outputs, or key code snippets during execution]
Antipatterns
- Skipping IDs: Strictly forbidden to skip ID numbers.
- Forgetting: Strictly forbidden to close a conversation without updating statuses.
- Clutter: Strictly forbidden to pile up completed tasks in the
active/directory. - Hidden Logic: Strictly forbidden to discuss complex logic only in the conversation without persisting it in task files.
Examples
todos/zh/active/TASK-0005-setup_skills_reference.mdtodos/zh/archive/TASK-0004-fix_pydantic_validation.md