requirements

Gather project requirements through interviews and write cortex/requirements/*.md files.

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/charleshall888/cortex-command --skill requirements-charleshall888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/charleshall888/cortex-command/tree/main/plugins/cortex-core/skills/requirements
Command: npx skills add https://github.com/charleshall888/cortex-command --skill requirements-charleshall888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gathering and documenting project requirements is manual, time-consuming, and error-prone; this Skill provides a deterministic path to interview stakeholders and produce formal requirement artifacts.

Core Features & Use Cases

  • Orchestrated interviews: routes prompts through /requirements-gather and /requirements-write to generate cortex/requirements/*.md.
  • Scope-aware: supports project-level and area-level documents, plus a list enumeration for governance workflows.
  • Artifact generation: writes the final requirement document to cortex/requirements/ and coordinates with the commit workflow.

Quick Start

Run /cortex-core:requirements to start a project-level interview and generate cortex/requirements/project.md.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I automate gathering project requirements through stakeholder interviews?

Automated interviews for gathering project requirements route prompts through a deterministic flow using /requirements-gather and /requirements-write to produce formal artifacts. This orchestrates stakeholder questions end-to-end without manual documentation workload.

What is the best way to document project scope and area scope for governance workflows?

Documenting project scope and area scope is handled through scope-aware generation that supports project-level documents, area-level documents, and list enumeration. It writes final artifacts to cortex/requirements/*.md for governance workflows.

How do I generate formal requirement documents from planning interviews?

Generating formal requirement documents from planning interviews applies a deterministic path through /requirements-gather and /requirements-write. This produces cortex/requirements/*.md files and integrates with cortex-core:commit for artifact coordination.

Can I use automated requirements gathering for both project-level and area-level planning?

Automated requirements gathering supports both project-level and area-level planning scope. You can start a project-level interview by running /cortex-core:requirements to generate cortex/requirements/project.md.

Does the requirements workflow integrate with commit workflows for artifact management?

The requirements workflow integrates with cortex-core:commit for artifact management. After writing requirement documents to cortex/requirements/, it coordinates with the commit workflow to finalize formal artifacts.

Why does manual requirements gathering cause errors and how can I avoid them?

Manual requirements gathering causes errors because it is time-consuming and prone to human oversight during documentation. A deterministic interview flow eliminates this by automating stakeholder prompts and writing structured artifacts.