masterdata-requirement-analyzer

Analyze a strategy's requirements folder and generate a Markdown file structure report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Wonderplanet/glow-brain --skill masterdata-requirement-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: masterdata-requirement-analyzer
Source: https://github.com/Wonderplanet/glow-brain/tree/main/.claude/disable-skills/masterdata-requirement-analyzer
Command: npx skills add https://github.com/Wonderplanet/glow-brain --skill masterdata-requirement-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

施策の要件フォルダを分析し、要件ファイル構成ドキュメントを生成します。

Core Features & Use Cases

  • 要件フォルダ分析: 要件のファイル構成と依存関係を把握
  • 要件ファイル構成の自動生成: 要件ファイル構成.md を生成
  • Use Case: 新施策の要件を初期分析から整理

Quick Start

Quick Start: 施策ディレクトリを指定して要件ファイル構成を生成します。例:

  • Skill(skill: "masterdata-requirement-analyzer", args: "マスタデータ/施策/新春ガチャ")

Frequently Asked Questions about masterdata-requirement-analyzer

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

FAQPage Schema
How do I analyze a requirements folder structure and generate documentation?

Requirements folder analysis identifies file organization, extracts titles and headings, traces inter-file references, and generates a structured Markdown document mapping the requirements file structure, dependencies, and data flow for stakeholder review.

What does a requirements file structure document include?

The generated document includes an overview of the requirements folder, complete file structure with indexed sections, inter-file relationships and dependencies, data flow visualization, and usage notes to help teams understand requirement organization and dependencies.

Can I use this with large requirements files?

Yes. The Skill handles large files by reading only header sections when content exceeds 25k tokens, preserving encoding compatibility while extracting metadata efficiently to avoid processing bottlenecks.

What file types and organizational patterns does this support?

It processes numbered section directories (01_, 02_), index and table-of-contents files, templates, and backup files within a requirements folder, extracting titles, headings, and cross-references to build a comprehensive structural report.

Where does the generated documentation get saved?

The final structured Markdown document is automatically saved at the strategy root directory as '要件ファイル構成.md', making it immediately accessible to stakeholders and team members for reference.

What metadata does the analysis extract from requirements files?

The Skill extracts titles, headings, internal links, and file relationships, then categorizes and orders them to preserve the logical structure while identifying unused items and backup files.