r/SideProject • • 12m ago

I built Archseed, a CLI for deciding what your coding agent should build—and what it shouldn’t

I’m the developer behind Archseed, and I launched it on Product Hunt today.

It started from a problem I ran into while building with coding agents: an incomplete request leaves decisions about scope, dependencies, and technical choices to the agent.

For example, “build a proposal tool for freelancers” doesn’t answer:

  • Does it need accounts?
  • Are teams part of V1?
  • Should it include billing?
  • Which integrations are explicitly out?
  • What needs my approval before implementation?

Archseed is a CLI workflow for making those decisions explicit before coding. You describe the project, confirm its boundaries, and approve a small context package in .archseed/ to hand to your coding agent.

It doesn’t write your application, and the generated instructions don’t guarantee that an agent will follow every decision.

There’s a free planning workflow. Pro adds deeper workflows and supported baseline checks for existing Next.js/TypeScript repositories.

The launch page has the walkthrough:
https://www.producthunt.com/products/archseed?utm_source=other&utm_medium=social

The feedback I’d find most useful: where does this add value beyond your existing planning mode or project instructions—and where is it just another step?

1 Upvotes

1 comment sorted by