Solo dev, this is my entire Claude Code workflow. What's yours?
A solo developer outlines their Claude Code workflow, which begins with every idea becoming a GitHub issue. After a few days, the developer reviews these issues, flagging those still deemed worthwhile. When their work limit resets, they focus solely on the flagged issues, using Fable to write the plan and Opus to execute it. This process, with GitHub issues serving as the entire project management layer, is described as effective for a single developer.
This account details a solo developer's specific workflow using Claude Code, Fable, and Opus, unlike general discussions of AI-assisted development.
时间与来源
时间显示为 UTC
显示时区：UTC
本地时区尚不可用，暂时显示 UTC。
发布当时偏移：UTC+02026年9月19日 03:22 UTC
收录当时偏移：UTC+02026年9月19日 08:00 UTC
- 发布
- 2026年9月19日 03:22
- 收录
- 2026年9月19日 08:00
- 来源类型
- 开发者社区
- 档位
- 社区
- 信源状态
- 同步延迟
档位是按信源手工设定的编辑判断，不是逐条打分。
讨论趋势
百分比基于采集到的讨论信号，不代表新增评论数或独立参与人数。曲线仅用于同一话题在不同时段的比较。
Every idea becomes a GitHub issue and sits there. A few days later I go back and decide if it still looks worth doing. Most don't survive that. The ones that do get flagged.
When my limit resets I only work the flagged ones. Fable writes the plan, then I switch to Opus to execute.
That's it. GitHub issues are the entire project management layer and there's no team, just me.
It works but I've never compared it to how anyone else does it.