skills.rest
charleshall888
charleshall888COMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements-gather

Conduct a structured requirements interview and output a Q&A markdown block.

1|Updated Apr 1, 2026
Search Tags:#requirements#interview#orchestrator#cadence#gathering#qa-block#requirements-write
One-click install
npx skills add https://github.com/charleshall888/cortex-command --skill requirements-gather
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-gather
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-core/skills/requirements-gather
Command: npx skills add https://github.com/charleshall888/cortex-command --skill requirements-gather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured requirements interview and returns a Q&A markdown block for downstream synthesis by the /requirements-write orchestrator. It does not write any files to disk.

Core Features & Use Cases

  • One-at-a-time interview cadence that surfaces intent, priorities, constraints, and boundaries.
  • Grounding: when possible, references existing code or documentation to prune questions and improve recommendations.
  • Output: delivers a ready-to-consume Q&A markdown block for the orchestrator to pass to /requirements-write.

Quick Start

Start a guided requirements interview through the cortex-core:requirements orchestrator and capture the resulting Q&A block for downstream synthesis.

Frequently Asked Questions about requirements-gather

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

FAQPage Schema
How do I conduct a structured requirements interview to capture project intent and constraints?▼

A structured requirements interview uses a one-at-a-time cadence to surface intent, priorities, constraints, and boundaries across project or area scopes, returning a formatted Q&A markdown block for downstream synthesis.

What is the best way to gather project boundaries and priorities without writing files to disk?▼

Gathering project boundaries and priorities through a guided interrogation returns a ready-to-consume Q&A markdown block directly in the conversation without writing any files to disk for downstream synthesis.

How do I ground requirements recommendations in existing code and documentation?▼

Grounding recommendations in existing code or documentation prunes unnecessary questions during the interview and improves the quality of the final Q&A block output by referencing available context.

Does the requirements interview process output a format I can pass directly to a synthesis orchestrator?▼

The requirements interview process outputs a ready-to-consume Q&A markdown block designed specifically for an orchestrator to pass directly to the requirements-write step for downstream synthesis.

Why use a one-question-at-a-time cadence for requirements gathering instead of batch surveys?▼

A one-question-at-a-time cadence enforces focused interrogation during requirements gathering, systematically surfacing specific constraints and boundaries without overwhelming the respondent before generating the final markdown block.

Related Skills

Explore More Product & Management Skills→
amazingloft999-droidamazingloft999-droid
356

grill-with-docs

Interrogate product plans against the domain model and update CONTEXT.md and ADRs.

Community
Advanced
nzkbuildnzkbuild
3

steroid-specify

Generate a formal specification document from a markdown vibe file.

Community
Advanced
JotJuniorJotJunior
21

briefing

Conduct structured discovery interviews to capture project context into briefing documents.

Community
Intermediate
Growthub-aiGrowthub-ai
48

growthub-video-generation

Bind local reference images as typed data URLs for Veo and Vertex video generation.

Official
Advanced