It begins with a feature, described in plain English.
You bring an idea, framed however it's clearest in your head. Weft asks the questions a thoughtful product partner would ask: who is this for, why now, what would "done" actually look like? By the end, the idea is sharper than when you walked in, and you both know exactly what you're about to build.
Four Builders shape the idea before code is written.
Session 1 hands the idea to The Strategist, The Planner, The Architect, and The Designer in sequence. The strategic case becomes a requirements doc, becomes a data layer, becomes a clickable mockup. Session 1 ends with a design you can open in your browser, approved by you, before a single line of code exists.
Five Builders build the feature and ship it.
Session 2 takes the approved spec through The Engineer, The Tester, The Auditor, The Deployer, and The Chronicler. The feature gets built, the tests get written, security gets reviewed, the change goes live, and the project context gets updated to reflect what just shipped. Nothing moves forward without your sign-off.
Stop anytime. Pick up exactly where you left off.
Most AI coding tools forget who you are between sessions and trap you mid-workflow. Weft does neither. Track progress Builder by Builder in the side panel, Save & Pause at any stage, and Weft holds your place. Come back tomorrow or next week and resume from the exact step you stopped at, with every stage saved as a file you can inspect.
Every shipped feature makes the next one easier.
When a feature reaches production, The Chronicler updates the project's context with what was built and why. The next time you start something new, Weft already knows your stack, your conventions, your past trade-offs. Over time, it starts to feel like Weft has been working at your company for a while.