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.
Time & source
Times shown in UTC
Display time zone: UTC
Local time zone unavailable; showing UTC.
PublishedOffset at this time: UTC+0Sep 19, 2026, 03:22 UTC
IngestedOffset at this time: UTC+0Sep 19, 2026, 08:00 UTC
- Published
- Sep 19, 2026, 03:22
- Ingested
- Sep 19, 2026, 08:00
- Source type
- Dev community
- Tier
- Community
- Source status
- Healthy
Tier is a per-source editorial setting, not a per-item score.
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.