AI Pipeline — approve a repo-grounded spec before a coding agent writes code

I run a small software shop and built this because the plan I approved never stayed binding once the agent started writing.

A plain-language task goes in. A planning agent clones the project's real repositories and drafts a specification from them. A human approves it. Only then does a coding agent — OpenAI API, Anthropic API, Claude Code CLI or Copilot CLI, on your own key — build exactly that and open a pull request.

The part I think is actually new: a Customer seat. Someone who does not read code can file tasks, drive planning and approve, but never touches settings, repositories, agents or skills.

What it does not do yet: it does not verify the finished PR against the approved spec automatically. That is a human comparing the two, and it is the next thing to build.

Free tier runs real tasks. Five-minute walkthrough: [walkthrough URL] · Product page: producthunt.com/products/ai-pipeline

I'd value one thing more than sign-ups: would you let a non-technical person approve the spec, and what would you need to see before you trusted the PR?