# The 5-Part Prompt Skeleton I Use For Every Serious Task

> Role, context, task, constraints, output format — in that order, every time.

- **Author:** [Aarav Sharma (@aarav_sharma)](https://www.promptabide.com/aarav_sharma)
- **Published:** 2025-12-27
- **Updated:** 2026-08-22
- **Tags:** `prompt-engineering`, `workflow`, `productivity`
- **Views:** 4072
- **Likes:** 79

## Prompt

```
After a year of daily use I stopped writing prompts freehand. Everything now goes through the same five blocks:

**1. Role** — "You are a senior Postgres DBA reviewing a production migration."
**2. Context** — the schema, the traffic shape, what already failed.
**3. Task** — one sentence, one verb. Not three tasks bundled together.
**4. Constraints** — "No downtime. Postgres 14. Must be reversible."
**5. Output format** — "Return a numbered plan, then the SQL, then the rollback SQL."

The block that people skip is #5, and it is the one that does the most work. Without it you get prose you then have to reformat by hand. With it you get something you can paste straight into a runbook.

One more rule: if the answer comes back wrong, do not argue with it in a follow-up. Edit the original prompt and re-run. Arguing compounds the confusion; editing removes it.
```

## Output

*Produced by Claude · claude-opus-4.*

```
**Migration plan**
1. Add the new nullable column in a separate transaction.
2. Backfill in batches of 5,000 rows with a sleep between batches.
3. Add the NOT NULL constraint as NOT VALID, then VALIDATE separately.

**SQL**
ALTER TABLE orders ADD COLUMN currency text;
...

**Rollback**
ALTER TABLE orders DROP COLUMN currency;
```

---

Canonical HTML: https://www.promptabide.com/bides/five-part-prompt-skeleton-aarav-sharma-1
Agent guide: https://www.promptabide.com/llms.txt · https://www.promptabide.com/agent-instructions.md
Sitemap: https://www.promptabide.com/sitemap.xml