---
name: "requirement-plater"
description: "Plate scattered requirement sources — PRDs, notes, screenshots, chat snippets — into one flattened Markdown requirement file that test-generator consumes directly."
type: skill
roles: ["Quality Assurance", "Product", "Project Management"]
activities: ["Planning", "Documentation", "Quality Assurance"]
tags: ["Requirements", "SoW", "QA Pipeline", "Documentation"]
owner: "Yayan Adipraja"
sourceUrl: "https://drive.google.com/drive/folders/1GPYfnfCX-aLEswtiEKsSb059DGz7FX9Q"
---

# requirement-plater

> Plate scattered requirement sources — PRDs, notes, screenshots, chat snippets — into one flattened Markdown requirement file that test-generator consumes directly.

## Overview

requirement-plater is the first stop in a QA pipeline. It consolidates scattered requirement sources — PRDs, user flow descriptions, meeting notes, screenshots, chat snippets, exported Figma frames — into a single flattened Markdown requirement file at `SoW/<feature_slug>.md`, ready for the `test-generator` sub-agent to consume.

The skill is a **plater and clarifier, not an inventor**: it reorganizes, deduplicates, and surfaces gaps as Open Questions, but never fabricates functionality. You review and approve the plate conversationally before it goes downstream.

## Key Conventions

- **Output tree** — `SoW/<feature_slug>.md`, with smart versioning (`.v2.md`, `.v3.md`) on updates
- **Feature slugs** — project-namespaced, e.g. `bdf-bot-otp-flow`, `japfa-form-registration`; the slug groups test scenarios downstream
- **Channel taxonomy** — a closed enum (`web`, `whatsapp`, `qiscus-widget`) shared in lockstep with `test-generator` and `test-executor`
- **Local files only** — Figma URLs, Jira tickets, or Notion pages must be exported/pasted first; the skill never fetches external systems

## When to Use

- You have one or more requirement files and the next step is QA test generation
- A user flow was described informally and needs structuring
- A kick-off or product discussion just ended and the outcomes need capturing as a requirement file

Not for generating test scenarios (that's `test-generator`), writing MoMs, or producing slides/timelines — those have their own skills.

## How to Access

Get the skill from the [shared Drive folder](https://drive.google.com/drive/folders/1GPYfnfCX-aLEswtiEKsSb059DGz7FX9Q) and install it into your Claude skills. Run it from the sub-project root so the `SoW/` folder lands in the right place.

## Example Prompts

```
Plate these requirements for test generation: [attach PRD + flow notes]
```

```
Consolidate these three docs into one SoW file for the
bdf-dashboard-login feature.
```

## Related Tools

- [uat-dashboard](/tools/uat-dashboard/) — downstream UAT reporting once tests run