Page: 'Alderwood Relaunch — Task Board'\n\nIn Progress:\n- Homepage copy (Tom) — updated yesterday, on track for review Friday.\n- Case study template (Fieldstone/Jess) — status says 'in progress', last comment was 8 days ago: 'starting on this soon.' No draft shared yet.\n- Pricing page dev build (Marcus) — updated this morning, two of three components done.\n- Dev environment setup (Marcus) — status says 'in progress' since Week 1, no comments or updates since then. Marcus mentioned in standup last week he 'hasn't gotten to it yet' but didn't move the ticket.\n- Blog redesign scope (unassigned) — card exists, no owner assigned, no updates since creation. David mentioned wanting this in the original brief but nobody has picked it up.\n- Stock photography selection (Priya) — updated today, final picks sent to Fieldstone.\n\nDone:\n- Homepage wireframes (Fieldstone)\n- Kickoff call notes (Priya)\n- Sales pricing alignment doc (Priya + Sales team)\n\nBlocked (explicitly marked):\n- Case study interviews with 2 customers — waiting on customer availability, one has not responded to outreach in 5 days.\n\nAuto-detected: Two cards marked 'in progress' show no real movement in over a week, case study template and dev environment setup, and one card has no owner at all, the blog redesign.

Summary  
This chapter demonstrates how to filter and classify items in a collection by their status and last update to identify genuinely blocked entries and determine which blocker, if resolved, frees the most downstream work.

General domain of usage  
Project management (task or issue tracking)

Still Priya, still the Alderwood relaunch. Your team tracks its work on a task board — the shared list of everything in progress, done, and blocked. The problem: a board full of "in progress" labels can hide the one task that's actually stuck, because "in progress" often just means someone opened it once and never came back.
 
In this chapter Claude reads the task board and tells you what's genuinely blocked versus just quietly sitting there.

The task board is connected as a tool for this chapter — it stands in for something like a shared Notion or Trello board your team would use. Here's what's currently on it, so you can see what Claude is reading:

Note

>### Task
> 
> Ask Claude to read the task board and tell you which items are genuinely blocked versus just labeled "in progress" without real movement — and why.
 >
>**Prompts to Try**
 >
>><b>Read the Alderwood relaunch task board and tell me which items are genuinely stuck versus just sitting there, and why.
 >
> Working with your own board instead? Describe it, then ask: 
>
>><b>Which of these are actually blocked, and what needs to move to unstick them?
> 
>**What you're aiming for:** Claude should separate real blockers from stale "in progress" cards — catching that the case study template and dev environment setup haven't moved in over a week, and that the blog redesign has no owner at all. It should end by naming the one blocker that, if solved first, unblocks the most other work. When the hidden stuck items are visible, you're done.

Discover how to keep a real project from falling apart: turn a messy brief into an actual plan, catch budget and schedule problems before they bite, push back on scope creep, and keep your team coordinated under a hard deadline. You'll practice it all through a live website relaunch, with Claude helping you plan, defend, and coordinate the work end to end.

Get hands-on experience turning a scattered project brief into a task list, then checking that plan against a real calendar and a real budget before you commit to a deadline.
 

Discover how to defend a deadline against scope creep, find the task that's quietly stuck, and chase down a vendor who's gone quiet — before any of it becomes a crisis.

Master the skills needed to research the competitive landscape, update stakeholders clearly, track the whole team's progress in one place, and coordinate a final sprint under pressure.