Skip to content
Forgeplan

forgeplan_blocked

Show artifacts that are blocked by unmet structural dependencies. An artifact is “blocked” when it references another artifact (via based_on, refines, supersedes, or contradicts) that is still in draft state — meaning the prerequisite decision has not been activated yet. deprecated and superseded prerequisites are treated as resolved, not blockers.

Category: Dashboards & Graph

When an agent calls it

Section titled “When an agent calls it”
  • Sprint planning — determine which artifacts are ready to work on vs waiting on upstream decisions.
  • Before activation — confirm an artifact has no unmet prerequisites before calling forgeplan_activate.
  • Bottleneck diagnosis — identify the upstream draft that is blocking many downstream artifacts.
  • Session start — quickly see “what’s ready to pick up” after restoring context.

Input parameters

Section titled “Input parameters”
NameTypeRequiredDescription
idstringnoArtifact ID to check. If omitted, lists all blocked artifacts.

Schema source: crates/forgeplan-mcp/src/types.rs::BlockedParams

Returns

Section titled “Returns”
{
  "blocked": [
    {
      "id": "RFC-006",
      "kind": "rfc",
      "status": "draft",
      "blocked_by": [
        { "id": "PRD-039", "status": "draft", "relation": "based_on" }
      ]
    }
  ],
  "total_blocked": 1
}

Example invocation

Section titled “Example invocation”
{}

Or for a single artifact:

{ "id": "RFC-006" }

Typical sequence

Section titled “Typical sequence”
  1. forgeplan_blocked — list blocked artifacts.
  2. forgeplan_get on the upstream blocked_by — check what it needs.
  3. forgeplan_activate the upstream once validation passes.
  4. forgeplan_blocked again — confirm downstream is now unblocked.

CLI equivalent

Section titled “CLI equivalent”
Terminal window
forgeplan blocked
forgeplan blocked RFC-006

See also

Section titled “See also”