Stage 4 · AI-SDLC Guide
SDLC (Software Development Life Cycle) is the series of steps an idea goes through to become working software. In Stage 4, you will use the AI tools you learned in Stage 3 to build a small web page from planning to deployment and improvement. It is okay if you do not know how to code. What you learn in this stage is not how to write code, but what to hand over to AI, and what to get back and check.
This guide is based on the official GitHub and Claude Code docs, as well as the spec-kit and OpenSpec repositories, checked on November 1, 2026. Features and screen names change often. A free GitHub account is all you need. For AI tools, you will use the same ones from Stage 3 (Claude Code, Codex, Antigravity).
| Chapter | Reading | Title | What You Will Learn |
|---|---|---|---|
| 1 | Required | Building Together with AI | The six stages of SDLC, how AI works in a loop, what humans are responsible for |
| 2 | Required | Creating a GitHub Repository | Git, GitHub, and repositories, public vs. private, README, .gitignore, license, and cloning |
| 3 | Required | Planning and Specification | Getting interviewed for SPEC.md, what a good spec looks like, spec-driven development tools |
| 4 | Required | Building | Plan mode, branches, small commits, reading what AI built |
| 5 | Required | Checking and Testing | Verification checks, getting proof, GitHub Actions |
| 6 | Required | PR and Review | Pull requests, reviewing even when working alone, limits of /code-review, merging |
| 7 | Required | Deploying | GitHub Pages, how to publish, limits and prohibited uses, irreversible deployments |
| 8 | Required | Operating and Improving | Issues, labels, and boards, the fixes keyword, going around the loop once more |
| 9 | Required | Safety and Responsibility | Three layers of defense for secrets, pre-public checklist, licenses and AI output, dependencies |
| 10 | Required | Hands-on Project | One full cycle with the to-do board, starting from scratch with your own problem, checklist |
Ongoing Example — Corner Cafe To-Do Board
The "Try It Yourself" section at the end of each chapter connects into a single example. It is a web page that collects and shows action items from the meeting notes created by the Stage 3 organizer tool. For the to-do data, you will use the results from Stage 3.
All names in the notes (Minji, Junho, Seoyeon) are fictional. If you use your own notes instead, remove real names and contact info before uploading to a public repository (Chapter 9).
You can see a to-do board actually built by following this guide on the example page and in the repository. It is fine if yours looks different.
If you have not gone through Stage 3 yet, start with Stage 3 · Claude Code. Folders, permissions, rule files, and plan mode are explained there, and this stage links back to them.