Blog / AI & prompting · 8 min read ·
Prompting free AI assistants for your capstone, responsibly
Copyable prompt templates for titles, objectives, interviews, ERD review, debugging, test cases and defense practice, with the integrity rules to follow.
Free web chat assistants can save a capstone team hours of blank-page time, but only if you use them as a reviewer and a sparring partner, not as an author. This guide gives you prompt templates for the parts of a capstone where an assistant helps, and the rules that keep your work honest and your respondents' data safe.
Replace every [placeholder] with your own details before you send a prompt. The more specific your input, the less generic the answer.
Choosing a free assistant
Free web chat assistants such as DeepSeek Chat, ChatGPT free tier, Gemini and Claude free tier all handle the tasks in this guide reasonably well. Their limits, models and features change often, so check the current terms, message limits and data-use settings yourself before relying on one. Where a tool offers a setting to stop your chats being used for training, read what it does and decide as a team.
- Use one shared chat per topic (title, ERD, testing) so the context stays focused.
- Paste the relevant part of your document, not the whole manuscript.
- Ask for options and critique rather than a finished answer.
- Save useful prompts and the date you used them, in case your adviser asks how AI was involved.
The anatomy of a good prompt
Most weak answers come from weak context. A reliable capstone prompt has five parts. You do not need headings for each, but every part should be present.
| Part | What to include | Example |
|---|---|---|
| Role | Who the assistant should act as | An adviser reviewing a BSIT capstone proposal |
| Context | Your system, users and setting | A water billing system for a municipal water district in Batangas |
| Task | One clear thing to do | Point out scope problems in these objectives |
| Constraints | Limits and rules | Do not rewrite the objectives; list issues only |
| Output format | How you want the answer shaped | A numbered list, one issue per line, with a reason |
Prompt templates for each capstone stage
Refining a title
Draft your own title first. The assistant's job is to point out vagueness and suggest tighter wording, not to invent your topic. If you are still looking for a direction, the capstone title generator gives you starting points to react to.
Act as a capstone adviser for a [BSIT/BSCS/BSIS] programme in the Philippines. Our draft title is: "[your draft title]" The system is for: [beneficiary, e.g. barangay health workers in Barangay ___] The core problem: [one or two sentences] Platform: [web / mobile / web + mobile] List up to five weaknesses in the title (vague words, missing beneficiary, scope that is too broad). Then suggest three alternative titles that keep our meaning. Do not add features we did not mention.
Scoping objectives
Here are the general and specific objectives of our capstone, a [system type] for [beneficiary]: [paste objectives] Our team has [number] members and [number] months to build it. For each specific objective, tell me: (1) whether it is measurable, (2) whether it is achievable in our timeframe, and (3) which module of the system it maps to. Flag any objective that describes research we are not doing. Do not rewrite them; list problems and questions only.
Generating interview questions
Requirements gathering is where many teams go wrong, because they only ask questions that confirm the system they already want to build. Use the assistant to widen your question list, then remove anything leading.
We are gathering requirements for a [system type, e.g. clinic queueing system] at [type of organisation, e.g. a rural health unit]. We will interview [role, e.g. the nurse in charge of patient intake]. Write 12 open-ended interview questions that uncover: the current manual process step by step, where delays or errors happen, what records they keep and how, who approves what, and what they would not want changed. Avoid leading questions and avoid questions that assume a computer system is the answer. Group them by topic.
Reviewing an ERD in text
Assistants cannot reliably read a blurry photo of your diagram, but they review a plain-text list of entities well. Write your tables, columns, keys and relationships as text, then ask for a critique.
Review this database design for a [system, e.g. school enrolment system]. Act as a database instructor. Entities: [TABLE_NAME](column PK, column, column FK -> OTHER_TABLE) [repeat for each table] Relationships: [e.g. one STUDENT has many ENROLMENT records] Check for: missing primary or foreign keys, many-to-many relationships without a junction table, repeating groups or other normalisation problems up to 3NF, and columns that store derived values. Explain each issue in one or two sentences. Do not produce a new schema.
Explaining an error
I am building [feature] using [language/framework and version, e.g. PHP 8.2 with Laravel 11]. This is the error message: [paste the full error and stack trace] This is the code it points to: [paste the smallest relevant snippet, with passwords, API keys and real data removed] Explain what the error means in plain language, list the most likely causes in order, and tell me how to confirm each one. Do not rewrite my whole file.
Writing test cases
Write test cases for this feature of our [system]: Feature: [e.g. computing a monthly water bill] Rules: [e.g. minimum charge for the first 10 cubic metres, tiered rate after that, 10% penalty if paid after the due date] Inputs: [list the fields] Return a table with columns: Test ID, Description, Input, Expected result, Type (normal, boundary or invalid). Include boundary values for every numeric rule and at least three invalid inputs. Do not invent rules I did not list; ask me instead.
Polishing, not writing, chapter text
Write the paragraph yourself first, then ask for feedback on clarity and grammar. Read every suggested change and accept only what you understand and agree with. If your school requires disclosure of editing assistance, include it.
Below is a paragraph I wrote for Chapter [number] ([chapter title]) of our capstone manuscript. [paste your paragraph] Point out grammar errors, unclear sentences and repeated words. Show each suggestion as: original phrase, suggested phrase, reason. Keep my meaning and technical terms. Do not add new claims, sources or citations.
Practising defense Q&A
Act as a capstone defense panel of three: a technical panelist, a research methods panelist and an industry practitioner. Our system: [one-paragraph summary] Tech stack: [stack] Scope and limitations: [paste] Ask me one question at a time. After I answer, rate the answer as strong, acceptable or weak, explain why in two sentences, then ask the next question. Focus on scope, security, data privacy, testing and deployment.
What not to do
- Do not ask an assistant to write your chapters, your review of related literature or your conclusions.
- Do not cite a source an assistant gives you until you have found and read the original yourself; assistants can produce references that do not exist.
- Do not paste survey responses, interview transcripts, patient records or resident lists that identify real people.
- Do not paste credentials,
.envcontents or production database dumps. - Do not copy generated code you cannot explain line by line; the panel will ask.
- Do not use AI to fabricate survey results, respondent counts or evaluation scores.
- Do not hide AI use when your school or adviser requires you to disclose it.
A simple workflow that keeps you in control
- 01
Draft first
Write your own title, objectives, schema or paragraph before opening the assistant.
- 02
Ask for critique
Use a template above and ask for issues, options or questions rather than a replacement.
- 03
Verify
Check facts against primary sources, run the code, and test the edge cases yourself.
- 04
Decide as a team
Accept or reject each suggestion deliberately, and note why in your meeting minutes.
- 05
Disclose
Record which tool you used and for what, following your school's required format.
Next step
Pick one template above and use it on your current stage today, then write down what you kept and what you changed. If you still need a topic, start with the free capstone title generator and react to its ideas.