Skip to content

This page was translated from the Korean original with AI and may contain errors.

Chapter 1. Building with AI — SDLC at a Glance ​

Required Read this to follow this stage.

One-line summary: Software reaches the world through Plan → Create → Review → Test → Deploy → Operate. This flow is called the SDLC. AI acts as your hands at each stage, but deciding what to build and checking the results is your job. Stage 4 teaches you how to divide this work.

This chapter is based on the GitHub official docs and Claude Code official docs checked on November 1, 2026. It is written for readers who have already worked with folders using Claude Code, Codex, or Antigravity in Stage 3. If you have not read Stage 3 yet, start with Stage 3 · Claude Code.

What Is the SDLC? ​

The SDLC (Software Development Life Cycle) describes the stages a project moves through, from the first idea to actually running software.[1] GitHub divides this process into six stages.

StageWhat you doIn this guide
PlanWrite down and track your workChapter 3
CreateWrite code and record changesChapter 4
ReviewPropose changes and get feedbackChapter 6
TestRun automatic checks before mergingChapter 5
DeployRelease your work so people can use itChapter 7
OperateWatch it and keep improving itChapters 8 & 9

Source: GitHub official docs (summarized by this guide)[2]

The order of chapter numbers in the table is a little different. This guide covers Test (Chapter 5) before Review (Chapter 6). That way, you can look at the test results while reviewing.[3]

You do not need to use every stage from day one. GitHub also notes that many people start with one repository and a few tasks, then expand as their project grows.[4] In this guide, you will also go through all six stages once with a single small web page.

Quick check

Which statement accurately describes the SDLC according to GitHub?

How AI Works ​

Claude Code handles a task in three steps: gather context → take action → verify results.[5] Finding and reading files, editing them, and running tests to check its own work are all part of this loop.

Plan mode, which you tried in Stage 3, becomes important again here. In plan mode, Claude reads your files and proposes a plan, but it does not change anything until you approve.[6]

The official best practices docs point out two common reasons why work does not turn out as expected:[7]

  • It built something different from what you had in mind. This happens when information that cannot be found just by reading the repository is missing. → Covered in Chapter 3, "Planning and Specifications".
  • It said it was done, but it was not quite finished. This happens when it had no way to check its own work. → Covered in Chapter 5, "Verification and Testing".

You can reduce both cases by handing AI the right information and a way to check the work. That is why Stage 4 focuses less on how to write code and more on what to hand to AI, and what to get back and verify.

Quick check

According to official docs, what is a common reason AI says it is done when the work is actually incomplete?

Your Job as the Human ​

Even when AI acts as your hands, there are jobs that you must handle yourself.

StageYour job
PlanDecide what to build and why
CreateRead and approve the plan
TestLook at the evidence (commands and output) and judge
ReviewDecide whether to merge
DeployJudge whether it is safe to publish and press the button

Source: Summarized by this guide (see footnotes in each chapter for sources)

The official docs also state that you are responsible for reviewing proposed code and commands for safety before approval.[8] Also, actions that affect outside systems—like deployment—cannot be undone with Claude Code's rewind (checkpoints).[9] A checkpoint is a save point that is created automatically every time you send a request. Like a save point in a game, most files on your computer that Claude changed can be rolled back to that moment (except files changed by shell commands or other sessions). But something you have already published on the internet does not come back. So the more an action reaches the outside world, the more important it is that you check it and press the button yourself.

Quick check

According to this guide, what must a human always be in charge of when building with AI?

What You Will Build in This Stage ​

The "Try It Yourself" sections in Stage 4 follow a single example across every chapter. You will build a web page that collects and displays the action items from the meeting notes created by your Stage 3 organizer tool, called the "Corner Cafe To-Do Board".

GitHub's official getting-started series also follows one small website from start to finish as you plan work, write code, review changes, and deploy to a live website.[10] This guide follows the same order, using Claude Code from Stage 3 in the AI role.

A few unfamiliar words appear in the table. For now, just get a light sense of what they mean. Each chapter covers them step by step.

  • GitHub: a service where you put project files and change history on the internet and work together
  • Repository: the place that holds project files and change history. It is the project's home
  • PR (Pull Request): a change proposal you put forward saying "Please merge in what I changed"
  • GitHub Pages: a feature that publishes the files in a repository as a web page for free
ChapterWhat you do on the To-Do Board
2Create a repository on GitHub
3Get interviewed about what to show and write SPEC.md
4Receive a plan and build the first screen on a branch
5Build a check to verify the number of to-do items matches
6Create a PR and get it reviewed
7Publish it with GitHub Pages
8Write the next improvement as an issue and go around the cycle once more
9Check for secrets and personal information before publishing

Source: This guide's plan

It does not need to be perfect from the start. Follow along one chapter at a time, and by the end you will have your own page with a live web address.

Summary ​

  • The SDLC is the set of stages from an idea to running software. GitHub divides it into six stages: Plan, Create, Review, Test, Deploy, and Operate.
  • You do not need to use all of them from day one. Start small and expand.
  • Claude Code works by gathering context → taking action → verifying results. Common reasons for failure are missing information and having no way to verify the work.
  • Deciding what to build, judging the evidence, and deciding whether to merge and deploy are your job.

Key Terms ​

TermOne-line meaning
SDLCThe stages software moves through from idea to operation
RepositoryThe place where project files and change history are stored
DeployReleasing what you built so people can use it
Plan modeClaude Code's mode that shows only a plan before making edits

Finished this chapter?

Progress is saved only in this browser. See your progress on the full table of contents.

Next chapter: Chapter 2. Creating a GitHub Repository

References (10)
  1. GitHub official docs, "What is GitHub?". "The software development life cycle describes the stages a software project moves through, from the first idea to running code in production." docs.github.com (checked on 2026-11-01) ↩︎

  2. GitHub official docs, "What is GitHub?". "Track your work, set milestones, and organize long-term projects." / "Write and store code, develop new features safely, and create a clear timeline of your changes." / "Suggest changes to your project, discuss your updates with reviewers, and apply feedback." / "Automate checks to validate every change before it merges." / "Ship software with automated deployment workflows and release management." / "Monitor applications, manage dependencies, and find and fix security issues." docs.github.com (checked on 2026-11-01) ↩︎

  3. On GitHub, "Operate" covers a wide range from monitoring and dependency management to security. This guide covers only improving through issues (Chapter 8) and safety (Chapter 9). ↩︎

  4. GitHub official docs, "What is GitHub?". "You do not need to use every stage at once. Many people start with a repository and a few issues, then expand their use of the platform as their project grows." docs.github.com (checked on 2026-11-01) ↩︎

  5. Claude Code official docs, "How Claude Code works". "When you give Claude a task, it works through three phases: gather context, take action, and verify results." code.claude.com (checked on 2026-11-01) ↩︎

  6. Claude Code official docs, "Common workflows". "For changes you want to review before they touch disk, switch to plan mode. Claude reads files and proposes a plan but makes no edits until you approve." code.claude.com (checked on 2026-11-01) ↩︎

  7. Claude Code official docs, "Best practices for Claude Code". "It's missing information it can't get from reading the repo." / "Claude said it was done and it wasn't quite, usually because it had no way to check its own work." code.claude.com (checked on 2026-11-01) ↩︎

  8. Claude Code official docs, "Security". "You're responsible for reviewing proposed code and commands for safety before approval." code.claude.com (checked on 2026-11-01) ↩︎

  9. Claude Code official docs, "How Claude Code works". "Actions that affect remote systems (databases, APIs, deployments) can't be checkpointed." code.claude.com (checked on 2026-11-01) ↩︎

  10. GitHub official docs, "Creating a repository for your project on GitHub". "By the end of the journey, you'll plan work, write code, review changes, and deploy your code to a live website." docs.github.com (checked on 2026-11-01) ↩︎