Build an invoicing demo from a Markdown brief with 13 Claude roles
At a glance
A project manager used a Python pipeline of 13 specialized Claude instances to turn a Markdown brief into a deployed invoicing demo. This workflow is listed under agent-orchestration, app-development, software-testing.
Nicolas supplied an IDEA.md project brief to a Python orchestrator that ran Claude roles in sequence for specification, design, implementation, review, database checks, security and Playwright testing. Failed checks triggered repair cycles; after two stalled rounds, a separate role investigated the cause. He tested the pipeline on an invoicing app for French freelancers.
How it went
He published a live demo and public repository with authentication, client records, invoice numbering, PDF export, payment tracking and six interface languages.
Worth knowing
The author explicitly scoped this as a demo: it lacked signup, password resets, email sending and recurring invoices. He was still improving the pipeline between runs.
Save ideas in this browser. Upvotes count across the board.
An indie hacker packaged an agency's eight repeated workflows (briefs, client approval with revision counters, quotes with margin checks, content calendars, post-mortems) as free MIT Claude skills.
Anthropic’s Building Effective Agents appendix highlights two proven patterns—support agents that pull data and take actions like refunds, and coding agents that iterate against tests—with clear success metrics and human review.
Indie Hackers founder Sean Prentice used Claude Code to build an orchestrator + marketing director + specialist agents (content/ads/research) for his SaaS; outputs land in Slack and nothing posts or spends without his explicit say (~$10/mo self-use).
Indie Hackers guide: Jotform intake → Zapier → Claude/ChatGPT triages priority and drafts a reply → a control form lets you edit → a second Zap finishes CRM/notify actions—only high-priority items pause for review.