1
00:00:00,000 --> 00:00:05,039
Okay, this is us back in Jira again. Check this out. You can see that it moved the other ticket

2
00:00:05,039 --> 00:00:09,439
to done. I didn't remember seeing it do that. I didn't ask it to, I don't think, I don't remember,

3
00:00:09,439 --> 00:00:15,279
but it did. Okay, so now we're going to create some more tickets. I just started writing this

4
00:00:15,279 --> 00:00:28,639
one. Let's have the first of them being from prototype, build foundation of v1 product.

5
00:00:28,639 --> 00:00:37,119
Let's start with that as a ticket. And then the next ticket is going to be add AI chat,

6
00:00:38,159 --> 00:00:48,639
but still just mutual NDA. And then the next step is expand to all legal, all supported

7
00:00:50,400 --> 00:00:56,880
legal document types. There we go. That's our three sets. This is coming in from our business.

8
00:00:57,759 --> 00:01:02,000
Let's have a look at this one. First of all, maybe this one is a bit more of a technical one,

9
00:01:02,000 --> 00:01:15,360
but this one is upgrade the prototype so that it is the proper technical foundation for the full

10
00:01:15,919 --> 00:01:27,120
v1 project, including front end, back end, and temporary database

11
00:01:29,519 --> 00:01:40,879
with scripts to start and stop, but without updating the functionality

12
00:01:41,839 --> 00:01:50,720
yet. Let's say the features, the product features. Yes, that seems like a clear instruction. That's

13
00:01:50,720 --> 00:01:54,800
may well, that's probably one of the technical lead or put in rather than the business sponsor.

14
00:01:54,800 --> 00:01:59,279
But you'd say, as we move from prototype to the full v1, that would be the next thing that we

15
00:01:59,279 --> 00:02:03,360
would do. So I put that in the comments stupidly. Let me cut that. I meant to put it in the

16
00:02:03,360 --> 00:02:09,199
description, put it in there. That's what I meant to do. Save that. There we go. Very good. That is

17
00:02:09,360 --> 00:02:17,279
our first ticket added. Presumably, yes, we are PL4. Okay. Now I'm going over here to PL5,

18
00:02:17,279 --> 00:02:29,919
add AI chat, but still just mutual NDA. We're going to say, now change the user, the UX user

19
00:02:29,919 --> 00:02:41,119
input. Let's write it in business speak. Now change the way the platform, the product

20
00:02:43,600 --> 00:02:57,360
interacts with a user. Instead of a series of questions, this should be a free form chat

21
00:02:58,000 --> 00:03:11,440
with an AI. The AI asks about the document, asks questions related to the fields

22
00:03:12,479 --> 00:03:17,759
and populates the document based on the responses.

23
00:03:21,360 --> 00:03:24,960
And I think that's it. I'm not going to mention Cerebras. I'm not going to mention

24
00:03:25,279 --> 00:03:29,440
structured outputs or anything else. I can think in my mind, there's different ways to interpret

25
00:03:29,440 --> 00:03:35,360
this. Like, is it able to change the text outside the key fields? I'm not sure. I think we're just

26
00:03:35,360 --> 00:03:40,160
going to let it interpret it as it wants. Maybe ask us some questions. That seems like a cool way

27
00:03:40,160 --> 00:03:44,080
to do it. Yet again, I put that in the comment instead of the description. What's wrong with me?

28
00:03:44,080 --> 00:03:52,240
There we go. I'm too excited. Save that. Okay. Let's keep going. Okay. Now it's on to PL6.

29
00:03:52,240 --> 00:03:58,240
Up it comes. Let's click in description, paste in what I just wrote. Now expand the functionality

30
00:03:58,240 --> 00:04:02,800
so it supports all legal document types for which we have templates. Engage with the user

31
00:04:02,800 --> 00:04:08,080
if they want an unsupported document. Explain we can't generate that, but offer a closest

32
00:04:08,080 --> 00:04:17,760
document that we can generate. Save that. There we go. Okay. And then I just want to be clear

33
00:04:17,839 --> 00:04:24,160
about the users. Let's just see. Hang on. For upgrade the frontend backend,

34
00:04:27,119 --> 00:04:36,160
only have a fake login screen for now. No authentication.

35
00:04:38,640 --> 00:04:46,640
Just bring the user into the platform. So that's clear. I don't want to add on user authentication

36
00:04:46,640 --> 00:04:54,480
up front, but at the end of it, I pressed save by mistake. We'll add in one more ticket in here.

37
00:04:54,480 --> 00:05:02,559
What needs to be done? Support multiple users. That's going to be our final ticket, PL7.

38
00:05:03,440 --> 00:05:07,920
Let's write that. Okay. So going into support multiple users, go to the description,

39
00:05:07,920 --> 00:05:12,799
and I'm going to paste in there. Add a proper sign in and sign up screen that lets the user

40
00:05:12,799 --> 00:05:17,200
register and come back into the platform. Store previously generated documents. Allow the user

41
00:05:17,200 --> 00:05:21,679
to look back at prior documents that they've created. The database can be temporarily reset,

42
00:05:22,399 --> 00:05:27,679
can be temporary, and be reset every time the server restarts. That's fine.

43
00:05:29,760 --> 00:05:37,679
Also add polish to all the screens so that they look like a professional

44
00:05:38,559 --> 00:05:50,559
SaaS application. That seems like a great thing to do. And also add a disclaimer that the documents

45
00:05:51,279 --> 00:05:56,559
should be considered draft and are subject to legal review.

46
00:05:57,279 --> 00:06:08,160
And let's change this to support multiple users and other final polish. There we go. Okay. Got

47
00:06:08,160 --> 00:06:18,640
there in the end. This is our Jira board now. We've got our four tickets, PL4, 5, 6, and 7.

48
00:06:19,200 --> 00:06:22,959
With the functionality you want to build, imagine it's been your engineering lead,

49
00:06:22,959 --> 00:06:27,519
your product people, your business sponsors, maybe even your clients that have come in and

50
00:06:27,519 --> 00:06:31,600
added these Jira tickets. Typically, this would now go off to the engineering team.

51
00:06:31,600 --> 00:06:35,920
These will be assigned off to different people. But what we're going to do is we're going to

52
00:06:35,920 --> 00:06:42,239
assign it, of course, to our friend, Claude Code. So here I am in the Jira board.

53
00:06:42,559 --> 00:06:47,679
And I'm going to type Claude. And the first thing we want to make sure is see what we see if I do

54
00:06:47,679 --> 00:06:54,959
slash context. We're hoping to see that there is a new skill. So rebrass inference, a project skill,

55
00:06:54,959 --> 00:07:00,959
isn't that cool? We could see that we've got our plugins and we know that we've got a project

56
00:07:00,959 --> 00:07:05,519
that's going to be using this plugin. So let's go ahead and create that. And we're going to

57
00:07:06,320 --> 00:07:12,399
inference, a project skill, isn't that cool? We could see that we've got our plugins. And we know,

58
00:07:12,399 --> 00:07:19,839
of course, that we have our existing Atlassian and GitHub MCP servers now. And you can see that

59
00:07:19,839 --> 00:07:27,600
we've used up a fair amount of context with the MCP tools that we've got. But we are primed for

60
00:07:27,600 --> 00:07:31,920
our project. Is there anything we have to do first? Yes, there is. I know you're thinking,

61
00:07:31,920 --> 00:07:36,079
why is that always something we have to do first? This one is an obvious one. We have to

62
00:07:36,079 --> 00:07:42,399
do that authentication again, because of Atlassian is funny. Come on in reauthenticate.

63
00:07:42,399 --> 00:07:49,679
Here we go. Approve. I tell you, if I don't do this, it wouldn't work. Accept, accept. Okay,

64
00:07:49,679 --> 00:07:56,000
we're ready. We're authenticated. So right away, I come back. It's time for us to do this.