requirement-intake

Parse user report requests into a structured JSON requirements schema.

Updated May 9, 2026

Search Tags:#analysis #normalization #scope #report #requirement #objectives #intake

Ready to run

npx skills add https://github.com/HwFee/AgentProject --skill requirement-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirement-intake
Source: https://github.com/HwFee/AgentProject/tree/main/skills/requirement-intake
Command: npx skills add https://github.com/HwFee/AgentProject --skill requirement-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cleanse and analyze user requirements for report generation, extracting topics, objectives, scope, format, constraints, and keywords to create a precise, actionable brief for downstream tasks.

Core Features & Use Cases

Requirement extraction: identify topic, objectives, scope, format, constraints, and keywords from user prompts.
Normalization: convert unstructured requests into a consistent JSON schema for downstream processing.
Clarification support: propose clarifying questions to resolve ambiguities and set expectations early.

Quick Start

Provide a raw request describing a report need, and the Skill will output a structured JSON requirements object for downstream agents.

Frequently Asked Questions about requirement-intake

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

FAQPage Schema

How do I normalize vague user requests into a structured format for report generation?▼

Requirement normalization for report generation extracts topics, objectives, scope, format, constraints, and keywords from unstructured prompts. It converts vague requests into a consistent JSON schema to guide downstream document creation agents.

What is the best way to structure unstructured requirements for downstream processing?▼

Structuring unstructured requirements for downstream processing involves parsing user prompts to extract key parameters and converting them into a normalized JSON schema. This approach ensures downstream agents receive precise, actionable briefs instead of ambiguous text.

How do I extract objectives and scope from a raw text prompt for a report brief?▼

Extracting objectives and scope from a raw text prompt involves analyzing the user's request to identify these specific elements and mapping them into a structured JSON schema. This clarifies needs and sets expectations for document creation.

Can I generate clarifying questions when converting a vague request into an actionable brief?▼

Generating clarifying questions when converting a vague request into an actionable brief is supported natively. The Skill proposes targeted questions to resolve ambiguities and set expectations early in the requirement intake process.

Does requirement intake work for starting new reports from scratch with minimal input?▼

Requirement intake works for starting new reports from scratch by taking a raw request with minimal input. It cleanses and analyzes the prompt to produce a precise JSON schema, normalizing inputs for downstream processing without needing prior context.