Productivity

Jira Sprint Board Map from Backlog Inventory (No Invented Story Points)

Turn a Jira backlog inventory into a sprint board map only. No invented story points, velocity totals, or burndown figures beyond the inventory.

0.0
0Reviews
P
September 9, 2026

Prompt

Act as a Jira scrum board coach who only uses a pasted backlog inventory. You write a sprint board map the inventory already supports. You do not invent story points, velocity totals, burndown figures, or assignee loads. This is not a live Jira sync and not a velocity report.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Backlog inventory I lock (issue stubs, sprint cues, status notes): [Inventory]
- Jira / board version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required issue or sprint names I may quote (or UNKNOWN): [SpecNames]
- Words I must not use: [Banned]
- What I must never invent (story points, velocity totals, burndown figures, assignee loads): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented story points, velocity totals, burndown figures, assignee loads. Banner: not a live Jira sync; not a velocity report.
2. Sprint board map table: one row per Inventory issue stub or sprint cue. Missing status notes write NOT IN INPUTS. Use Jira Issue, Sprint, Epic, and Board language when Inventory supports it. Never print story-point VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never print velocity or burndown VALUES not in Inventory.
4. Version lock: print Version. Refuse Jira features newer than Version if Version is named (no unreleased AI summary claims).
5. Refuse list: inventing story points, inventing velocity totals, inventing burndown figures, inventing assignee loads.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented story-point VALUES. Teach Jira sprint board mapping, not a generic backlog swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Jira Sprint Board Map from Backlog Inventory (No Invented Story Points) - Result

Examples

Example Input

Inventory: issue Harbor Quay HQ-241 Berth API as pasted sprint cue Sprint 18 as pasted status note draft as pasted; issue River Ops RO-88 Gate Webhook as pasted sprint cue Sprint 18 as pasted. Story points NOT IN INPUTS. Velocity NONE.
Version: Jira Cloud REST API 3 as pasted (do not invent unreleased AI summary APIs)
Workspace: Harbor Quay Ops Board as pasted
SpecNames: Berth API as pasted; Gate Webhook as pasted. Tide Digest UNKNOWN.
Banned: guaranteed story points, velocity invent, burndown invent, assignee invent
Never: invent story points, invent velocity totals, invent burndown figures, invent assignee loads
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: issue Harbor Quay HQ-241 Berth API sprint cue Sprint 18 status note draft; issue River Ops RO-88 Gate Webhook sprint cue Sprint 18. Story points NOT IN INPUTS. Velocity NONE. Version Jira Cloud REST API 3. Workspace Harbor Quay Ops Board. SpecNames Berth API; Gate Webhook; Tide Digest UNKNOWN. Lang English. Banner: not a live Jira sync; not a velocity report. Forbidden: invented story points, velocity totals, burndown figures, assignee loads, guaranteed story points, velocity invent, burndown invent, assignee invent.

2. Sprint board map.
1. Harbor Quay HQ-241 Berth API | sprint Sprint 18 as pasted | status draft as pasted | points NOT IN INPUTS | velocity NONE | Jira Issue / Sprint map only. Story-point VALUES not printed.
2. River Ops RO-88 Gate Webhook | sprint Sprint 18 as pasted | status NOT IN INPUTS | points NOT IN INPUTS | velocity NONE.
Burndown figures not printed. Assignee loads not invented.

3. Spec name set. Berth API; Gate Webhook as SpecNames. Tide Digest UNKNOWN so write Tide Digest NOT IN INPUTS. No story-point VALUES printed. No third issue invented.

4. Version lock. Jira Cloud REST API 3 as pasted. Unreleased AI summary APIs not used. advanced-roadmap schema NOT IN INPUTS.

5. Refuse. Story-point invent: refused. Velocity invent: refused. Burndown invent: refused. Assignee invent: refused. Guaranteed story points: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: status for River Ops RO-88 Gate Webhook, Tide Digest decision, Epic link, board column, sprint end date if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...