/ block
Flag the current issue as blocked with a reason and notify the team.
The /block command marks the active issue as blocked. Use this
when you can't proceed due to external dependencies or missing information.
Usage
/block "Waiting for API credentials" /block --notify @teammate "Need design approval" Options
| Option | Description | Default |
|---|---|---|
--notify | Mention users in the blocking comment | None |
--priority | Escalate priority when blocking | No change |
What Happens
- Status Update: Issue transitions to "Blocked"
- Blocking Comment: Reason added as comment with timestamp
- Session Paused: Current session is paused (not ended)
- Notifications: Mentioned users are notified
Blocking Comment
FlyDocs adds a structured comment:
**Blocked** - Waiting for API credentials
Session paused at 45 minutes.
Progress: 2/4 acceptance criteria complete.
@teammate Can you help with this? Unblocking
When the blocker is resolved, use /activate to resume work.
FlyDocs will restore your session context.
/activate ENG-145 Blocked Issue Visibility
Blocked issues appear prominently in /status output and
session start summaries to ensure visibility.