FlowState Agents
Creating an Agent
Workflow: Creating an Agent Task
Overview
This guide walks you through creating a task that will be executed by an AI agent. You'll learn how to properly configure a task, provide clear instructions, and set up the workflow for optimal agent performance.
Time Required: ~10 minutes Skill Level: Beginner
Prerequisites
Before creating an agent task, ensure you have:
- Access to the Agents App
- At least one codebase configured (see Getting Started)
- Understanding of what you want the agent to accomplish
- Clear, specific requirements for the task
Workflow Diagram
+------------------+ +------------------+ +------------------+
| Define Task |---->| Create Task |---->| Agent Picks Up |
| Requirements | | in App | | Task |
+------------------+ +------------------+ +------------------+
|
v
+------------------+ +------------------+ +------------------+
| Review Output |<----| Approval |<----| Agent Executes |
| & Iterate | | Created | | Work |
+------------------+ +------------------+ +------------------+
Steps
Step 1: Define Your Task Requirements
Before opening the app, clearly define what you want the agent to accomplish.
Good task descriptions include:
| Element | Description | Example |
|---|---|---|
| Objective | What should be accomplished | "Add input validation to the user registration form" |
| Context | Relevant background | "The form is in src/components/RegistrationForm.tsx" |
| Acceptance Criteria | How to know it's done | "All fields should validate on blur and show error messages" |
| Constraints | Any limitations | "Use Zod for validation, don't modify the API" |
Bad task descriptions:
- "Fix the code" (too vague)
- "Make it better" (no clear objective)
- "Add some tests" (not specific enough)
Step 2: Open the Task Creation Dialog
- Navigate to the Dashboard or Tasks page
- Click the New Task button
- The task creation dialog will appear

Step 3: Fill in Task Details
Complete the task creation form with clear, actionable information:
Title Field:
- Keep it concise but descriptive
- Use action verbs (Add, Fix, Update, Create, Implement)
- Include the component or area affected
Good: "Add email validation to RegistrationForm"
Bad: "Registration stuff"
Description Field: Write a detailed description that includes:
- Context: What is the current state?
- Objective: What should change?
- Details: Specific requirements or constraints
- Acceptance Criteria: How to verify completion
Example description:
## Context
The RegistrationForm component currently accepts any input without validation.
Users can submit empty forms or invalid email addresses.
## Objective
Add client-side validation to all form fields using Zod schemas.
## Requirements
- Email field: validate format using Zod email()
- Password field: minimum 8 characters, at least one number
- Username field: 3-20 characters, alphanumeric only
## Acceptance Criteria
- [ ] Validation errors appear on blur
- [ ] Submit button disabled when form invalid
- [ ] Error messages are user-friendly
- [ ] Existing tests still pass

Step 4: Submit the Task
- Review your task details for clarity
- Click Create to submit the task
- You'll be navigated to the task detail page
The task is now in the queue with status To Do.
Step 5: Monitor Task Progress
Once an agent picks up your task:
- Task status changes to In Progress
- Navigate to the task detail page to monitor
- Check the Activity or Logs tab for real-time updates

Step 6: Respond to Agent Queries
Agents may need clarification. If the agent has questions:
- Check the Conversation tab on the task detail page
- Read the agent's query carefully
- Provide a clear, specific response
- Click Send to submit your response
The task will be re-queued and the agent will continue with your input.

Step 7: Review the Output
When the agent completes the task:
- An approval request may be created (if configured)
- Navigate to Approvals or check the task detail
- Review the agent's work:
- Check the output description
- Review any code changes
- Verify acceptance criteria are met
Step 8: Take Approval Action
After reviewing, take one of these actions:
| Action | When to Use | Result |
|---|---|---|
| Approve | Work meets requirements | Workflow completes successfully |
| Reject | Work is fundamentally wrong | Task may need manual intervention |
| Request Revision | Minor changes needed | Agent will attempt to address feedback |
Include helpful comments with your decision:
Approve: "Good implementation. Code is clean and tests pass."
Request Revision: "Validation works but error messages need to be
more user-friendly. For example, 'Invalid email' should be
'Please enter a valid email address'."

Expected Results
After completing this workflow, you should see:
- A completed task with status Complete
- Approval status showing Approved (if applicable)
- Agent's work integrated or ready for integration
- Logs showing the execution history
Best Practices
Writing Effective Task Descriptions
- Be specific: Include file paths, function names, component names
- Provide context: Explain why the change is needed
- Set boundaries: Specify what NOT to change
- Include examples: Show expected input/output if relevant
Task Sizing
| Size | Description | Example |
|---|---|---|
| Small | Single file, focused change | "Fix typo in error message" |
| Medium | Multiple files, related changes | "Add form validation" |
| Large | Feature-level work | "Implement user settings page" |
For best results, break large tasks into smaller, focused tasks.
Monitoring Tips
- Check logs regularly: They show detailed execution steps
- Respond quickly: Pending queries block task progress
- Review thoroughly: Catch issues early in the approval step
Troubleshooting
Issue: Task stays in "To Do" indefinitely
Cause: No workers available to pick up the task.
Solution:
- Check the Workers page for active workers
- Verify workers are configured for your workspace
- Contact your administrator if no workers are available
Issue: Agent produces incorrect output
Cause: Task description may be unclear or missing context.
Solution:
- Request revision with specific feedback
- Provide additional context in your feedback
- Consider breaking the task into smaller pieces
- Add explicit acceptance criteria to future tasks
Issue: Agent keeps asking questions
Cause: Task scope may be too broad or ambiguous.
Solution:
- Answer questions with specific details
- Consider revising the original task description
- Break complex tasks into simpler sub-tasks
Related Workflows
- Getting Started - Initial setup guide
- Features - All available features
- Troubleshooting - Common issues and solutions
Summary
Creating effective agent tasks requires:
- Clear, specific task descriptions
- Proper context and constraints
- Measurable acceptance criteria
- Active monitoring and timely responses
- Thorough review of agent output
Following these practices leads to better agent performance and higher quality outputs.