Skip to content

[feature] surface "why is this quest blocked" without requiring SQL access #29

Description

@kunallanjewar

Summary

When a quest is in blocked status, there's no first-class way to ask "what's blocking it?" — agents have to fall back to sqlite3 ~/.guild/quest.db and inspect the dependency edges by hand, which violates the trust model that says guild operations should go through the API.

Acceptance

  • A verb (extending guild quest scroll QUEST-N or a new guild quest why QUEST-N) shows the dependency graph for the quest: which deps are fulfilled, which aren't, and what's blocking acceptance.
  • Output is agent-readable without requiring .schema lookups.
  • MCP equivalent: either quest_scroll returns structured dependency state, or a new quest_status tool surfaces the same.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions