task-complete

To mark a backlog task as done, the task markdown file needs its frontmatter status updated to done and then relocated into the tasks/done directory. This archives the completed work while maintaining a single source of truth for task tracking.

Retaining learnings from a completed workflow task requires recording a concise completion summary via a Hindsight note. This tagged note preserves key decisions and context so future tasks can reference what worked and avoid repeating mistakes.

Archiving completed tasks into a done directory improves backlog management by preventing finished items from lingering as in-progress. Relocating the markdown files keeps the active backlog clean and ensures only current work remains visible.

Yes, you can use markdown files for status tracking in a devflow backlog workflow by updating their frontmatter status. Tasks move from open or in-progress folders into a tasks/done archive as they are completed.

Yes, you need a task ID to archive a completed task file. Providing the specific task ID ensures the correct markdown file is identified, updated, and relocated to the done archive.