docs: normalize README with Why and What

Author: fdelbrayelle

README.md

@@ -35,17 +35,18 @@
 </p>
 <p align="center" style="color:grey;"><i>Get started with Kestra in 4 minutes.</i></p>
 
-
 # Kestra Transform Plugin
 
-This repository allows you to transform data coming from a JSON for instance.
+## Why
+
+- What user problem does this solve? Teams need a reliable way to operate Transform from orchestrated workflows instead of relying on manual console work, ad hoc scripts, or disconnected schedulers.
+- Why would a team adopt this plugin in a workflow? It keeps Transform steps in the same Kestra flow as upstream preparation, approvals, retries, notifications, and downstream systems.
+- What operational/business outcome does it enable? It reduces manual handoffs and fragmented tooling while improving reliability, traceability, and delivery speed for processes that depend on Transform.
 
-This repository contains several transformation plugins:
-* [Grok](https://github.com/kestra-io/plugin-transform/tree/main/plugin-transform-grok)
-* [JSONata](https://github.com/kestra-io/plugin-transform/tree/main/plugin-transform-json)
-* [Transform (Records)](https://github.com/kestra-io/plugin-transform/tree/main/plugin-transform-records)
+## What
 
-![Kestra orchestrator](https://kestra.io/video.gif)
+- Provides plugin components under `io.kestra.plugin`.
+- Keeps the implementation focused on the integration scope exposed by this repository.
 
 ## Documentation
 * Full documentation can be found under: [kestra.io/docs](https://kestra.io/docs)