req

Guide structured interviews to capture development requirements into a Markdown template.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/wakuwaku-inc/req-skill --skill req
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: req
Source: https://github.com/wakuwaku-inc/req-skill/tree/main/skills/req
Command: npx skills add https://github.com/wakuwaku-inc/req-skill --skill req

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill guides structured interviews to capture complete development requirements and auto-populate a standardized Markdown template, reducing vagueness and rework.

Core Features & Use Cases

  • Guided interviews to extract issues, requests, and acceptance criteria, then assemble a consistent requirements document.
  • Workspace-aware output paths that write to docs/requirements or docs/req-skill/requirements depending on setup.
  • Update mode support for editing existing requirement docs via local files or Notion pages, with safe fallbacks and versioning ideas.

Quick Start

Ask questions to collect a development requirements document and write it to docs/requirements/YYYY-MM-DD_<title>.md.

Frequently Asked Questions about req

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

FAQPage Schema
How do I turn interview notes into structured requirements documents?▼

Creating structured requirements documents from interviews is achieved by this skill guiding structured conversations to extract requests and acceptance criteria, then assembling the captured data into a consistent, ready-to-write Markdown file.

Can I update existing requirements docs via Notion pages?▼

Updating existing requirements docs via Notion pages is fully supported. The skill features an update mode for editing local files or Notion pages, utilizing workspace-aware path resolution to ensure outputs are correctly located.

How do I make sure my Markdown requirements are not missing critical data?▼

Ensuring Markdown requirements contain all critical data is handled by the skill enforcing a strict non-fabrication policy and prompting for missing information during the interview, guaranteeing a complete and ready-to-write document.

Does the requirements template support workspace-aware output paths?▼

The requirements template fully supports workspace-aware output paths, automatically resolving and writing generated Markdown files to designated directories like docs/requirements based on your specific project setup.

What is the best way to capture development requests without writing vague requirements?▼

Capturing development requests without vagueness is best achieved through a guided interview process that extracts specific issues and acceptance criteria, assembling them into a standardized template to eliminate ambiguity and prevent rework.