using-just-demand

Routes agent work through the just-demand workflow lifecycle and clarification gates.

Updated May 21, 2026
One-click install
npx skills add https://github.com/Sighthesia/just-demand --skill using-just-demand-sighthesia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-just-demand
Source: https://github.com/Sighthesia/just-demand/tree/main/.opencode/skills/using-just-demand
Command: npx skills add https://github.com/Sighthesia/just-demand --skill using-just-demand-sighthesia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents drift between roles, forget decisions, and start editing code before the goal is clear. This Skill enforces a routing-first workflow so every repo task passes through clarification, intake, execution, verification, and closeout instead of ad-hoc prompting. ## Core Features & Use Cases - Mandatory skill routing: loads first for repo work and directs each turn to the correct workflow skill (clarification, intake, execution, verification, or lesson capture). - Clarification and anti-sycophancy gates: blocks edits and subagent dispatch until the expected effect and plan are approved, and challenges weak user premises before optimizing. - Skill-only fallback: when runtime plugins are unavailable, it self-enforces task readiness via just-demand . list-active before any write or subagent dispatch. - Use Case: A user reports "the export button stopped working." Instead of patching immediately, the agent loads this skill, runs socratic clarification to pin down the expected behavior, creates an intake, promotes a formal task, then executes and verifies through the workflow. ## Quick Start Ask the agent to handle a bug report or feature request in this repo and it will load this skill first to route the work through clarification and the formal task workflow.

Frequently Asked Questions about using-just-demand

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

FAQPage Schema
How do I route agent work through a structured workflow in OpenCode?▼

Load the using-just-demand skill first for any repo work. It routes each turn to the right workflow skill: socratic-clarification for new or ambiguous requests, just-demand-intake for new tasks, and execution or verification skills for ready formal tasks.

How do I stop an AI agent from editing code before clarifying requirements?▼

Use a clarification gate that blocks writes and subagent dispatch until the expected effect and plan are approved. This skill treats clarification as mandatory for high-risk or ambiguous work and requires a promoted formal task before execution.

What is the difference between create-intake and promote in just-demand?▼

create-intake only records a draft work item, while promote converts it into a formal task authorized for execution. The list-active command stays empty until a task is promoted, and promotion is blocked when clarification fields are missing.

When should a subagent be dispatched instead of running in the main session?▼

Dispatch only when all six eligibility gates and all three net-benefit questions pass. Any failed or uncertain answer means the main agent executes, even for multi-file or long-context work; small reads and script-verifiable checks always stay in the main session.

What happens if the just-demand plugins are unavailable?▼

The skill-only fallback applies: before any write or subagent dispatch, run just-demand . list-active, confirm a ready formal task exists with required context files, and otherwise enter clarification and intake instead of editing inline.