Client Requirement Extraction Skill ⭐

The problem

Vague client emails and messy chat logs lead to scope creep, missed deadlines, and unbilled work. Developers and PMs often waste hours manually parsing informal communication into structured tasks while missing critical assumptions or contradictions.

What it does

• Extracts business objectives, functional requirements, and technical constraints from messy chat or meeting transcripts.
• Classifies data by evidence level, distinguishing between explicit client requests and your own working assumptions.
• Maps deliverables to specific requirements, including quantities, file formats, and ownership.
• Identifies contradictions in client statements, such as conflicting deadlines or platform requirements, before work begins.
• Generates a prioritized list of clarification questions to resolve blocking unknowns.

Why this beats prompting it yourself

A standard LLM often "hallucinates" clarity, making guesses about vague deadlines or missing features just to be helpful. This skill enforces strict evidence levels, ensuring you never mistake a reasonable inference for a confirmed requirement, which protects you from liability and scope creep.

Use cases

• Converting a 20 minute raw Zoom transcript into an implementation-ready requirements document.
• Turning a chaotic WhatsApp thread into a structured table of deliverables and deadlines.
• Auditing a client brief for missing technical constraints, security needs, or compliance gaps.
• Generating Gherkin-style acceptance criteria directly from informal project notes.

Known limitations

Cannot resolve relative dates like "next Friday" unless a specific reference date is provided in the context.