Lesson 06 | Act 6: Wrap-up

⏱ Est. reading time: 4 min Updated on 5/7/2026

Act 6: Wrap-up (Episodes 13-14)

From "it works" to "delivery"

Episode 13: How Do We Know It's Done? — Verification Methodology

Scene: The code is written, but how do we confirm it's actually finished?

  • Verification is not just running tests once
  • Goal backtracking: Reverse-check from Phase goals, have all "must be true" statements been verified?
  • What /gsd-verify does: Independent agent reads PLAN.md goals → checks code → generates VERIFICATION.md
  • Code review: /gsd-code-review multi-dimensional scan (security/performance/maintainability), severity levels (Critical/High/Medium/Low)
  • Fix workflow: Review finds issues → /gsd-code-review-fix automatically patches line-by-line
  • What passing all 154 project tests means (what is covered, what isn't)
  • Core concept: Being done ≠ being right; verification is an independent step

Output Files:

  • .planning/phases/*/VERIFICATION.md — 4 verification reports
  • .planning/phases/*/REVIEW.md — Review reports

Command: /gsd-verify, /gsd-code-review


Episode 14: Retrospective — From a Sentence to a Complete Product

Scene: Wrapping up. Looking back at what we achieved along the way.

  • Start point: "Build a calculator that elderly people can use" (One sentence)
  • End point: 3 files / 1529 lines of code / 1631 lines of tests / 154 tests all passed
  • Complete file list and their roles:
    • index.html — 57 lines, semantic structure, full ARIA
    • style.css — 535 lines, CSS variable dual themes, 3-breakpoint responsiveness
    • app.js — 937 lines, four-layer architecture (engine/state machine/UI/persistence)
    • .planning/ — Full project planning logs (requirements/roadmap/decisions/plans/verification)
  • Bug hunt checklist: Floating-point precision, CSS Grid hidden elements, file:// protocol limitations
  • GSD Workflow recap:
    • /gsd-new-project — Idea → Structured
    • /gsd-discuss-phase — Lock decisions
    • /gsd-plan-phase — Break down tasks
    • /gsd-execute-phase — Write code
    • /gsd-verify — Verify
    • /gsd-quick — Quick fixes
  • Can this method be reused on other projects? (Yes — GSD applies to any software project)
  • v2 Outlook: Scientific calculation, currency conversion, PWA offline installation

Appendix

A. GSD Command Quick Reference Used in this Project

Command When to Use Times Used in Project
/gsd-new-project Have an idea, want to start 1
/gsd-discuss-phase Lock decisions before coding 4 (Once per Phase)
/gsd-plan-phase Break decisions into tasks 4
/gsd-execute-phase Execute tasks & code 4
/gsd-verify Confirm it was done right 4
/gsd-code-review Check code quality As needed
/gsd-quick Small fixes As needed
/gsd-debug Investigate bugs As needed

B. Technical Concept Index

Alphabetically sorted, noting which episode they appeared in:

  • ARIA labels → Episode 9
  • CSS Custom Properties → Episode 8
  • Event Delegation → Episode 6
  • FIFO Queue → Episode 5
  • Media Query → Episode 12
  • Shunting-yard → Episode 3
  • State Machine → Episode 7
  • TDD → Episode 4
  • XSS Prevention → Episode 11