Skip to main content

​
Quickstart guide

This guide will walk you through creating your first project and generating AI-powered tickets on your Kanban board.

​
Sign up for an account

1

Navigate to the signup page

Go to the Toots application and click “Sign up” (or navigate directly to /signup)
2

Create your account

Enter your email address and create a password. Toots uses better-auth for secure authentication.
// Authentication is powered by better-auth with email/password
// All sessions are securely stored in PostgreSQL
3

Sign in

After creating your account, sign in with your credentials to access the dashboard

​
Describe your project idea

Once signed in, you’ll see the home screen where you can describe your project.
1

Enter your project idea

On the home page, you’ll see a text area prompting you to “Describe your project idea”. Enter a clear description of what you want to build.
The first line (up to 80 characters) becomes your project name, and the full description is stored for context.
Example ideas to try:
  • “A mobile app for team standups with async video notes and daily digests”
  • “API integration with auth, retries, and webhooks”
  • “Onboarding flow: signup, email verify, first steps”
2

Submit your idea

Click the send button or press Enter. Toots will create a new project and navigate you to the project workspace.
// Behind the scenes, Toots:
// 1. Creates a Project record in PostgreSQL
// 2. Stores your description for AI context
// 3. Generates a unique project ID
const project = await rpc.projects.create({ name, description })

​
Chat with AI to refine scope

Once your project is created, you’ll enter the project workspace with a chat interface.
1

AI asks clarifying questions

The AI assistant (powered by Google Gemini) will ask clarifying questions about your project to better understand:
  • Key features and functionality
  • User types and personas
  • Technical requirements and constraints
  • Priority and scope
2

Answer the questions

Provide answers in the chat interface. The more context you provide, the better the AI can generate relevant tickets.
You can be conversational — the AI understands natural language and can handle back-and-forth discussion.
3

Request ticket generation

Once you’ve provided enough context, ask the AI to generate tickets. For example:
  • “Generate tickets for this project”
  • “Create a breakdown of tasks”
  • “I’m ready for the ticket generation”

​
Generate AI-powered tickets

The AI will analyze your conversation and generate structured tickets.
1

AI generates tickets

Based on your project description and chat history, the AI creates tickets with:
  • Type — Story, Task, Epic, Bug, or Technical Debt
  • Priority — High, Medium, or Low
  • Title — Clear, actionable description
  • Description — Detailed context and implementation notes
  • Acceptance criteria — Specific success conditions
  • Estimated effort — Time estimate (e.g., “2-3 days”, “1 week”)
  • Dependencies — Related tickets that must be completed first
  • Labels — Categorization tags
// Example ticket structure in the database:
{
  id: "clx123abc",
  title: "Implement user authentication",
  type: "Story",
  priority: "High",
  description: "Add email/password auth with session management",
  acceptanceCriteria: ["Users can sign up", "Users can log in", "Sessions persist"],
  estimatedEffort: "3-4 days",
  dependencies: ["Database setup"],
  labels: ["auth", "backend"],
  status: "todo"
}
2

Review generated tickets

All tickets appear on the Kanban board in the “To Do” column. Review them to ensure they match your expectations.
3

Request modifications

If you want changes, use the chat to request updates:
  • “Add a ticket for unit tests”
  • “Increase priority of the auth ticket”
  • “Break down the API integration into smaller tasks”
The AI will update or add tickets accordingly.

​
Manage tickets on the Kanban board

Your project workspace includes a drag-and-drop Kanban board for ticket management.
1

View your tickets

The Kanban board has three columns:
  • To Do — New and unstarted tickets
  • In Progress — Active work
  • Done — Completed tickets
All newly generated tickets start in “To Do”.
2

Drag and drop tickets

Click and drag any ticket to move it between columns. Status updates are automatically saved to the database.
// Powered by dnd-kit for smooth drag-and-drop
// Status updates are persisted via oRPC to PostgreSQL
3

View ticket details

Click any ticket to open a slide-out detail sheet showing:
  • Full description
  • Acceptance criteria
  • Estimated effort
  • Dependencies
  • Labels
4

Edit or delete tickets

From the detail sheet, you can:
  • Edit any field inline
  • Delete the ticket with confirmation
  • View creation and update timestamps

​
Continue refining your project

1

Use the project chat

The chat panel is collapsible and available throughout your project. Use it to:
  • Request new tickets
  • Ask questions about implementation
  • Refine scope and priorities
2

Create multiple projects

Return to the home page (click “Home” in the breadcrumb) to create additional projects. Your project list appears in the sidebar, grouped by month.
3

Export tickets (coming soon)

Future versions will support one-click export to Jira and Linear, or formatted output for coding agents like Cursor.

​
Next steps

Self-hosting guide

Install Toots on your own infrastructure

Features

Explore all AI-powered features and capabilities

Product discovery

Learn about upcoming evidence-based product discovery features

GitHub repository

View source code and contribute

​
Troubleshooting

Make sure you’ve provided enough context in the chat. The AI needs to understand:
  • What you’re building
  • Who it’s for
  • Key features and requirements
Try explicitly asking: “Please generate tickets for this project”
Check that:
  • The AI has finished generating (watch for completion message)
  • You’re viewing the correct project
  • Refresh the page if needed
Ensure you’re clicking and holding on the ticket card itself (not buttons or links inside it). The drag functionality is powered by dnd-kit.
Click on the ticket card to open the detail sheet. All fields should be editable inline. If not, check that you’re signed in and own the project.

Build docs developers (and LLMs) love

Get started for freeTalk to us