How are you guys actually using Fable 5 for complex app ideas?
这条记录涉及编程工具或代码能力更新，适合开发者评估工作流变化和可复用价值。
一位用户尝试使用 Fable 5 来将酝酿已久的应用想法转化为详细的实施计划。他将 Markdown 格式的构思和产品想法输入 Fable 5，并要求其挑战想法、提出澄清问题并制定计划。尽管 Fable 5 提出了一些有价值的问题，但最终的计划却令人失望。…
finally worked up to start building an app idea I’ve been sitting on for a while.
I had all my brainstorming and product ideas written in Markdown files, so I gave them to Fable 5 and asked it to challenge the idea, ask clarifying questions, and turn everything into a detailed implementation plan.(cause again thats what i learned fable is good at, making plans for other subagents to implement)
It did ask some genuinely good questions, but the final plan felt really underwhelming. It watered down the MVP, removed some of the features that made the app interesting, and kept pushing toward simpler, safer implementations because the original features would supposedly take months of research.
My initial impression of Fable 5, based on how people talk about it online, was that this is exactly where it shines: taking ambitious, complicated ideas, deeply reasoning through them, and finding a realistic way to make them happen.
Instead, I ended up with a very conservative implementation plan that feels like a much less interesting version of the original app.
So how are you guys actually using Fable 5?
Do you use it mainly for brainstorming, research, architecture, implementation planning, coding, or creating reusable skills and workflows? Is there a better way to prompt it so that it explores how to achieve the ambitious version before immediately cutting scope and avoiding risk?
I’m not against reducing scope for an MVP, but I want it to help me find the smartest achievable version of the idea, not automatically turn it into the safest and most generic version.