Four steps. The first two are you and Foundry agreeing on what the project is; the last two turn that into work.
Start a new project and write what you are building in plain language. Attach anything that already exists — a PDF spec, an RFC, a Markdown brief, meeting notes. Foundry reads them and researches the domain in the background.
"Replace our on-prem billing system with a multi-tenant service. 40k merchants, PCI scope, zero-downtime cutover from the PHP monolith."
The more constraints you state up front, the fewer Foundry has to ask about.
Foundry reads the description for gaps and asks about the ones that would change the plan — who the users are, what has to keep working, where the hard limits sit. It scores readiness as you answer and holds the pipeline until the brief is complete enough to be worth running.
You can commit early. The gate is a recommendation, not a lock.
Each phase reads the previous phase’s output: discovery, specification, architecture, database, plan, estimation, and the sprint breakdown. Phases a project does not need are skipped by rule. You can open any phase, read what it produced, and re-run it.
What each phase produces →Install the extension, sign in with your Mindaeon account, and the approved plan syncs into your workspace as tasks with their acceptance criteria and context attached. Your repos, branches, and review process stay exactly as they are.
Install the VS Code extension →