flow-block

Marks a task as blocked in Beads with a documented reason and updates its status.

15|4|Updated Jan 20, 2026

Search Tags:#workflow #developer tools #task management #beads #blocking

Ready to run

npx skills add https://github.com/cofin/flow --skill flow-block

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-block
Source: https://github.com/cofin/flow/tree/main/templates/codex/skills/flow-block
Command: npx skills add https://github.com/cofin/flow --skill flow-block

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to formally mark a task as blocked, providing a clear reason and ensuring this status is recorded and communicated.

Core Features & Use Cases

Task Blocking: Immediately flag a task that cannot proceed.
Reason Documentation: Capture the specific reason why a task is blocked.
Status Update: Updates the task status in Beads, the system of record.
Use Case: If a developer encounters an external dependency issue that prevents them from completing a coding task, they can use this Skill to mark the task as blocked and document the dependency issue.

Quick Start

Mark the current in-progress task as blocked with the reason 'Waiting for API key from security team'.

Frequently Asked Questions about flow-block

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I mark a developer task as blocked with a specific reason?▼

To mark a task as blocked, you provide a reason which is then documented while the task status is updated. The skill identifies the target task using a provided ID or by querying the current in-progress task from Beads or Plan.md.

What happens to task status in Beads when a task is blocked?▼

When a task is blocked, its status is updated in the Beads system to reflect the blockage. A dedicated file logs the blocking event with the reason, and subsequent actions are suggested for the user.

How do I document why a blocked task cannot proceed in my workflow?▼

You can document why a blocked task cannot proceed by providing a specific reason when marking it. This reason is captured and logged to a dedicated file, ensuring the dependency issue is formally recorded.

Can I block a task without knowing its ID?▼

Yes, you can block a task without knowing its ID. The skill automatically queries the current in-progress task from Beads or Plan.md if a specific task ID is not provided.

Does task blocking work with Plan.md?▼

Yes, task blocking works with Plan.md. If a task ID is not provided, the skill queries the current in-progress task directly from Plan.md to identify which task to mark as blocked.