w02-task-planning

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Task Planning Specification, applicable to complex tasks (≥3 steps), including requirement decision-making and project plan creation. It covers planning specifications, requirement decision-making processes, and project plan generation tools.

2installs

Sourceqiao-925/qiao-skills

Added on2026-02-07

NPX Install

npx skill4agent add qiao-925/qiao-skills w02-task-planning

SKILL.md Content (Chinese)

View Translation Comparison →

Task Planning Specification

Applicable to pre-planning of long-term tasks, ensuring controllable execution and trackable progress through the Plan + Checkpoint mechanism.

⚠️ Core Mandatory Requirements

Trigger Conditions

The user explicitly requests "planning", "plan", "design scheme", etc.
The Agent assesses that the task requires >= 3 clear steps
Involves multi-file modifications or architecture changes

Complex Tasks Must Create a Project Plan

Complexity	Characteristics	Handling Method
Simple	1-2 steps, single file	Execute directly
Medium	3-5 steps, 2-3 files	It is recommended to create a project plan
Complex	>5 steps, multi-file/architecture changes	Must create a project plan

Long-term Tasks Must Enable GitHub Issue Archiving (W00)

For tasks expected to span sessions/days, or requiring global tracking of in-progress status, an Issue must be created or bound via
```
w00-workflow-checkpoint
```
.
The project plan must record:
```
Issue #
```
, current
```
status
```
,
```
Next
```
(next step).
Issue creation/binding is completed by the main process;
```
w00-workflow-checkpoint
```
is only responsible for subsequent archiving and context loading.

AI Agent Behavior Requirements

Active Proposal

For complex tasks, must actively propose creating a project plan first:

Detected that the task involves [N] steps, it is recommended to create a project plan first. Execute scripts/generate_task_plan.py?

Status Update

After completing each CP, remind to update the status table:

CP1 completed, it is recommended to update the project plan status table: CP1: ⬜ → ✅ Completed | 2026-01-22

And synchronously update the checkpoint of the corresponding Issue (including

next step

).

Collaboration with W00 (Automatic + Manual)

After creating the project plan and binding the Issue, it can automatically trigger:
```
w00-workflow-checkpoint checkpoint
```
.
It can also be triggered manually: Execute
```
/w00-workflow-checkpoint
```
for checkpoint archiving or context loading.
If an Issue already exists: Fill in
```
Issue #
```
in the project plan and follow the existing status flow.
If no clear Issue exists and there are multiple candidates: List 3~5 candidate issues first, let the user select, then perform archiving/loading.

Must Wait for User Decision

Architecture/technology selection
Trade-offs between performance and maintainability
Technical debt or temporary solutions

Tool Scripts

Script:

scripts/generate_task_plan.py

Function: Plan Checkpoints, generate standardized project plans

Reference Materials

```
references/planning-workflow.md
```
- Detailed explanation of planning workflow (CP division, status marking, file management, file list format)
```
references/requirements-decisions.md
```
- Detailed explanation of requirement decision-making process (requirement understanding, scheme design, decision confirmation)
```
../w00-workflow-checkpoint/SKILL.md
```
- Basic archiving capability of Workflow GitHub Issues (Automatic + Manual)
```
refactor-and-decompose/SKILL.md
```
- File list and module boundary constraints during planning