Assignment at a glance

In about 30 minutes, you will create a small ChatGPT for Work project for a useful productivity or course task. The goal is not to produce many files. The goal is to make a simple project that knows what it should do, how it should respond, and where its limits are.

What you must build

• One AGENTS.md file that tells ChatGPT the project purpose, normal workflow, important limits, and when to ask before acting.
• Any two supporting Markdown files chosen because they improve your specific project.
• One quick fresh-chat check. You do not need to document the test in TESTS.md or provide formal evidence.
• A one-page PDF explaining what you built and why you chose those files.

What is optional

• MEMORY.md and an automatic memory instruction are optional. If you choose them, the file may be empty when submitted; you do not need to manufacture interaction entries.
• TESTS.md and BUILD_LOG.md are optional. No test IDs, memory IDs, screenshots, or populated evidence logs are required.
• Skills, plugins, connectors, reference folders, templates, and additional Markdown files are optional and should be used only when they clearly help the project.

Step 1 - Pick a useful project (3 minutes)

Choose one small, repeatable task. A focused project is easier to govern and easier to complete within the time limit.

Good project ideas

• Turn rough class notes into a concise study guide.
• Prepare a meeting agenda and follow-up draft from notes.
• Review a draft against a checklist or rubric.
• Create a weekly plan from a list of priorities and deadlines.
• Draft consistent project updates from a few bullet points.

Help me turn this idea into a small ChatGPT for Work project that can be built in about 30 minutes.

My idea: ____ PROJECT IDEA ____

Ask no more than three short questions. Then propose:
- a one-sentence purpose;
- the main input the project will receive;
- the main output it should produce;
- one important limit;
- a simple project name.

Keep the scope narrow and practical.

Step 2 - Create the project (3 minutes)

Create a local project in the ChatGPT desktop app and give it access to a new folder. Let ChatGPT handle the Markdown syntax and file creation.

Your starting folder

• Create one empty folder with a clear name and open it as a local project.
• Confirm that ChatGPT can read and create files in that folder.
• Start with AGENTS.md. Add only two supporting files now; you may add more later if they genuinely help.

I am building a small ChatGPT for Work project.

Project purpose: ____ ONE-SENTENCE PURPOSE ____

Create these files in the current project folder:
1. AGENTS.md
2. ____ SUPPORTING FILE 1 ____
3. ____ SUPPORTING FILE 2 ____

Use clear beginner-friendly Markdown. Keep every file short and practical. Do not create any other files yet. Before writing, tell me in one sentence what each selected file will control. Then create the files.

Step 3 - Build the core files (12 minutes)

AGENTS.md is the only specific file required for everyone. Then choose any two supporting files that match what your project needs.

Required: AGENTS.md

• State the project purpose and the kind of work it should handle.
• Describe the normal workflow in a few steps.
• Name the supporting files and explain when ChatGPT should use them.
• Include at least one guardrail: something the project must not do or must ask about first.
• Include a simple verification rule: verify claims that are current, consequential, uncertain, or based on an external source; do not over-verify routine formatting and rewriting tasks.

Create or revise AGENTS.md for this project.

Project purpose: ____ ONE-SENTENCE PURPOSE ____
Supporting files: ____ CHOSEN SUPPORTING FILES ____

Keep AGENTS.md under 500 words. Include:
- purpose and scope;
- the normal workflow;
- which supporting files to read and when;
- at least one clear guardrail;
- when to ask for confirmation;
- a short verification policy that distinguishes claims that need checking from routine work that does not.

Use direct instructions. Avoid repeating the same rule in multiple sections. Do not add a memory loop, testing log, connector, or skill unless I ask for one.

Choose any two supporting files

Create or revise these two supporting files: ____ CHOSEN SUPPORTING FILES ____.

Project purpose: ____ ONE-SENTENCE PURPOSE ____

For each file:
- include only information that belongs in that file;
- keep it under 300 words;
- use headings and bullets where helpful;
- make the instructions specific enough to guide behavior;
- do not invent personal information, policies, sources, or requirements.

After writing, give me a two-line explanation of why each file is useful to this project.

Step 4 - Consider optional upgrades (5 minutes maximum)

Stop after the core files unless an optional feature clearly improves your use case. Optional features are never required merely because they appear in this guide.

Optional MEMORY.md

If memory is useful, you may create MEMORY.md and tell AGENTS.md when to update it. The submitted file may contain only its headings or template. You are not required to populate it with past interactions, memory IDs, or evidence.

Do not store passwords, access tokens, private keys, payment data, or unnecessary sensitive personal information in MEMORY.md.

Only if memory is useful for this project, create a short MEMORY.md template and add a matching instruction to AGENTS.md.

Project purpose: ____ ONE-SENTENCE PURPOSE ____

The memory template should capture only stable, useful, non-sensitive project information and short summaries of important completed interactions. Keep it simple. Do not invent or backfill entries. Do not require test IDs or evidence. Make it clear that the memory file is optional and should be updated only when there is something worth carrying into a future chat.

Optional skills and connectors

A skill is useful when the project repeats the same multi-step method. A connector is useful when the project needs access to another service. Both add complexity, so skip them unless they solve a real need.

My project purpose is: ____ ONE-SENTENCE PURPOSE ____

The optional feature I am considering is: ____ OPTIONAL FEATURE ____

Tell me whether this feature provides enough value for a 30-minute beginner project. Answer with:
- Add it / Skip it;
- one-sentence reason;
- the smallest safe implementation if I add it.

Do not recommend an optional feature simply to make the project look more advanced.

Step 5 - Run one quick check (3 minutes)

Open a fresh chat inside the project and try one realistic request. This is a quick usability check, not a formal testing exercise.

• Use an input that resembles how you would really use the project.
• Check whether the answer follows the purpose, style, limits, and verification rule.
• If one problem is obvious, ask ChatGPT to make one focused correction to the relevant Markdown file.
• You do not need to create TESTS.md, record a test ID, capture a screenshot, or claim that every possible case works.

Use the project instructions to complete this realistic request:

____ REPRESENTATIVE REQUEST ____

Follow the project files exactly. If information is missing, ask only the questions needed to continue. Do not change any files during this request.

The fresh-chat result had this problem:

____ PROBLEM OBSERVED ____

Identify the single most relevant Markdown file and propose the smallest change that would prevent this problem next time. Show the exact change before editing. Do not add new files unless the problem cannot reasonably be solved in an existing file.

Step 6 - Prepare the submission (4 minutes)

Submit a one-page PDF and the Markdown files you actually created. Do not create empty optional files merely to make the folder look complete.

One-page PDF contents

• Project name and one-sentence purpose.
• The three required files you created: AGENTS.md and your two selected supporting files.
• Why you chose those two supporting files.
• Two important instructions, such as a style rule, guardrail, or verification rule.
• One sentence describing the fresh-chat check and any small correction you made. No screenshot or evidence log is required.
• Any optional feature you included and why it was useful. Write “None” if you did not add one.

Draft a concise one-page assignment report using this information:

Project purpose: ____ ONE-SENTENCE PURPOSE ____
Files created: ____ FILES CREATED ____
Why I chose the supporting files: ____ WHY THESE FILES ____
Two important instructions: ____ TWO IMPORTANT INSTRUCTIONS ____
Fresh-chat check: ____ QUICK CHECK RESULT ____
Optional feature, if any: ____ OPTIONAL FEATURE ____

Use clear headings and short paragraphs or bullets. Do not invent test evidence, memory entries, file contents, or optional features. Keep the report comfortably within one page.

Submit these items

• Your one-page PDF.
• AGENTS.md and the two supporting Markdown files.
• Any optional Markdown files you genuinely used.

Grading rubric (100 points)

The rubric rewards clarity, fit, and good judgment. Extra files, skills, connectors, memory entries, and test logs do not earn automatic credit.

Quick reference and troubleshooting

Markdown basics

You do not need to type the Markdown yourself. Ask ChatGPT to create or revise the files, then read the result and make sure the instructions match your intent.

If something is not working

• Check that the local project is connected to the correct folder.
• Check that the filename is exactly AGENTS.md and is in the project root.
• Ask ChatGPT to explain which project file governed an unexpected response.
• Prefer one small correction to the relevant file instead of adding more files.

Review this project as a concise 30-minute beginner assignment. Do not edit files.

Confirm only these requirements:
- AGENTS.md exists and is clear;
- two supporting Markdown files exist and each has a useful role;
- there is at least one guardrail and one verification rule somewhere in the project;
- the files do not contain secrets or unnecessary sensitive information;
- the one-page report accurately describes what was built.

Treat MEMORY.md, TESTS.md, BUILD_LOG.md, skills, plugins, connectors, references, and templates as optional. Do not ask for test IDs, memory entries, screenshots, or evidence logs. End with Ready / Needs one small fix and name only the highest-priority fix.