---
description: "Deferred/blocked work — check on session start; create when blocked; resolve when unblocked"
alwaysApply: true
---

# Deferred Items Protocol (Optional)

Use this rule when the project uses a `deferred/` directory to track work blocked on human action, external service, or missing information (see God-Mode Phase 3.5 and Get-er-DONE).

## On Every Session Start

Before planning new work:

1. If `deferred/` exists, read `deferred/README.md` for the current inventory.
2. For any item with `state: blocked`, check its `unblock-trigger` condition (programmatically if possible).
3. If newly unblocked: inform the user and propose executing the integration steps first.
4. If still blocked: acknowledge awareness and continue with requested work.

## When Encountering New Blocks

If work is blocked on human action, external service, or missing information:

1. Create a new file in `deferred/` using the template in `deferred/README.md`.
2. Use priority prefix: P0 (critical), P1 (high), P2 (nice-to-have), P3 (future). Name format: `P[N]-[short-id].md`.
3. Include exact unblock-trigger (preferably a command that returns pass/fail).
4. Include exact AI-executable steps for integration once unblocked.

## When Resolving Items

1. Execute the integration steps from the deferred item.
2. Move the file to `deferred/resolved/` with resolution date appended.
3. Update `deferred/README.md` table (move from Current to Resolved).
4. Update any cross-referenced files.

**Note:** If the project does not have a `deferred/` directory, this rule has no effect. Session-protocol Phase 2 already includes "if project has deferred/, read README and check unblock triggers."
