Okay, this is us back in Jira again. Check this out. You can see that it moved the other ticket
to done. I didn't remember seeing it do that. I didn't ask it to, I don't think, I don't remember,
but it did. Okay, so now we're going to create some more tickets. I just started writing this
one. Let's have the first of them being from prototype, build foundation of v1 product.
Let's start with that as a ticket. And then the next ticket is going to be add AI chat,
but still just mutual NDA. And then the next step is expand to all legal, all supported
legal document types. There we go. That's our three sets. This is coming in from our business.
Let's have a look at this one. First of all, maybe this one is a bit more of a technical one,
but this one is upgrade the prototype so that it is the proper technical foundation for the full
v1 project, including front end, back end, and temporary database
with scripts to start and stop, but without updating the functionality
yet. Let's say the features, the product features. Yes, that seems like a clear instruction. That's
may well, that's probably one of the technical lead or put in rather than the business sponsor.
But you'd say, as we move from prototype to the full v1, that would be the next thing that we
would do. So I put that in the comments stupidly. Let me cut that. I meant to put it in the
description, put it in there. That's what I meant to do. Save that. There we go. Very good. That is
our first ticket added. Presumably, yes, we are PL4. Okay. Now I'm going over here to PL5,
add AI chat, but still just mutual NDA. We're going to say, now change the user, the UX user
input. Let's write it in business speak. Now change the way the platform, the product
interacts with a user. Instead of a series of questions, this should be a free form chat
with an AI. The AI asks about the document, asks questions related to the fields
and populates the document based on the responses.
And I think that's it. I'm not going to mention Cerebras. I'm not going to mention
structured outputs or anything else. I can think in my mind, there's different ways to interpret
this. Like, is it able to change the text outside the key fields? I'm not sure. I think we're just
going to let it interpret it as it wants. Maybe ask us some questions. That seems like a cool way
to do it. Yet again, I put that in the comment instead of the description. What's wrong with me?
There we go. I'm too excited. Save that. Okay. Let's keep going. Okay. Now it's on to PL6.
Up it comes. Let's click in description, paste in what I just wrote. Now expand the functionality
so it supports all legal document types for which we have templates. Engage with the user
if they want an unsupported document. Explain we can't generate that, but offer a closest
document that we can generate. Save that. There we go. Okay. And then I just want to be clear
about the users. Let's just see. Hang on. For upgrade the frontend backend,
only have a fake login screen for now. No authentication.
Just bring the user into the platform. So that's clear. I don't want to add on user authentication
up front, but at the end of it, I pressed save by mistake. We'll add in one more ticket in here.
What needs to be done? Support multiple users. That's going to be our final ticket, PL7.
Let's write that. Okay. So going into support multiple users, go to the description,
and I'm going to paste in there. Add a proper sign in and sign up screen that lets the user
register and come back into the platform. Store previously generated documents. Allow the user
to look back at prior documents that they've created. The database can be temporarily reset,
can be temporary, and be reset every time the server restarts. That's fine.
Also add polish to all the screens so that they look like a professional
SaaS application. That seems like a great thing to do. And also add a disclaimer that the documents
should be considered draft and are subject to legal review.
And let's change this to support multiple users and other final polish. There we go. Okay. Got
there in the end. This is our Jira board now. We've got our four tickets, PL4, 5, 6, and 7.
With the functionality you want to build, imagine it's been your engineering lead,
your product people, your business sponsors, maybe even your clients that have come in and
added these Jira tickets. Typically, this would now go off to the engineering team.
These will be assigned off to different people. But what we're going to do is we're going to
assign it, of course, to our friend, Claude Code. So here I am in the Jira board.
And I'm going to type Claude. And the first thing we want to make sure is see what we see if I do
slash context. We're hoping to see that there is a new skill. So rebrass inference, a project skill,
isn't that cool? We could see that we've got our plugins and we know that we've got a project
that's going to be using this plugin. So let's go ahead and create that. And we're going to
inference, a project skill, isn't that cool? We could see that we've got our plugins. And we know,
of course, that we have our existing Atlassian and GitHub MCP servers now. And you can see that
we've used up a fair amount of context with the MCP tools that we've got. But we are primed for
our project. Is there anything we have to do first? Yes, there is. I know you're thinking,
why is that always something we have to do first? This one is an obvious one. We have to
do that authentication again, because of Atlassian is funny. Come on in reauthenticate.
Here we go. Approve. I tell you, if I don't do this, it wouldn't work. Accept, accept. Okay,
we're ready. We're authenticated. So right away, I come back. It's time for us to do this.