req-setup

Initialize a per-product requirements workspace at docs/req-skill.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured workflow to bootstrap and manage a per-product context workspace at docs/req-skill, ensuring a consistent starting point for requirements capture and reducing miscommunication during product launches.

Core Features & Use Cases

  • Scaffold a workspace from plugin templates (product.md, glossary.md, decisions.md, references.md) and render them into a ready-to-use docs/req-skill structure.
  • Scan existing docs under the target workspace for terms, decisions, and references to surface candidate content for the glossary, decisions, and references files.
  • Guide product interviews and step-by-step prompts to collect product name, description, and stakeholders, then populate the workspace with structured content.
  • Support atomic, template-driven writes and safe write practices to assemble final workspace artifacts.

Quick Start

Run /req-setup in your project directory to initialize the workspace at docs/req-skill and begin the guided setup.

Frequently Asked Questions about req-setup

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

FAQPage Schema
How do I set up a product requirements workspace with structured templates?▼

To set up a product requirements workspace, run /req-setup in your project directory to scaffold standardized templates including product.md, glossary.md, decisions.md, and references.md at docs/req-skill.

What is the best way to extract existing decisions and terms from project documentation?▼

Extracting decisions and terms from project documentation is handled automatically by scanning existing docs under your target workspace to surface candidate content for the glossary, decisions, and references files.

Can I automate requirements capture through guided product interviews?▼

Automating requirements capture through product interviews is supported via step-by-step prompts that collect product name, description, and stakeholders, then populate your workspace with structured content.

Does req-setup support atomic writes when assembling workspace artifacts?▼

Atomic writes are fully supported during workspace assembly, utilizing safe write practices and template-driven assembly to render final artifacts without data corruption.

What limitations exist when fetching external references during workspace initialization?▼

External references are fetched using MCP-aware capabilities during workspace initialization, though the scope of references depends on accessible external sources and existing document content within your target workspace.