[whpalmer4]

My suggestion is that you don't actually have the project repeat, and here's why: if for some reason you don't check off every last item in this weekend's project, you won't get next weekend's project created until you do so (or mark the project complete).

Instead, just make a parallel project or single action list, and have each of the actions repeat individually. Put a start date on them so you don't see them until you want them. The repeat policy would be Repeat Every 1 week (so the dates stay aligned). Start Again is what you would do for scheduling a task that happens a fixed amount of time after you do it the previous time, like a haircut—no point in getting your monthly on the 1st of the month if you didn't manage to get it done until the 15th this month. Repeat Every is what you would use for scheduling a task that happens at a specific time of the month, like paying the rent—you don't get to pay it later next month if you were late this month.

With my scheme, you will still see the project if you look at a project mode view, but about the only time I spend looking at project mode, I'm either adding or editing a project, or doing a review. I spend most of my time in context mode actually executing available actions, and there it will be invisible except when there are actions to do.

Minor pro/con: with Brian's solution, you'll get a completed project for each week. With mine, you won't have any completed projects, but you will have a lengthy list of completed tasks in the ongoing project. If you need to do a report over time, my approach might be easier; if you want to delete the completed work, Brian's might be easier.