analyze

Generates a System Requirement Masterplan from business needs in Thai.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/natthasath/natthasath-marketplace --skill analyze-natthasath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/natthasath/natthasath-marketplace/tree/main/plugins/masterplan/skills/analyze
Command: npx skills add https://github.com/natthasath/natthasath-marketplace --skill analyze-natthasath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning vague business needs into actionable functional and technical requirements is difficult, and missing requirements cause scope creep and team misalignment. This Skill acts as a System Analyst that produces a structured System Requirement Masterplan ready for development teams. ## Core Features & Use Cases - Structured Masterplan Generation: Produces an 8-section requirement document covering system objectives, stakeholders, functional and technical requirements, non-functional requirements, diagrams, roadmap, and risk mitigation. - Artifact Output in Thai: Delivers the masterplan as a ready-to-use Artifact written in Thai, suitable for sharing with stakeholders and management. - Summary Mode: Typing "done", "summary", or "สรุป" lists key questions and technical terminology related to the masterplan. - Use Case: A project lead describes a new internal approval system in plain language and invokes /analyze to receive a complete requirement specification, then continues to /architect for system design. ## Quick Start Invoke /analyze with a description of your business needs, for example by asking to turn the described approval workflow into a System Requirement Masterplan.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I create a system requirement document from business needs?▼

Invoke /analyze with a description of your business needs. The Skill acts as a System Analyst and generates a System Requirement Masterplan covering objectives, stakeholders, functional and technical requirements, roadmap, and risks as a Thai-language Artifact.

What sections does a System Requirement Masterplan include?▼

The masterplan includes eight sections: system objectives, stakeholders, core functional requirements, technical requirements, non-functional requirements, system diagrams, a phased development roadmap, and risks with mitigation approaches.

Does the analyze skill trigger automatically in conversation?▼

No, it is invoked manually via the /analyze command only, with disable-model-invocation enabled. It is designed to run after /gather and before /architect in the masterplan workflow.

Can I attach requirement notes or use case documents?▼

Yes, attached files such as requirement checklists, use case diagrams, or meeting notes like requirement_notes.docx or stakeholder_map.pdf are used to ground the analysis and reduce repeated stakeholder questions.

What language is the requirement document output in?▼

The masterplan is delivered in Thai as an Artifact. Typing done, summary, or สรุป produces a list of key questions and technical terminology related to the masterplan.