ipms-brd

Generates traceable customer Business Requirements Documents with fit-gap analysis from survey evidence.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill ipms-brd-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ipms-brd
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/ipms-brd
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill ipms-brd-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting a customer-facing Business Requirements Document (BRD) for the iPMS performance management platform is slow and error-prone: survey answers must be converted into traceable requirements, checked against the product capability catalog, and stripped of internal notes before anything reaches the customer. This Skill standardizes that entire presales documentation workflow. ## Core Features & Use Cases - Requirement normalization: Converts survey minutes or self-declaration forms into traceable BR requirements with acceptance criteria, MoSCoW priority, and evidence references. - Fit-gap analysis: Maps every requirement against the iPMS capability catalog using a 5-level fit scale, producing separate internal and customer-facing fit-gap documents. - Single-source document generation: Builds the 15-section DOCX BRD and 7-sheet XLSX appendix from one ho-so.json file, automatically stripping internal keys prefixed with underscore. - Use Case: After four discovery interview rounds with a prospective client, consolidate the minutes into ho-so.json, run the generator, and receive a bilingual-ready BRD package with a traceability matrix and a confidentiality gate checklist before sending it for signature. ## Quick Start Ask the assistant to draft a customer BRD for a new iPMS prospect from the survey minutes in the client's 02-khao-sat folder, then generate the DOCX and XLSX package from ho-so.json.

Frequently Asked Questions about ipms-brd

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

FAQPage Schema
How do I create a BRD from customer survey results?

Collect survey minutes or the customer self-declaration form, normalize each answer into a BR requirement with acceptance criteria and evidence source, then consolidate everything into ho-so.json and run the generator script to produce the DOCX and XLSX package.

What is a fit-gap analysis in presales documentation?

Fit-gap analysis maps each customer requirement against the product capability catalog using a 5-level fit scale. Requirements with no matching capability are marked as needing development or out of scope, and high-priority gaps trigger risk entries in the BRD.

How does the skill prevent internal notes from leaking into customer documents?

Internal notes are stored in JSON keys prefixed with underscore, which the generator strips before building documents. A mandatory 7-point gate check, including grep patterns for internal terms, must pass before any file is released.

What is the difference between customer BRD and platform BRD?

The customer BRD describes what a specific client needs and is signed by them, with internal references blocked. The platform BRD is an internal document defining what iPMS itself should become, generated by a separate script from a different template.

Can a BRD be released with open questions still unresolved?

Yes, a BRD may be released containing CHO-KHACH placeholders for missing information, but never inside a Must-priority requirement. Missing evidence must become an open question in section 15 rather than a fabricated requirement.