Requirements

Requirements capture what success looks like for a change. Instead of you manually writing a checklist, the agent extracts requirements from your request and tracks each one through planning, implementation, and testing.

What it looks like

How requirements work

1. You describe your intent — “Redesign the homepage hero and add a pricing table” in the chat.
2. The agent extracts requirements — concrete, testable criteria like “Hero headline uses serif font” or “Pricing table has three tiers.”
3. Tasks map to requirements — each task in the plan is linked to the requirement it satisfies.
4. Tests verify requirements — test results tag back to their requirement, so you can see at a glance which criteria passed and which need work.

You don’t need to write requirements yourself — the agent infers them from your description. But you can always refine, add, or remove requirements through the chat.

Requirements and testing

Each requirement can have linked tests that verify it automatically. The requirements panel shows test status inline:

• ✓ Passed — the linked test confirms this requirement is met.
• ✗ Failed — the test found an issue; the agent will attempt to fix it automatically.
• ○ Pending — the test hasn’t run yet.

This closes the loop between what you asked for and what was actually delivered.

Requirements and task planning

Requirements feed directly into the task planning system. When the agent creates its plan, each task references which requirement it addresses. This gives you traceability from intent → requirement → task → code → test.