菜单
Task template definitions for AIDF. Provides structured templates for component, refactor, test, docs, architecture, and bugfix task types.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Teaches AI agents how to work with AIDF (AI-Integrated Development Framework) projects — structure, task format, scope enforcement, completion signals, and conventions.
Software architect for the AIDF CLI tool. Designs around the 5-layer context system, provider interface, and scope enforcement.
Senior developer for the AIDF CLI tool. Writes ESM-only TypeScript, follows provider patterns, and centralizes types.
Technical writer for the AIDF project. Maintains docs/, CLAUDE.md, AGENTS.md, and skill documentation.
Code reviewer for the AIDF CLI tool. Checks ESM compliance, type centralization, scope enforcement, and provider consistency.
Task template definitions for AIDF. Provides structured templates with scope, requirements, and Definition of Done for the AIDF codebase.
| name | aidf-task-templates |
| description | Task template definitions for AIDF. Provides structured templates for component, refactor, test, docs, architecture, and bugfix task types. |
| version | 1.0.0 |
| author | AIDF |
| tags | templates, tasks, project-management, workflow |
| globs | .ai/tasks/**, .ai/templates/** |
Structured templates for AI-assisted development tasks. Each task type has a specific template with goal, scope, requirements, and definition of done.
New feature or component implementation. Includes scope definition, implementation requirements, and quality gates.
Code restructuring without changing behavior. Requires before/after comparison and all existing tests must pass.
Adding or improving test coverage. Defines coverage targets, test categories, and quality thresholds.
Documentation writing or improvement. Accuracy verification, working examples, and audience targeting.
System design and planning. Trade-off analysis, component diagrams, and migration paths.
Bug reproduction and fix. Requires root cause analysis, fix verification, and regression test.
Every task follows this structure:
# TASK: [Name]
## Goal
[What needs to be accomplished]
## Task Type
[component|refactor|test|docs|architecture|bugfix]
## Suggested Roles
- [role names]
## Scope
### Allowed
- [file patterns]
### Forbidden
- [file patterns]
## Requirements
[Detailed requirements]
## Definition of Done
- [ ] [Criteria 1]
- [ ] [Criteria 2]