track-issue-flow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Follow this workflow when handling issue work in repositories that use the

track

CLI.

在使用

track

CLI的代码仓库中处理问题工作时，请遵循此工作流。

Identify candidate issues.
- Run
```
track list
```
  .
- If the user refers to an item by list position (for example, "5"), map it to the exact issue ID in the current output before acting.
Confirm issue scope.
- Run
```
track show <issue-id>
```
  .
- Extract status, priority, labels, and notes to understand expectations and missing details.
Start execution with explicit state changes.
- When work begins, set status to active (
```
in_progress
```
  ) using
```
track set
```
  .
- Keep user-facing updates aligned with tracker state.
Implement and validate.
- Make code/doc changes required by the issue.
- Run project checks relevant to changed files.
Close the loop in the tracker.
- Update labels/priority/status as needed.
- Mark done only after the requested implementation and validation are complete.

Read

references/track-cli-reference.md

for command patterns used by this skill.

阅读

references/track-cli-reference.md

以了解此技能使用的命令模式。

Resolve IDs from fresh
```
track list
```
output; do not assume stale ordering.
Prefer concrete IDs (
```
TRK-xx
```
) for mutations.
Keep tracker updates small and explicit so history remains auditable.
If issue details are unclear, capture assumptions in progress updates before making irreversible changes.