skills.rest
ddaanet
ddaanetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements

Capture and organize functional and non-functional requirements into a structured file.

Updated Jan 19, 2026
Search Tags:#design#planning#documentation#recall#requirements#elicitation#artifact
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill requirements-ddaanet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/requirements
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill requirements-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill captures and structures requirements discussed in conversations and documents, turning them into a formal artifact that guides design and implementation.

Core Features & Use Cases

  • Extract functional and non-functional requirements from dialogue and existing artifacts, then organize them into plans/<job>/requirements.md.
  • Support semi-structured elicitation with targeted questions and open questions tracking to prevent missing essentials.
  • Ground requirements in existing memory and repository context to maintain consistency across design and runbook steps.

Quick Start

Run /requirements <job-name> to capture and seed plans/<job-name>/requirements.md.

Frequently Asked Questions about requirements

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

FAQPage Schema
How do I extract project requirements from conversations and structure them?▼

This Skill extracts requirements from conversations by identifying discussed details, eliciting missing information through targeted questions, and outputting a structured artifact at plans/<job>/requirements.md.

What is requirements elicitation and how does it prevent missing essentials?▼

Requirements elicitation draws out unstated needs. This Skill applies semi-structured elicitation with targeted questions and open questions tracking to ensure you capture all essential functional and non-functional details.

How do I document functional and non-functional requirements for software planning?▼

You document functional and non-functional requirements by grounding dialogue in repository context and recording constraints, dependencies, and open questions into the plans/<job>/requirements.md artifact.

Can I use this to capture requirements for product and project initiatives?▼

Yes, you can capture requirements for product, software, and project initiatives. The Skill supports planning and design interactions, including recall, and structures them into a formal artifact.

What's the best way to track open questions and constraints during design planning?▼

The best way to track open questions and constraints is recording them within a structured requirements artifact. This Skill logs dependencies, constraints, and open questions alongside captured functional requirements.

Related Skills

Explore More Software Engineering Skills→
Rycen7822Rycen7822
2

paper-fetch

Retrieve and verify arXiv/OpenReview research papers for quest evidence.

Community
Advanced
dobrinz123dobrinz123

gsd-discuss-phase

Extract implementation decisions and phase context into a phase-specific CONTEXT.md artifact.

Community
Advanced
c-dalyc-daly

distill

Distill episodic session learnings from EPISODES.md into persistent memory patterns in MEMORY.md.

Community
Intermediate
DoubleslashSEDoubleslashSE
4

requirements-elicitation

Gather, analyze, and document software requirements using structured elicitation techniques.

Community
Basic