analyzing-banking-requirements

Generates compliance-validated PRDs with API contracts for regulated banking workflows.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill analyzing-banking-requirements-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyzing-banking-requirements
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/analyzing-banking-requirements
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill analyzing-banking-requirements-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Raw business requests for banking and lending features often reach engineering without formal requirements or regulatory review, causing compliance gaps discovered late in development. This Skill converts unstructured asks into a formal PRD with KYC, AML, and PCI-DSS compliance mapping before any architecture or code work begins. ## Core Features & Use Cases - Spec Mode: Analyzes a raw business request and produces a detailed PRD with compliance mapping, edge cases, and partner-bank API contract sections covering auth model, idempotency, and PII flow direction. - Audit Mode: Reviews an existing PRD for KYC / AML / PCI-DSS gaps and outputs a severity-ranked gap list (P1/P2/P3) with required remediations. - Compliance Verdict Gate: Every output ends with a green / yellow / red verdict; unresolved violations halt the spec as a P1 Blocker naming the regulation and a safer alternative. - Use Case: A product manager pastes a raw feature ask for a cross-border lending flow in Southeast Asia. The Skill drafts the PRD, applies PDPA and OJK checklists, maps the identity-verification vendor API, and flags a missing sanctions-screening requirement as a P1 blocker. ## Quick Start Draft a compliance-checked PRD from this raw business request for a borrower onboarding flow in Indonesia, including the KYC checklist and partner API contract section.

Frequently Asked Questions about analyzing-banking-requirements

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

FAQPage Schema
How do I write a PRD for a banking feature with compliance requirements?▼

Provide the raw business request including stakeholders, target geography, and data classes touched. The Skill runs KYC, AML, and PCI-DSS checklists, maps partner APIs, and outputs a PRD where every compliance-relevant statement cites its regulation, ending with a green/yellow/red verdict.

How to audit an existing PRD for KYC and AML gaps?▼

Use audit mode with the existing spec as input. The Skill reviews it against the per-regulation checklists and returns a gap list ranked P1/P2/P3 with required remediations, rather than rewriting the document.

Which regulations does the compliance mapping cover?▼

The checklists cover KYC, AML, PCI-DSS, PDPA variants for Singapore, Thailand, and Malaysia, GDPR, and sector regulators OJK (Indonesia), MAS (Singapore), and BOT (Thailand). Applicability is determined by operating geography and the data classes the requirement touches.

What happens when a compliance violation is found in a requirement?▼

The Skill stops generating the spec and outputs a P1 Blocker Warning naming the regulation, the offending requirement, and a safer alternative. The spec is not deliverable until the blocker is resolved by the named stakeholder.

Can this skill design the system architecture or write backend code?▼

No. It deliberately excludes architecture design, executable code, migrations, and deploy scripts. Those tasks are deferred to separate architecture and backend-coding skills; this one produces documentation only.

What information is needed before drafting a banking PRD?▼

Provide stakeholders, target geography, and the data classes involved such as PII, PAN, KYC documents, or transaction history. For partner integrations, supply the vendor's OpenAPI or Swagger documentation so the API contract section can capture auth model and PII flow direction.