req-fn-app-process-list

List online UI-triggered server-side actions as structured process records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams consistently document and update server-side processes triggered by online UI actions, avoiding missing or ambiguous backend steps during requirement reviews.

Core Features & Use Cases

  • Server process listing for online UI: Converts button/link/form-triggered server-side operations into a structured “process list” that supports review and handover.
  • Strict inclusion/exclusion rules: Targets only online server requests and explicitly excludes batch processing and JavaScript-only client-side events.
  • Deterministic documentation workflow: Guides mapping of “before/after screen function IDs,” transitions, actor names, and a consistent process ID format (P-NNN).

Quick Start

Ask the AI to generate an updated “処理一覧” using your current feature list, producing entries for every online button/link while excluding batch and JavaScript-only client events.

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

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

FAQPage Schema
How do I document server-side processes triggered by UI buttons for requirement reviews?

Generate a structured process list by mapping online UI-triggered server requests to records with deterministic IDs (P-NNN), actor names, and before/after function IDs (F-O-NNN) for auditable requirement reviews.

What is the best way to map screen transitions and actors for backend documentation?

Map screen transitions and actors by listing each online server-side action as a process record that references actor definitions and links before/after screen function IDs, ensuring consistent backend documentation across requirement changes.

Does the process list include batch processing and JavaScript-only client events?

No, the process list explicitly excludes batch processing and JavaScript-only client-side events, targeting only online UI-triggered server-side actions to maintain a focused and auditable process inventory for requirement reviews.

How do I generate a structured process inventory from an existing feature list?

Provide your current feature list to the AI to produce an updated process inventory, generating structured entries for every online button and link operation while adhering to the process list template and deterministic ID conventions.

Why use deterministic process ID rules like P-NNN for requirement consolidation?

Deterministic process ID rules like P-NNN ensure consistent tracking and linkage of before/after function IDs during requirement consolidation, preventing missing or ambiguous backend steps across change reviews.