building - https://xitter.cf/t.co/0Ct8EBoKAa - https://xitter.cf/t.co/3vZjp67mdE - https://xitter.cf/t.co/I0kEbEpSX3
California, USA
Joined May 2009
- Tweets2K
- Following864
- Followers10K
- Likes388
Pinned Tweet
1/ Today we're launching Plansmith.
The planning agent for the business side of software.
It takes your business context and what needs to be done, and helps you bring your expertise to create a build-ready plan and prototype you hand off to the dev team.
Will be interesting to see where we end up as agents use (and abuse) every website from booking restaurants, forums, forms, literally everything
Not saying it is a bad thing, but some of the underlying assumptions are changing so does UI/agent surface
business: that's not what I asked for
engineering: that's not what the ticket says
An old classic.
If it was defined properly from the beginning, the developer could have built it fast and the business would be happy.
With plansmith.co this will never happen again
Contrary to popular belief, it's not about building fast.
That's the narrative you often hear from people showing off products no one uses. At the end of the day it's about building right.
Plansmith.co runs /readiness-review and gives you a full report.
Nico Acosta retweeted
Grabbit is live in the Claude Connectors Directory.
Hosted screenshots for agents — grab any URL as an image, no local Chromium.
claude.ai/directory/grabbit
She gets a ticket, builds it, and hears back from the business: "Hey, that's not what I needed." Then she's like, "Well, that's not what the ticket said."
Show a clickable prototype, in your app's own look, first. Plansmith.co creates one in minutes.
This is great. Goes back to the idea of "Own the outcome"
We instituted an official AI Writing Policy at @Clay.
Massive thanks to @sophiebits on our engineering team who wrote this.
Originally this was just for eng, but other teams found it so helpful we expanded it company-wide.
Here are the four guiding principles:
1. You must stand behind every idea and sentence
It is your responsibility to make sure that the entire document is representative of your own thoughts before you share it.
2. Writing is thinking
Spending time on the writing process teaches you more about your topic. If you circumvent this process, you will walk away with a poorer understanding of the subject matter.
3. More time should be spent writing a document than consuming it
If you generate a document from a short prompt then ask your readers to go through the longer output, you are disrespecting their time. They can talk to ChatGPT themselves if they want to.
4. Longer is not better
AI makes it easy to generate long docs, and it loves padding them with sentences that say nothing. If you're producing docs from a short prompt, consider just sharing the prompt.
You can read (and borrow) the full policy below. Hopefully we all communicate a bit more clearly now :)
How to break a big project down before anyone builds it:
One epic, one spec per buildable thing, and 15 open questions flagged before anyone has a meeting about them.
Takes skill to break things down properly, plansmith.co does it for you.
How to get specs the dev team doesn't send back:
If you don't know the intent, you can build fast and build the wrong thing.
In plansmith.co you do the research, bring the customer moments into context, then ask for the specs. Six specs and a prototype out.
All GPT-6 Models Astra, Terra, and Luna are now available in Plansmith.
Lunas is my favorite (and platform default) for small and fast tasks.
Astra is a planning beast, helps you think about the strategy and the problem (and solution) space holistically
Every time you rebuild the context in Claude or ChatGPT, it's not a repeatable effort and it is not shareable with your team.
In plansmith.co you add context once. Decompose a big project into sub-plans and each one inherits everything above it.
Grok 4.7 is now available in plansmith.co
Found it super useful to power the adversarial spec and prototype reviews
Noticed agents writing way more comments in the code explaining decisions.
the code is in some sense a memory layer as well
Very nice of Anthropic and OpenAI to leave their differences aside and agree on releasing on the same day
Opus 5.5 is now available on plansmith.co
For planning, you’ll always want to use the most powerful models.
More meetings, more documents, more integrations: the business context gets harder to manage as a team.
When planning, this context matters.
In plansmith.co you manage in one place, three levels: company, project, this plan.
Planning is a team sport.
