draft-task

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

This skill creates a lightweight task file in

ralph/backlog/

— no interview, no PRD ceremony. Just a title, type, priority, and a short description.

该技能会在

ralph/backlog/

目录下创建轻量任务文件——无需问询，也不用走PRD流程，仅需标题、类型、优先级和简短描述即可。

Before starting

开始前

Check that

ralph/backlog/

exists. If it doesn't, suggest running

/setup-ralph

first.

Check existing backlog items to avoid duplicates — if a similar task already exists (open or in-progress), tell the user and ask if they still want to create a new one.

检查

ralph/backlog/

目录是否存在。如果不存在，建议用户先运行

/setup-ralph

。

检查现有待办项避免重复——如果已存在类似任务（处于打开或进行中状态），告知用户并询问是否仍要创建新任务。

Workflow

工作流

If the user provided a description inline (e.g.,
```
/draft-task add error toasts on failed API calls
```
), use it directly. Otherwise, ask them to describe the task in one or two sentences.
From the description, auto-detect:
- title — short, descriptive
- type — infer from keywords:
  - ```
  bug
```
  ,
```
  fix
```
  ,
```
  broken
```
  ,
```
  crash
```
  ,
```
  error
```
  ,
```
  regression
```
  →
```
  bug
```
- ```
refactor
```
    ,
```
rename
```
    ,
```
extract
```
    ,
```
clean up
```
    →
```
refactor
```
  - ```
  test
```
  ,
```
  lint
```
  ,
```
  ci
```
  ,
```
  types
```
  ,
```
  tooling
```
  ,
```
  config
```
  →
```
  infrastructure
```
- everything else →
```
  task
```
- priority — ask the user. Show them the scale:
  - 1 = Critical bugfix
  - 2 = Dev infrastructure
  - 3 = New feature / general task
  - 4 = Polish / quick win
  - 5 = Refactor
Write the file to
```
ralph/backlog/<kebab-case-title>.md
```
:

markdown

---
title: "<title>"
type: <type>
status: open
priority: <priority>
created: <today's date YYYY-MM-DD>
---

<the user's description, cleaned up if needed but not expanded into a PRD>

Show the user what was created: path, type, and priority. No confirmation step — this is meant to be fast.

如果用户直接附带了描述（例如
```
/draft-task add error toasts on failed API calls
```
），直接使用即可。否则请用户用一两句话描述该任务。
根据描述自动识别：
- title——简短、描述性的标题
- type——根据关键词推断：
  - ```
  bug
```
  、
```
  fix
```
  、
```
  broken
```
  、
```
  crash
```
  、
```
  error
```
  、
```
  regression
```
  →
```
  bug
```
- ```
refactor
```
    、
```
rename
```
    、
```
extract
```
    、
```
clean up
```
    →
```
refactor
```
  - ```
  test
```
  、
```
  lint
```
  、
```
  ci
```
  、
```
  types
```
  、
```
  tooling
```
  、
```
  config
```
  →
```
  infrastructure
```
- 其他所有内容 →
```
  task
```
- priority——询问用户，向用户展示优先级划分：
  - 1 = 紧急bug修复
  - 2 = 开发基础设施相关
  - 3 = 新功能/通用任务
  - 4 = 优化/速赢项
  - 5 = 重构
将文件写入
```
ralph/backlog/<kebab-case-title>.md
```
：

markdown

---
title: "<title>"
type: <type>
status: open
priority: <priority>
created: <today's date YYYY-MM-DD>
---

<the user's description, cleaned up if needed but not expanded into a PRD>

向用户展示创建的内容：路径、类型和优先级。无需确认步骤——该功能的设计初衷就是快速高效。

Batch mode

批量模式

If the user provides multiple tasks at once (e.g., a list), create a separate backlog file for each one. Show a summary table at the end:

File	Type	Priority
`add-error-toasts.md`	task	3
`fix-login-crash.md`	bug	1

如果用户一次性提供了多个任务（例如列表形式），为每个任务单独创建待办文件。最后展示汇总表格：

File	Type	Priority
`add-error-toasts.md`	task	3
`fix-login-crash.md`	bug	1