skills/prepare-submission/references/content/steps/prepare.md

# Prepare your submission

Turn your project into a clear Devpost-ready draft.

Codex will create or update `devpost-submission.md`, but you still need to gather the evidence and assets the final Devpost form will ask for.

Before you move to `$submit-project`, go do these things:

- [ ] Confirm the project title and one-sentence summary.
- [ ] Write the problem, target user, and why the project matters.
- [ ] List the features that work today. Keep future plans separate.
- [ ] Explain exactly how you used AI capabilities.
- [ ] Explain exactly how Codex helped you build, debug, test, or iterate.
- [ ] Add the public repository URL, or note why it is not public yet.
- [ ] Add the public demo URL, install/run instructions, or a local demo fallback.
- [ ] If this is a web app, open it in your browser and give Codex screenshots, logs, or notes for feedback.
- [ ] Capture 3-5 screenshots that show the project working.
- [ ] Record or outline a short demo video: problem, demo flow, AI/Codex usage, and final result.
- [ ] Run the project locally and write testing instructions.
- [ ] Name any known limitations honestly.
- [ ] Fill placeholders in `devpost-submission.md`, then rerun `$prepare-submission` if the draft changed materially.

When most boxes are complete, run `$submit-project`. If several boxes are still missing, do the missing work first and run `$prepare-submission` again.

Remember: preparing is drafting. Nothing is sent to Devpost until `$submit-project` reports "✅ Submitted to Devpost."
<!-- Copy maintainers: edit this page copy in content/steps/prepare.md. -->