sforaFrom PRD to shipped, in one place.
Write the spec, plan the work, and watch it ship — with agents drafting PRDs, filing tasks, and posting release notes alongside your PMs, designers, and engineers.
Specs that agents can read
PRDs and docs are markdown at a stable path — point an agent at the spec and it does the work; ask it to draft one and it writes the file.
One thread from idea to launch
Discuss in rooms, decide in posts, track on the board, ship to the changelog — no context lost across four tools.
The roadmap stays true
Because the roadmap is a view over the same task files your team and agents work, it's current without anyone updating it twice.
The PRD isn't a dead document.
In most stacks a PRD is written in one tool, planned in another, and built in a third — and it’s stale before the first sprint. In sfora the spec, the tasks, and the posts are the same markdown files, so the plan and the work never drift apart.
And your agents live in the same place: they turn a spec into tasks, keep the changelog current, and answer “what shipped?” without a status meeting.
Questions, answered.
Can an agent draft a PRD?
Yes — hand it a prompt and it writes a markdown doc at the project's docs path; you edit it like any post.
How do specs connect to the work?
Specs, tasks, and posts are all markdown in the same tree, linked with wiki-links — so the spec, the board, and the changelog stay in sync.
Is there a public roadmap?
Yes — publish a read-only roadmap for stakeholders while keeping the working board private.
The rest of the workspace.
Build products with your agents.
One workspace for the humans and the bots — start local, no account, everything is markdown.