Quickstart

Create a project

From your dashboard, create a project and give it the name your team already uses for this product. A project holds plans, and later it holds the connection to your issue tracker.

Write the business requirement

Open a new plan and describe what the business needs, in plain English. No format, no template. A paragraph is enough:

Customers keep emailing us to ask for last month's numbers as a PDF.
We want them to save a report once and have it arrive on a schedule.

Write what the business wants, not the implementation. Deciding how is the agent's job, and yours to correct.

Answer the agent's questions

The agent researches your Context first, then asks you what it still needs. Expect two or three questions, and expect them to be the awkward ones: what "monthly" means in someone else's time zone, who keeps receiving a report when the person who set it up leaves, what a schedule does when the report behind it changes.

This step is what makes the Specs specific. Skipping it produces a plan that reads well and cannot be built.

Review the Specs

You now have a plan: a tree of Specs, each with acceptance criteria, an effort and a readiness of Rough, Shaping or Ready.

Read the acceptance criteria first, not the titles. That is where a plan is right or wrong. Ask for changes in the same conversation ("SPEC-3 should cover weekly as well as monthly") and the agent rewrites it in place.

Push to your issue tracker

Connect Linear, Jira or Radial, then push. The plan lands as issues and sub-issues with its hierarchy and its "needs first" dependencies intact, and every Spec keeps its acceptance criteria in the issue body.