req-fn-app-notification-list

Create a reviewable inventory of system notifications with recipients, triggers, and content.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-fn-app-notification-list
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-fn-app-notification-list
Source: https://github.com/ABLER-Digital-Services/ai-guild/tree/main/skills/req-fn-app-notification-list
Command: npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-fn-app-notification-list

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sends from a system to users or administrators are often scattered across code and logs, making it hard to ensure completeness and consistency; this skill consolidates them into a single reviewable notification list.

Core Features & Use Cases

  • Notification inventory creation: Identify and document all user-facing, admin-facing, and scheduled notifications with their triggering events and intended message content.
  • Structured documentation output: Produce a table-like notification list that captures recipient roles, trigger (“〜時 / 〜した場合” style), and notification content summaries without including specific email addresses.
  • Review checklist support: Verify coverage for process-linked notifications, batch error/success notifications, and enforce formatting rules to prevent leaking concrete addresses or inconsistent triggers.
  • Use Case: When you ask to “整理して” or “一覧化して,” use this skill to build a comprehensive overview of which emails (or other channels) will be sent and why.

Quick Start

Ask for the notification list by saying: 「通知一覧を作って。システムからユーザーと管理者に送られる通知を、契機と通知内容つきで一覧化して。」

Frequently Asked Questions about req-fn-app-notification-list

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

FAQPage Schema
How do I compile a notification list of all system emails and messages?

To compile a notification list, map all user and administrator system emails by recipient role, trigger event, and message content into a single reviewable inventory table without including specific email addresses.

What is the best way to document batch processing notifications and trigger events?

Documenting batch processing notifications requires mapping scheduled batch success or error triggers and summarizing message content into a structured list to verify delivery coverage and review process-linked updates.

How do I review system messaging documentation for missing notifications?

Review system messaging documentation by running a review checklist against the notification inventory to verify coverage for process-linked triggers, batch errors, and missing success notifications without leaking concrete addresses.

Can I update existing notification documentation after feature or batch changes?

You can update existing notification documentation by recompiling the trigger mapping and message content inventory to reflect new feature or batch processing changes and verifying completeness against the review checklist.

Does the notification inventory include concrete user email addresses?

The notification inventory does not include concrete email addresses; it standardizes trigger phrasing and summarizes message content using recipient roles to enforce formatting rules and prevent data leaks.