just-demand-intake

Shapes clarified user requests into structured intake records for formal task promotion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New goals, bug reports, and feature requests often arrive vague or half-specified, causing agents to guess at scope, expected behavior, and approach. This Skill converts clarified user intent into a structured intake record with explicit approval gates before any implementation begins. ## Core Features & Use Cases - Structured Intake Capture: Records expected behavior, actual behavior, reproduction, scope, blocking questions, and anti-outcomes in user-language buckets. - Final Artifact Requirements: Enforces decision cards, option matrices, chosen approaches, implementation plans, and visible acceptance criteria before promotion. - Promotion Gates & Recovery: Defines hard promotion gates per work type (design/implementation vs. bug/mismatch) plus recovery recipes for failed promote commands. - Use Case: A user reports a UI animation that feels out of sync. The Skill routes through socratic clarification, captures the expected vs. actual behavior, records a visible-effect card with touchpoints and acceptance checks, and blocks promotion until the user approves. ## Quick Start Ask the agent to intake a new feature request or bug report and shape it into an approved work item before any code changes begin.

Frequently Asked Questions about just-demand-intake

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

FAQPage Schema
How do I turn a vague feature request into an approved task?▼

Run the request through socratic clarification first, then record the approved artifact in an intake file with scope, final expected effect, chosen approach, and implementation plan. Promotion is blocked until those required sections and explicit user approval are present.

What fields are required before promoting an intake to a task?▼

Design and implementation work requires Scope, Final Expected Effect, Chosen Approach, Final Implementation Plan, and Approval. Bug or mismatch reports require Scope, Expected Behavior, Actual Behavior, and Reproduction.

When should a question be treated as blocking during intake?▼

A question is blocking when guessing the answer could change the implementation path, validation criteria, user-facing behavior, or acceptable scope. Do not demote it just because a likely answer exists; proceed only if the user already answered or the change is safely reversible.

What happens if the promote command fails during intake?▼

Read the error text, update the same intake markdown file with the named missing sections, and rerun the same promote command. Do not create a second intake or edit task.json directly.

Does intake work without the workflow plugins installed?▼

Yes, in no-plugin fallback mode the agent self-enforces the transition: after clarification approval, it creates or promotes the intake before any write tool or execution subagent. This fallback is best-effort and cannot hard-block tools.