Skill

task-expert

'Task as Code' management expert. Responsible for maintaining task files in the todos/ directory, ensuring continuous task IDs, clear statuses, and adherence to specifications.

Install

npx claudepluginhub joshuarweaver/cascade-content-creation-misc-1 --plugin indenscale-typedown

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

Supporting Assets

SKILL.zh.md

SKILL.md

Similar Skills

angular-new-app

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

100.1k

angular-developer

20 files

Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.

angular-angular-1

100.1k

github-deep-research

2 files

Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.

bytedance-deer-flow-1

63.9k

Stats

Stars9

Forks0

Last CommitFeb 13, 2026

Actions

View Source View Plugin View on GitHub View README

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-XXXX number 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 status in the Front matter.

Move the file from active/ to archive/.

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.md

todos/zh/archive/TASK-0004-fix_pydantic_validation.md