Plan syntax

Tessl Plan format reference

Plans

Plans are markdown documents with a specific structure. Agents are encouraged to make and follow plans. This has the advantages of keeping the agent on track, creating reusable workflows, and providing a record of what happened.

Plan files are typically saved in ./plans and have a .plan.md extension.

Plan format

• Title: A markdown heading (#) describing the overall objective

• Description: Optional context about what the plan aims to achieve

• Task Lists: Markdown checkboxes representing tasks (- [ ] for pending, - [x] for completed)

• Feedback: The results of each task are saved as quote blocks (>) below their definition

Plan Structure

# Implement Authentication System

Add user authentication to the application with secure login and session management.

- [ ] Design authentication flow
  - [ ] Create flow diagrams
  - [ ] Define API endpoints
- [ ] Implement backend authentication
  - [ ] Set up user model
  - [ ] Create authentication endpoints
  - [ ] Add JWT token generation
- [ ] Review security implementation 
- [ ] Add frontend login UI
  - [ ] Create login component
  - [ ] Integrate with backend API
- [ ] Write tests
  - [ ] Unit tests for auth logic
  - [ ] Integration tests for API
- [ ] Deploy to staging