CompCode Academy

Lesson 61 of 65 · Free to read

Day 61 ΓÇö Capstone scoping

Month 3 · Week 13 — Capstone & Launch Audience: Final-year students & early-career engineers (0–3 years) Format: Self-paced study + optional live clinic · Suggested time: 4–6 focused hours Key tools: Claude

Overview

Capstone scoping: pick a portfolio-worthy product; write PRD + architecture; decide where agents, SLMs, n8n, or MCP add real value — not decoration.

Learning objectives

By the end of this session, you can:

  • Explain the core ideas behind: Capstone scoping: choose a real, portfolio-worthy product and write its spec and architecture.
  • Apply the ideas using Claude on a realistic task (capstone, internship, or first-job style)
  • Produce the exercise deliverable with clear success criteria
  • Identify common failure modes and how to recover
  • Capture at least one reusable prompt, rule, or checklist for your personal library
  • Decide what must remain human-reviewed for this class of work

Core concepts

Portfolio bar

Real problem, live URL potential, clear AI differentiator, testable milestones.

AI value test

If removing the AI component doesn’t hurt the product story, cut it.

Tooling for today

Primary tools: Claude. Prefer official docs when APIs change. When a model invents a symbol, verify against source or docs immediately.

Practice posture

You are a final-year or early-career engineer pairing with a very fast teammate (the model): clear intent, grounded context, inspect consequential changes, keep a paper trail (commits, prompts, decisions).

Process diagram

Watch & learn

Study these free videos before or during the exercise. Each embed is chosen to reinforce today's objectives.

Course video

Open on YouTube
Stop Vibe Coding. Use This Instead. — Spec-driven recovery from “accept all” failure modes.

Course video

Open on YouTube
How to Speak (Patrick Winston, MIT) — Demo and presentation craft for launch days.

Worked example / case study

Scenario

Finalize PRD, architecture, milestones; justify AI components.

Step-by-step

  1. Clarify the outcome in one sentence tied to the exercise below.
  2. Gather grounding context (files, docs, schema, acceptance checks).
  3. Run the primary tool(s): Claude.
  4. Produce the smallest vertical slice that proves the idea.
  5. Verify with a command, test, screenshot, or side-by-side comparison.
  6. Write down one steering note — what you told the AI when it went wrong.

Sample prompt you can adapt

Role: Senior engineer mentoring an early-career developer (pairing with me).
Task: Capstone scoping: choose a real, portfolio-worthy product and write its spec and architecture.
Context: Final-year / early-career project (capstone, internship, or junior role).
Constraints:
- Match existing project patterns
- No new dependencies unless justified
- Include tests or a verification checklist
- Call out assumptions explicitly
Output: step plan first, then code/files, then verification commands.

Hands-on exercise

Primary task. Finalize the PRD, architecture, and milestone plan. Decide where an AI agent, a small language model, an n8n automation, or an MCP server adds genuine value.

Coaching notes

Create a day-by-day build board for 62–65.

Steps

  1. Set up or open the workspace required by: Claude.
  2. Skim today's core concepts and watch the video(s) before prompting.
  3. Execute the task in small commits (or saved artifacts if no-code).
  4. Fill the success checklist below.
  5. Note one surprise and one process improvement for tomorrow.

Success criteria

  • Deliverable matches the exercise description
  • You can explain every AI-generated change in plain language
  • Verification ran (tests, manual check, or published URL)
  • At least one pitfall from this lesson was consciously avoided
  • Artifact saved (repo commit, doc, or published link)

Timebox

Suggested: 90–150 minutes of focused build time after study.

Templates & checklists

AssetPurpose
Prompt stubReuse today's structure (role → task → constraints → format)
Verification checklistTests / manual QA / security skim
Decision logWhat you delegated vs kept human

Copy-paste prompt skeleton

## Goal
Capstone scoping: choose a real, portfolio-worthy product and write its spec and architecture.

## Context files
- (list paths)

## Constraints
- Stack: (fill)
- Do not: (secrets, drive-by refactors)

## Definition of done
- Finalize the PRD, architecture, and milestone plan. Decide where an AI agent, a small language model, an n8n automation, or an MCP server adds genuine value.

Daily reflection (3 minutes)

  • What did AI do well?
  • Where did it confidently fail?
  • What rule will you add to your cookbook/rules file?

Common pitfalls

  • Scope that needs a team of eight
  • AI bolted on without user value
  • No milestone plan

Key takeaways

  • Scope is destiny
  • AI must earn its place
  • Milestones prevent Day-64 panic
  • Tools (Claude) change; the judgment skills transfer.

Resources

  • Official docs for: Claude
  • Course cookbook: keep prompts in a versioned Markdown file in your repo
  • Prior days this week — skim objectives if you skipped ahead

Self-paced lesson — Mastering AI-Assisted Development & Vibe Coding — Day 61 of 65.

New free lessons and course updates. Unsubscribe from any email.