Task went cold?

Resume a DevSpecs task after time away

Recover the current slice, its last gate, and whether the planned follow-up still matches the goal.

Starting state

One pinned repository. One concrete goal.

Resume a previously structured DevSpecs task and decide whether its next slice remains current.

+A structured DevSpecs task thread already exists on demo/devspecs-oauth-redirect.
+F01 was traced and checkpointed before the session ended.
+The returning developer has not reopened the earlier chat and is not reviewing a new unattended implementation diff.

Repository: fastapi/fastapi
Commit: 3d2aace4
DevSpecs: v1.3

DevSpecs entry

$ds recent "OAuth redirect"

DeveloperDevSpecsCoding agent

Workflow

STEP 1 OF 3

Ask what was active

Developer

Start with the topic you remember. The warmed local index and Git history can recover the surrounding work.

Command

$ds recent "OAuth redirect" --no-refresh

CLI output

TopicOauth Redirect Handoff

Recentc5996f0 chore: prepare OAuth redirect task handoff

Key path.devspecs/config.yaml

Tryds find "oauth redirect handoff"

Confidencemedium

What this tells you

There is one current OAuth redirect thread. The evidence is enough to orient, but the key-path signal is too thin to authorize an edit.

Continue with

Confirm the task lifecycle before choosing a slice.

Output verified against the pinned run

This receipt is the capture file used to check the excerpt. You do not need it to follow the workflow.

Normalized ds recent JSON · 10-recent.stdout.txt

STEP 2 OF 3

Recover the lifecycle state

DevSpecs

Read the durable task record so progress does not depend on the latest commit subject.

Command

$ds task status fastapi-oauth-redirect

CLI output

F01 validated · promote

F02 next · Add OpenAPI exclusion regression

F03 planned · Document configuration and cleanup

Nextds apply fastapi-oauth-redirect

What this tells you

The earlier trace passed its gate. F02 is the next bounded slice; F03 stays outside the current scope.

Continue with

Continue only if F02 still matches the human goal. Otherwise stop and rework the task before editing.

Output verified against the pinned run

This receipt is the capture file used to check the excerpt. You do not need it to follow the workflow.

Normalized task status JSON · 11-task-status.stdout.txt

STEP 3 OF 3

Choose whether to continue

Developer

Use the recovered thread as a decision input. The developer still decides whether the old plan remains current.

What this tells you

The local record is internally consistent: F01 promoted and named F02 as its follow-up. No later task state supersedes it.

Continue with

Continue with F02, but verify the named source and tests when the bounded prompt opens.

Result

The returning developer recovered F02 as the next slice and confirmed its decision gate without reopening chat. F03 remains out of scope. This resumes structured task state; it does not review a new agent diff.

F00-index.md
F01-...-result.md
checkpoints/<timestamp>-validated.md
task.json

Common failure

Treating recent as the whole answer

The real capture reports medium confidence and initially highlights only `.devspecs/config.yaml`. Use it to locate the thread, then verify the implementation files.

Use task status for lifecycle state, then use find or the bounded apply prompt to verify files before editing.