New project assignment
You've received a new email in Outlook from your manager at Tailwind Traders.
Read the message to understand why the team is writing a specification before building the agent.
Hi there,
We're finally green-lit to build Tailwind Assist, an AI agent to help customers on our support site. I know the team is eager to open a chat playground and start writing prompts, but last time that led to endless rework, everyone imagined a different agent, and no one could agree on when it was good enough to launch.
This time we do it properly. Before a single line of code, we write an agent specification: the blueprint, or job description, for the agent. It captures what the agent does, how it behaves, and how we'll know it works.
How we'll work:
- I've created a board in Azure DevOps with one work item per specification section.
- You'll capture the spec in agent-spec.md in VS Code, the same way we track any product requirement.
- Each section is grounded in real input, emails from colleagues, support dashboards, and reports on our current customer support data.
With the spec in hand, we can make design choices, like which model to use, with clear targets to aim for. Open the Azure DevOps board to get started.
Thanks,
Priya