Skip to main content
Twill can handle complex, multi-step projects. It researches your codebase, asks clarifying questions, and creates a detailed plan before writing any code. You could ask it to build an entire feature from scratch.But we’ve found that thinking in terms of delegation works better. Start with smaller, well-scoped tasks—the kind you’d hand off to a teammate. As you build trust and see how Twill works, you’ll naturally expand what you delegate.
Mention @twill wherever you work—Slack, GitHub, Linear, or the web app—and describe what you need. Here’s what teams typically ask for.

Bug Fixes

How it works: Describe the bug or paste an error message. Twill reproduces the issue, identifies the root cause, and opens a PR with the fix. Works best when: You include reproduction steps, error messages, or stack traces. The more context, the faster the fix.
ROI: Bugs fixed in hours, not days | Developers stay focused on feature work

Small Features

How it works: Describe what you want—add a new API endpoint, update a form, add a button. Twill asks clarifying questions if needed, then delivers a PR. Works best when: The scope is clear and well-defined. One feature per request.
ROI: 2-4 hours saved per feature | Ship faster without context switching

Refactoring

How it works: Ask Twill to clean up code, extract components, rename across the codebase, or migrate to a new pattern. Twill handles the tedious work while preserving behavior. Works best when: You’re specific about what to change and what to preserve.
ROI: Refactors that would take days done in hours | Less risk of regressions

Codebase Questions

How it works: Ask Twill about your codebase. “How does authentication work?” or “Where is the payment processing logic?” Twill explores the code and explains it clearly. Works best when: You’re onboarding, exploring unfamiliar code, or need a quick answer without interrupting teammates.
ROI: Faster onboarding | Reduces “hey, quick question” interruptions

Test Coverage

How it works: Ask Twill to add tests for a file, function, or feature. Twill analyzes the code, identifies edge cases, and writes tests that actually catch bugs. Works best when: You point to specific code that needs coverage.
ROI: Better coverage without the tedium | Edge cases humans skip

Documentation

How it works: Ask Twill to document a function, update a README, or explain how a system works. Twill reads the code and writes accurate, clear documentation. Works best when: The code is reasonably well-structured. Twill can explain messy code too, but the docs will reflect that.
ROI: Docs that stay accurate | No more outdated READMEs

PR Iteration

How it works: When you request changes on a Twill PR, the agent picks up your feedback and pushes updates. No need to re-explain context—Twill remembers the conversation. Works best when: You give specific, actionable feedback. “Make this function pure” or “Add error handling for null inputs.”
ROI: Faster iteration cycles | PRs that match your standards