Database
Add structured storage when files no longer fit the job.
When this is worth adding
Repeated queries, relationships or data volume exceed a simple file list.
First complete a useful task and a fresh restart in your existing folder. Keep the same team and add only the capability this problem needs.
Plan it with your team
Open your existing team project and paste this prompt. It produces a proposal for review.
Help me decide whether this workflow needs a database. Ask what records, queries and relationships we need, and compare a simple file or spreadsheet approach first. Use synthetic examples. If a database is justified, propose ownership, storage, backup and restore, access controls and a migration plan. Keep one authoritative source for each fact. Stop at a reviewable design before provisioning or importing real data.If copying is blocked, select the text and copy it manually.
What you should have
A bounded proposal with selected inputs, an output, ownership, permitted tools and acceptance checks. Planning only. No database, credentials or migration is created.
Checks before relying on it
- Prove the required queries on synthetic records.
- Test backup restoration and ownership of updates.
- Verify access and storage before importing sensitive records.
Record actual results, limitations and anything not run. Add execution instructions only after the intended tool and access are verified.
Return to your work
Continue in your existing team or choose another topic. There is no need to rebuild the team.