Projects: long-running goals

Give a continuing website goal one home in Claude Code Projects, where Claude coordinates the related tasks. This walkthrough starts with an evidence-based review so you can judge the results before authorizing changes.

Before you start

• A Pro or Max subscription with Projects already visible at claude.ai/code. The public beta is rolling out gradually; Team and Enterprise are not currently included.
• For code work: a repository on github.com, push access through your connected account, and the Claude GitHub App installed for that repository.
• A written goal and the pages to check, for example “Find what prevents a visitor from requesting a quote on a phone”.

Want to do it yourself?

Difficulty

6 out of 10

Estimated completion time

45–90 minutes for the first work cycle

Skills you’ll need: Define a bounded goal, organize project context, and check progress and saved results before continuing longer work.

I’ll do it myselfI’d rather get help

How this helps your brand

A continuing website goal gives related reviews and repairs a common brief. Checking evidence across the coordinated tasks helps you prioritise changes that support the visitor action you care about.

1. 1

   Step 1: Define a goal you can inspect

   Choose one stream of work that will produce several related tasks. “Improve my website” leaves too much room for interpretation. “Review Home, Services, and Contact for a phone visitor trying to request a quote” gives you a clear first batch.

   Write what would count as success: a finding for each page, the evidence behind it, and a suggested next action. This first batch should report findings without editing the site.

2. 2

   Step 2: Create the project with relevant context

   At claude.ai/code, select Projects in the sidebar and then New project. Enter a clear name, add your goal, and use Context to add the repository or reference files the review needs. Select Create project.

   Review any setup recommendations before applying them. On a first project Claude can take an initial turn, so read what it started before assigning the same review again.

3. 3

   Step 3: Brief the coordinating conversation

   Paste the prompt below in the project conversation. Name the target branch and the pages in scope. Ask Claude to separate confirmed problems from recommendations and to show evidence for each finding.

   State the working rules in the message, including no edits or publication for this review. For future batches, put recurring rules in project instructions in Project settings under Memory.

   Illustrated exampleOne goal, three focused review threads

   Example work map main

   One continuing goalHelp a phone visitor request a quote

   Coordinating conversation Assign the first review batch

   • 01Home

     Follow the quote link from the first screen.

     Return: destination + evidence
   • 02Services

     Check whether the offer is clear before asking for a quote.

     Return: finding or missing detail
   • 03Contact

     Try the form and inspect its error messages.

     Return: steps + observed result

   Shared rule for every threadReport findings only. No edits, pull requests, messages, or publication.

4. 4

   Step 4: Inspect the threads and answer blockers

   Claude starts threads for the related work. Use Overview to find work waiting on you, then open the relevant thread to read its full conversation before responding.

   If a thread cannot access the repository, check that the GitHub App is installed for that repository and your connected account has push access. Access granted to an ordinary cloud session with /web-setup alone does not satisfy the project prerequisite.

5. 5

   Step 5: Review results before assigning the next batch

   Compare the returned findings with your original page list. For each issue, ask where it occurs, what the visitor did, what happened, and which evidence supports the conclusion. A suggested improvement without that evidence should stay a recommendation.

   Choose one small fix to authorize next, with a check that will prove it worked. If several threads suggest changing the same component, ask the coordinator to resolve that overlap before starting the fixes.

   Illustrated exampleUse evidence to choose the next small fix

   Illustrative findings · sample website

   Confirmed problemHome → quote link

   Visitor action

   On a phone, tap “Request a quote” on Home.

   Observed result

   The link opens a missing page at /quote.

   Evidence

   Reproduce: Home → tap the quote link → see the 404 page. Contact is available at /contact.

   Your next decision

   1

   Authorize one fixPoint the Home quote link to /contact.

   2

   Define the checkTap the link on a phone and confirm the Contact form opens.

6. 6

   Step 6: Check usage and pause when finished

   Open Usage in Project settings to inspect consumption. The coordinator and worker threads draw on your plan, so parallel work can use it faster than one session.

   When you want all work to stop, use Pause under Project settings, General. Pausing interrupts the conversation and running threads and stops new project work. Keep the project available for the next batch instead of deleting it.

Our continuing goal is [specific website goal]. Review [page list] in [repository] on [branch]. The visitor we care about is [visitor and device] trying to [main action]. Coordinate a first batch that reports findings only. Do not edit files, open pull requests, send messages, or publish anything. For each page, report the behavior you inspected, evidence with file paths or reproducible steps, confirmed problems, and separate recommendations. Do not describe a browser check as completed unless it actually ran. Ask me about missing business details. Finish with blockers and one small next task that I can choose to authorize.