feature-continue

To resume interrupted feature development while preserving PM-DB tracking, you need a task-list.md file and a PM-DB import. The feature-continue command detects the last completed checkpoint and continues remaining tasks without duplication.

To resume feature work across sessions, you need an existing task-list.md file path and a PM-DB import. This setup provides the resume context needed to seamlessly recover remaining tasks after outages or intentional halts.

PM-DB continuity works during a paused phase run by using a single phase_run to maintain end-to-end traceability. It passes resume context to detect the last completed task and continues from the next task without redoing work.

Yes, you can recover task lists after a crash or intentional halt. The feature-continue command works directly from your task-list.md location to support scoped recovery, preventing data loss and seamlessly continuing remaining tasks.

The best way to prevent task duplication when resuming a feature workflow is to use a PM-DB phase_run. It automatically detects the last completed task in your task-list.md and continues from the next step without redoing completed work.