Sweet! CLI

AI-Powered Development Workflows

Sweet! CLI workflows are prompt-driven: you describe the goal, Sweet! CLI plans the work (todos) and executes it using its tools.

Workflow Overview

In this repo, workflows are not implemented as separate --review/--deploy flags. Instead, you use clear prompts and (optionally) autopilot.

Common Patterns

1) One-shot task

sweet "Fix the failing test and explain the root cause"

2) Interactive session

sweet
You: Audit our docs and remove anything not implemented
Sweet! CLI: Creates todos, edits files, verifies outputs

3) Autopilot / timeboxed work

sweet --work-for 45m "Refactor the billing page CSS for consistency"

Inside interactive mode you can also use /workfor 45m, /workoff, and /workstatus.

Daily Development Workflow

A typical day using Sweet! CLI might look like this:

Morning: Planning & Setup

# Start Sweet! CLI interactive mode
sweet

# Review yesterday's work
You: Summarize what we accomplished yesterday
Sweet! CLI: Shows todos, commits, and remaining tasks

# Plan today's work
You: Create a todo list for implementing user authentication
Sweet! CLI: Breaks down authentication into actionable steps

Midday: Active Development

# Work on a specific task
You: Implement the login endpoint
Sweet! CLI: Creates route, validation, database queries, tests

# Get unstuck
You: I'm getting a 500 error when submitting the form
Sweet! CLI: Analyzes logs, suggests fix, implements solution

# Review code
You: Review the changes I just made
Sweet! CLI: Provides feedback on code quality, security, performance

Afternoon: Testing & Deployment

# Generate tests
You: Write integration tests for the login flow
Sweet! CLI: Creates comprehensive test suite

# Prepare for deployment
You: Create a deployment checklist
Sweet! CLI: Generates migration scripts, environment variables, monitoring setup

# End of day wrap-up
You: Create a summary of today's work
Sweet! CLI: Generates commit messages, updates documentation, plans tomorrow's work

Team Collaboration Workflows

Sweet! CLI enhances team productivity with these collaborative patterns:

Code Review Standardization

Ensure consistent code reviews across the team:

# Team configuration file
{
  "code_review": {
    "required_checks": ["security", "performance", "accessibility"],
    "auto_approve_threshold": 90,
    "reviewers": ["@senior-engineers"]
  }
}

Knowledge Sharing

Automatically document team decisions and patterns:

sweet "Document our API design decisions from today's meeting"
sweet --knowledge-base --update

Onboarding Automation

Help new team members get up to speed:

sweet "Create an onboarding guide for new backend developers"
sweet --onboarding --role "backend-engineer"

Automation

You can integrate Sweet! CLI into scripts/CI by invoking the CLI with a prompt (and ensuring the runner has access to the repo and credentials).

Best Practices

  • Start small - Begin with one workflow (like code reviews) before expanding
  • Set clear goals - Define what you want to automate before starting
  • Review AI suggestions - Always validate AI-generated code before deploying
  • Iterate - Refine workflows based on what works for your team
  • Measure impact - Track time saved, bugs caught, and quality improvements

Next Steps

Now that you understand workflows: