Production-Ready Claude Code: Tech Spec → GitHub Epics/Issues → Execute Issue by Issue (ex-Shopify eng)

Exact instruction

Write a detailed tech spec in Claude Desktop (Opus 4.8) — not Claude Code — covering: what you're building, edge cases, data flow, UI/UX.
Connect Claude Code to GitHub. Ask it to convert the spec into an Epic with Issues and Sub-Issues.
Execute issue by issue. Review each before moving to the next. Catch problems before they compound.
Comment 'Claude Code' on the original post for the one-page setup guide.

Suggested prompt

Before writing any code: let's write a detailed technical spec for this feature. Cover: what we're building, edge cases, data flow, UI/UX decisions, and success criteria. Write it as a full markdown doc. Once approved, we'll convert it to GitHub issues.

Adopt?

Yes: This is the most rigorous production workflow pattern in this batch. The key insight — write specs in Claude Desktop first, THEN have Claude Code convert to GitHub issues — separates planning from execution and creates a reviewable audit trail. Directly applicable to serious projects.

Find the resource

Comment 'Claude Code' on the original post (@nelsontalksmoney) for the one-page setup guide on breaking specs into structured GitHub issues.

show original caption

How I get Claude Code to write production-ready code, not just demos. Plan first, break it into GitHub Epics and Issues, execute in pieces. Comment "Claude Code" and I'll DM you the setup. #claudecode