vibe-continue

Original：🇨🇳 Chinese

Translated

This skill applies when the user wants to resume previous work, enters the command "/vibe-continue", or starts a new session and needs to load saved context. Restore from shared task facts first, then use task.md as the local handoff.

2installs

Sourcejacobcy/vibe-coding-control-center

Added on2026-03-16

NPX Install

npx skill4agent add jacobcy/vibe-coding-control-center vibe-continue

SKILL.md Content (Chinese)

View Translation Comparison →

/vibe-continue - Resume Current Flow

The goal of

/vibe-continue

is to restore the context of the task corresponding to the

flow

hosted in the current directory, but the restoration order must be "shared facts first, local handoff as supplement", not the other way around.

Core Principles:

Read the shared source of truth first, then read
```
.agent/context/task.md
```
.
```
.agent/context/task.md
```
is a handoff, not a shared source of truth.
The maintenance obligation of handoff shall follow
```
docs/standards/handoff-governance-standard.md
```
; if inconsistencies with the current scene are found, corrections must be made.
Do not invent non-existent Shell repair actions during the continue phase.

Announce at start: "I am using the /vibe-continue skill to restore the task context of the current flow."

Truth Sources

The following semantics shall be based on the standards:

```
docs/standards/skill-standard.md
```
```
docs/standards/command-standard.md
```

docs/standards/shell-capability-design.md

```
docs/standards/git-workflow-standard.md
```

docs/standards/handoff-governance-standard.md

```
docs/standards/glossary.md
```

Special Constraints:

flow

is not equivalent to

worktree

,

branch

, or

workflow

. Refer to

docs/standards/glossary.md

.

The obligations for reading, writing, and correcting

.agent/context/task.md

shall follow

docs/standards/handoff-governance-standard.md

.

Command Boundary

```
/vibe-continue
```
is responsible for interpreting the current scene and providing suggestions for continuation.
Shell commands are only used to read the shared source of truth and deterministic facts of the current scene.
```
git
```
/
```
gh
```
can be used to supplement on-site facts such as branch, dirty status, PR, etc.
If an environment correction action is required, you must use a real, documented entry in the repository; do not invent unvalidated repair commands.

Restore Order

/vibe-continue

restores in the following order by default:

Current

git

scene (

git branch --show-current

,

git status --short

,

gh pr view

if necessary)

$(git rev-parse --git-common-dir)/vibe/registry.json

$(git rev-parse --git-common-dir)/vibe/tasks/<task-id>/task.json

```
$(git rev-parse --git-common-dir)/vibe/worktrees.json
```
(if exists, only as a compatibility period auxiliary clue)
```
.agent/context/task.md
```
(if exists)

Supplement with the following if necessary:

Current branch
```
git status --short
```
Current PR / review facts

Workflow

Step 1: Identify the task corresponding to the flow hosted in the current directory

Prioritize identification from the

git

scene, shared

registry.json

, and task details:

Current task
```
next_step
```
```
plan_path
```
Current runtime binding facts
```
primary_issue_ref
```
(if exists, it is the explicit landing point of the
```
task issue
```
)

If

worktrees.json

exists, it can only be used as a compatibility period hint, and cannot preempt the current task identification right before

registry.json

.

If the current task cannot be identified from the shared source of truth, do not directly elevate

task.md

as an alternative source of truth; it can only be used as a local handoff clue.

Step 2: Read local handoff

If

.agent/context/task.md

exists, use it as a supplementary source for the following information:

Completed items in this round
Current judgments
Blockers
Key files

If its content is inconsistent with the current source of truth or scene, you must correct the handoff before exiting, and cannot directly use the old judgment.

If it is missing, it does not block the continue process; it only indicates that there is no local handoff currently.

Step 3: Cross-check the current scene

Complete the current view with deterministic facts, such as:

Current branch
dirty / clean status
Current PR status

During the continue phase, you can report inconsistencies, but do not refer to query commands as "auto-alignment", and do not call unvalidated implicit repair actions.

Step 4: Provide continuation suggestions

The priority of suggestions is as follows:

If
```
plan_path
```
exists, prioritize suggesting to continue according to the plan.
If only
```
next_step
```
exists, suggest continuing with the next step of the current task.
If only the local
```
task.md
```
handoff exists, clearly mark it as a local supplementary clue, not a shared fact.

Suggested Output

📋 Session Resume

📁 Current Scene
  • worktree: <worktree>
  • branch: <branch>
  • state: dirty|clean

📌 Current Task
  • task: <task-id>
  • next step: <next-step>
  • plan: <plan-path|none>

📝 Local Handoff
  • task.md: present|missing
  • blockers: <summary>

💡 Suggested Action
  • continue with <plan-path|next-step>

Design Decisions

The continue process restores shared facts first, then reads the local handoff.
The role of
```
task.md
```
is to provide supplementary explanations, not to replace the source of truth.
The continue phase reports scene differences, but does not invent unvalidated automatic repair actions.