The 7-day Finish One challenge
One abandoned project.
One week to ship it.
Starting another project is not allowed. Choose the unfinished repo with the shortest credible path to a user, clear one class of risk at a time, and finish with evidence. No account is required and the first scan runs entirely in your browser.
Choose by evidence
Scan the portfolio. Pick the project closest to a real user, not the idea you feel most guilty about.
Define done
Write one observable finish line: deployed, installable, submitted, published, or handed to its first user.
Remove launch blockers
Handle secrets, authorization, payment verification, migrations, and other issues that make a working demo unsafe to release.
Close the smallest gaps
Turn vague remaining work into tasks small enough for one focused session. Delegate labor; keep judgment.
Verify the path
Run the real tests and walk the critical user journey. Record what is proven and what still needs human confirmation.
Make it findable
Deploy it, document the first-use path, add basic measurement, and give one real person access.
Ship and close the loop
Publish the release, note what changed, and share the result. Only then choose the next project.
The rules
- Do not add a feature unless it is required by the finish line.
- Every agent edit is reviewed before it reaches disk.
- A passed check is evidence; confidence is not.
- Sharing is optional. Shipping is the point.