flow-skip

To skip a task in the Beads workflow system, you close the specified task by providing a justification reason. The system then logs the skipped task details, including its description and your reason, directly into a skipped.md audit file within the project's specification directory.

Documenting task abandonment is best handled by logging the task description and a justification reason into a skipped.md file. This creates a clear audit trail within the project specification directory, ensuring task progress is managed and justified for future review.

You should formally skip a task when it becomes irrelevant, out of scope, or blocked due to changing project requirements. Skipping preserves an audit trail of the task description and reason in a skipped.md file, whereas deleting removes it entirely from the workflow history.

Yes, the Beads task management system supports logging skipped tasks to markdown. When you close a task with a provided reason, it automatically generates a skipped.md file in the project's specification directory to maintain a documented audit trail.

To close a blocked task in Beads while keeping an audit trail, you skip the task by providing a specific justification. This action closes the task in the workflow and appends the task details and reason to a skipped.md file for documentation.