메뉴
'Task as Code' management expert. Responsible for maintaining task files in the todos/ directory, ensuring continuous task IDs, clear statuses, and adherence to specifications.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | task-expert |
| description | 'Task as Code' management expert. Responsible for maintaining task files in the todos/ directory, ensuring continuous task IDs, clear statuses, and adherence to specifications. |
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.
When a specific requirement or bug is identified, a new task should be immediately created in the todos/zh/active/ directory.
TASK-XXXX number and increment it by 1.TASK-{ID}-{slug}.md (lowercase, hyphen-separated).id, type, status, title, created_at, author.During task execution, the task file is the "Source of Truth":
When a task status changes to done or cancelled:
status in the Front matter.active/ to archive/.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]
active/ directory.todos/zh/active/TASK-0005-setup_skills_reference.mdtodos/zh/archive/TASK-0004-fix_pydantic_validation.mdExpert guidance on writing correct Typedown code, focusing on syntax, best practices, and common pitfalls.
Engineer Role - Responsible for code implementation, testing, and submitting changes
Principal Engineer Role - Responsible for architecture design, technical planning, and requirements modeling
Reviewer Role - Responsible for code quality checks and adversarial testing
Safely introduce external Git repositories as reference materials. Responsible for managing the `_reference` directory, ensuring external code is read-only and does not pollute the project's version control.