How to Use: Things 3 Area Project Map from List Inventory (No Invented Completion Counts)

You pasted a messy Things 3 list inventory and need a clean deliverable without invented numbers. This PromptDig prompt turns only what you already listed into a structured map or checklist for area and project handoffs.

What this prompt does

It locks your inventory, version, workspace label, and domain fields, then builds a ledger plus a table that refuses fake metrics. Missing cells stay NOT IN INPUTS instead of guessing.

Use it when you already have real stubs from Things 3 and want a teachable map for this job, not a generic template swap from another vendor. The Generate steps name Things 3 nouns on purpose so a title swap into another category would fail the swap-title test.

The deliverable is aimed at Things 3 area maps. Reviewers should see Inventory nouns echoed in the table rows, not marketing fluff. Cap style limits stay soft unless you add them later in Extra.

How to fill the brackets

1. Paste your Inventory with concrete nouns only. Prefer two labeled rows so the example shape stays visible after you swap names.
2. Lock Version to what you actually run. If you do not know the version, write unknown rather than guessing a marketing release name.
3. Quote Workspace and SpecNames when known; otherwise UNKNOWN.
4. Fill the three domain fields shown in the prompt. Leave UNKNOWN cells alone instead of inventing polish.
5. List Banned words and Never invent rules that match the risks in your org wiki.

Keep Harbor Quay and River Ops out of your production paste. Those labels exist only so the example_input shows two inventory rows. Replace them with your real area names, project titles, or heading folders before you run the prompt.

Example shape

The included example_input uses Harbor Quay and River Ops labels so you can see how two inventory rows become a checklist without inventing metrics. Swap those labels for your own before you run it. Keep Cap style limits if you add any later. Prefer a short second pass that only reorders rows over asking for a longer rewrite that invents missing fields.

When the model returns the map, check that every row cites an Inventory noun. If a row invents completion counts, deadline totals, or tag frequencies, quote the Never line and re-run. A clean map with two honest rows beats a long table full of guesses.

Why the honesty rules matter

Teams lose trust when a model invents completion counts, deadline totals, or tag frequencies. This prompt quotes Banned and Never hits, then cuts them. An honesty ledger at the top makes the refuse list easy to audit in code review or design critique.

If a teammate asks for a number that was never in the paste, the correct answer is NOT IN INPUTS plus a gaps bullet. That habit keeps area and project handoffs accurate when the inventory is incomplete.

Honesty also protects you from soft plagiarism of vendor marketing pages. The prompt refuses testimonials, star ratings, and press logos that were never in Inputs. Your wiki stays a map of what you pasted, not a brochure.

Step by step run

Copy the prompt into ChatGPT, Claude, or Gemini. Replace every bracket with your locked values. Run once, then check the honesty ledger against your paste.

If the output invents a metric, paste the Never line again and ask for a rewrite that only uses Inventory nouns. Keep the Format you locked so the checklist stays reviewable.

When you are ready for more maps like this one, open the live prompt on PromptDig, then Browse more prompts or Share a prompt with your team.

Live prompt: Things 3 Area Project Map from List Inventory (No Invented Completion Counts)