intake

Capture mission requirements through interactive questioning into a validated JSON spec.

15|4|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/choam2426/geas --skill intake-choam2426
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/choam2426/geas/tree/main/plugin/skills/intake
Command: npx skills add https://github.com/choam2426/geas --skill intake-choam2426

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It addresses the uncertainty and hidden assumptions in raw mission descriptions by guiding users through a structured, question‑by‑question intake process that produces a complete, immutable mission specification.

Core Features & Use Cases

  • Interactive questioning: Asks targeted, single‑question prompts to uncover scope, constraints, acceptance criteria, and risks.
  • Spec generation: Builds a validated spec.json containing scope, constraints, risk notes, and other essential fields.
  • Mode selection & approach proposals: Determines the appropriate execution depth (lightweight, standard, full_depth) and offers concrete implementation options.
  • Lightweight variant: Provides a streamlined intake for minor feature additions in existing projects.

Quick Start

Invoke the intake gate with /geas:mission and follow the prompted questions to create a frozen mission spec.

Frequently Asked Questions about intake

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

FAQPage Schema
How do I formalize mission requirements before starting an AI-driven project workflow?

To formalize mission requirements, use an interactive intake process that captures scope, acceptance criteria, constraints, and risks. This structured approach clarifies raw mission descriptions and records essential fields in a validated JSON spec before execution begins.

What is the best way to freeze project specifications and prevent scope creep in AI orchestration?

Freezing project specifications is best achieved through a question-by-question intake process that uncovers hidden assumptions. It generates an immutable mission specification, ensuring complete scope definition and preventing changes during AI orchestration execution.

How do I capture task contracts and acceptance criteria using interactive prompts?

You capture task contracts by answering targeted, single-question prompts during the intake process. This interactive questioning systematically extracts acceptance criteria, scope boundaries, and risk notes, compiling them into a formal specification.

Can I use a lightweight intake process for minor feature additions in existing projects?

Yes, you can use a lightweight intake variant designed specifically for minor feature additions in existing projects. This streamlined process bypasses exhaustive questioning while still producing the necessary validated specification for execution.

How do I determine the appropriate execution depth for a mission specification?

You determine execution depth during the intake process through mode selection. The system analyzes your captured requirements and proposes an appropriate depth level—lightweight, standard, or full_depth—along with concrete implementation options for the mission.