Menu

Individual skill

requirements-extractor

0upvotes

Converts vague, informal, or incomplete requirements into clear functional and technical requirements, and flags open questions. Use when a request is too ambiguous to implement directly.

skills/reasoning/requirements-extractor/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Turn a vague request ("make it faster," "add user profiles," "it should feel more modern") into explicit, checkable functional and technical requirements, and surface the ambiguities that need an answer before implementation can start.

## When to Use

- A feature request, ticket, or user message is underspecified for direct implementation.
- Before starting implementation on anything nontrivial, to confirm scope with the requester.
- When a team keeps re-litigating "wait, was that supposed to include X?" mid-build.

## What to Analyze / Do

1. **Restate the request** in plain language to confirm the core intent.
2. **Extract functional requirements** — what the system must do, from a user's perspective, as discrete checkable statements ("User can reset their password via email").
Back to top