Show HN: Primer – AI 에이전트를 사용하여 한 번에 하나의 마일스톤으로 소프트웨어 구축

Primer helps you build real software with AI agents one verified milestone at a time. The main work happens inside your AI coding agent. The primer CLI sets up the workspace, verifies prerequisites, and powers the milestone workflow under the hood. Instead of handing an agent a huge vague task, Primer gives you a milestone contract, a verification step, and a clear next action. Primer is a good fit if you want to: - start from a real workspace instead of a blank prompt - keep the agent focused on the current step - verify progress before moving on - learn the system as you build it Current recipes: cli-tool : build a practical task tracker CLI in Pythoninterpreter-mini : build a small expression language in Pythonoperating-system : build an x86 operating system from bootloader to shell - Start Here - Guides - 5 Minute Demo - How Primer Works - Why Primer - Is Primer Beginner-Friendly? - Who It's For - Installation - AI Tool Integration - Available Recipe - Tracks - Agent Workflow Actions - CLI Setup Commands - JSON Examples - Workspace Model - Troubleshooting - Contributing - License If you want the fastest path from zero to building inside your AI coding agent: primer list primer init cli-tool --tool codex --track learner --path ~/projects/task-cli-demo cd ~/projects/task-cli-demo primer doctor cli-tool --milestone 01-bootstrap Use the terminal for setup: primer list shows the catalog.primer init creates a separate project workspace and generates AI-tool instructions for it.primer doctor checks whether your local toolchain is ready for the first milestone. Then open the generated workspace in your AI coding agent and use the Primer workflow actions there: primer-build : implement only the current milestone scopeprimer-verify : run milestone verification and mark it verified on successprimer-next-milestone : unlock the next milestone only after verification passesprimer-explain : show the deeper explanation for the current milestoneprimer-status : show current milestone, verification state, retries, and progress Primer is designed so that: - In a regular shell, you mainly use primer for setup, diagnostics, and utilities such asinit ,doctor , andcompletions . - Inside a generated workspace in a supported AI tool, you do the actual milestone work through generated actions such as primer-build andprimer-status . If you are new to Primer, start with --track learner . If you want one short walkthrough instead of the general setup story, use the 5 minute demo. Primer's public docs now have three main entry paths: - Learn With Primer: the beginner-friendly path focused on cli-tool , learner track, and understanding the loop - Build Safely With Primer: the execution-focused path for milestone-by-milestone delivery and JSON wrappers - Use Primer In An Existing Repository: the brownfield path built around workstreams, boundary analysis, and repo-local state If you only want one short walkthrough, jump straight to the 5 minute demo. The best quick demo path today is the beginner-friendly cli-tool recipe. What this path demonstrates: - initialize a workspace - inspect the current milestone - watch verification fail before the code exists - implement one milestone - verify it successfully - advance safely The full walkthrough lives in docs/5-minute-primer.md. Quick start: primer init cli-tool --tool codex --track learner --path ~/projects/task-cli-demo cd ~/projects/task-cli-demo primer doctor cli-tool --milestone 01-bootstrap Then open the workspace in your AI tool and use: primer-status primer-build primer-verify primer-next-milestone Primer has two layers: - The setup layer: the primer CLI creates the workspace, checks your environment, and manages workflow state. - The working layer: your AI coding agent uses the generated Primer actions inside that workspace while you build milestone by milestone. In practice, that means: - you touch the terminal first to initialize the workspace - you spend most of your time inside the AI coding agent - Primer verification decides when a milestone is actually complete The CLI is important infrastructure, but it is not meant to be the primary day-to-day interface. Most AI coding workflows fail in predictable ways: - the task is too broad - the agent implements future steps too early - there is no reliable check for "done" - progress is hard to see Primer turns that into a repeatable loop: - Initialize a separate project workspace from a recipe. - Load the current milestone contract. - Build only that scope. - Run verification. - Advance only after it passes. The result feels closer to a guided lab than an open-ended prompt. The workflow is beginner-friendly. The current recipe catalog is not broadly beginner-oriented yet. That distinction matters: - Primer itself is designed to be approachable for students, entry-level developers, and people learning with AI assistance. - The current flagship recipe, operating-system , is still an advanced systems project with a real toolchain and