req-writer

Generate and refine Japanese requirement definition documents through guided questioning.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill req-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-writer
Source: https://github.com/takemo101/compose-workflow/tree/main/.pi/skills/req-writer
Command: npx skills add https://github.com/takemo101/compose-workflow --skill req-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and refinement of requirement definition documents, ensuring clarity and completeness by guiding users through a structured, proposal-driven questioning process.

Core Features & Use Cases

  • Guided Requirement Gathering: Asks targeted questions to elicit necessary details for requirement documents.
  • Best Practice Integration: Researches and suggests common best practices for features and security.
  • Structured Document Generation: Produces comprehensive requirement documents following a predefined template.
  • Use Case: A product manager needs to document a new user authentication feature. They provide a basic idea, and the Skill asks clarifying questions about user roles, security needs, and non-functional requirements, eventually generating a draft requirement document.

Quick Start

Use the req-writer skill to create a requirement definition document for a new project based on the idea in 'docs/memos/my-idea.md'.

Frequently Asked Questions about req-writer

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

FAQPage Schema
How do I generate a requirement definition document from a rough idea?

To generate a requirement definition document, provide a basic project idea or memo. The Skill uses a guided-questioning approach to collect business, user, and technical context, then outputs a structured specification document.

What is the best way to document functional and non-functional requirements?

The best way to document functional and non-functional requirements is through a structured template. This approach researches best practices via web search to inform proposals and captures constraints and external interfaces for completeness.

Can I use a proposal-driven approach to gather product management specifications?

Yes, you can use a proposal-driven approach to gather product management specifications. The Skill asks targeted clarifying questions about user roles, security needs, and constraints to elicit necessary details for the document.

Does this requirement generation process support writing documents in Japanese?

Yes, the requirement generation process supports writing documents in Japanese. It generates and refines requirement definition documents in Japanese while incorporating proposal-based questioning and best practice research.

What do I need to start creating structured requirement documents?

To start creating structured requirement documents, you need a basic feature idea or project memo. The Skill handles the refinement by asking targeted questions to build comprehensive proposals and detailed specifications.