1
00:00:00,004 --> 00:00:01,955
This one is about agent roles.

2
00:00:04,892 --> 00:00:07,102
A role is what the agent does in a stage,

3
00:00:07,102 --> 00:00:09,216
like reviewing or implementing.

4
00:00:09,216 --> 00:00:10,398
It doesn't depend on the tool,

5
00:00:10,398 --> 00:00:13,570
so the same role works for both Claude and Codex.

6
00:00:14,068 --> 00:00:18,906
Four come ready-made: analyst, implementer, reviewer and checker.

7
00:00:18,906 --> 00:00:20,945
I'm going to create a security one.

8
00:00:20,945 --> 00:00:24,455
It looks for secrets in the code and for unvalidated input,

9
00:00:24,455 --> 00:00:27,660
writes what it finds to a file, and doesn't change the code.

10
00:00:27,660 --> 00:00:29,610
This role has a rule of its own:

11
00:00:29,610 --> 00:00:32,139
cite the file and line for each finding.

12
00:00:32,901 --> 00:00:36,222
In New stage, I pick the role under More options.

13
00:00:36,222 --> 00:00:39,699
The task itself is short, just analyze the code folder,

14
00:00:39,699 --> 00:00:41,759
because the rest is already in the role.

15
00:00:43,323 --> 00:00:46,507
It wrote its findings to SEGURANCA.md.

16
00:00:46,507 --> 00:00:49,794
git status shows that file and the PrumoGrid ones,

17
00:00:49,794 --> 00:00:51,785
and nothing inside the code folder.

18
00:00:51,785 --> 00:00:54,827
In Flow, the roles show up as buttons.

19
00:00:54,827 --> 00:00:57,535
Clicking implementer gives me a planned stage with that role right

20
00:00:57,535 --> 00:01:02,217
away, and on the card I can change it later, under Role and sequence.

21
00:01:04,341 --> 00:01:08,091
A role can also point to a skills folder for the agent to look at.

22
00:01:08,091 --> 00:01:11,041
That field is optional; I hardly ever use it.

23
00:01:11,881 --> 00:01:13,352
In the next one, I'll put all of this

24
00:01:13,352 --> 00:01:15,960
together in an operation with three agents.