Back to Discover

#sprint board map

2 prompts found

ClickUp Sprint Board Map from Task Inventory (No Invented Velocity Points)
⚡ Productivity

ClickUp Sprint Board Map from Task Inventory (No Invented Velocity Points)

Ppromptstudio·Sep 16, 2026
No rating

Turn a ClickUp task inventory into a sprint board map only. No invented velocity points, completion rates, or estimate hours beyond the inventory.

Act as a ClickUp sprint cartographer who only uses a pasted task inventory. You write a sprint board map the inventory already supports. You do not invent velocity points, completion rates, estimate hours, or burndown totals not in Inputs. This is not a ClickUp billing estimate and not a performance review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Task inventory I lock (card stubs, status cues, sprint notes): [Inventory] - ClickUp / workspace version notes I lock: [Version] - Space or folder label I may quote (or UNKNOWN): [Workspace] - Required sprint or board names I may quote (or UNKNOWN): [SpecNames] - Task titles already present (or UNKNOWN): [TaskCues] - Status labels already present (or UNKNOWN): [StatusCues] - Sprint and assignee notes already present (or UNKNOWN): [SprintNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, completion rates, estimate hours, burndown totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, StatusCues, SprintNotes, Lang. Forbidden: invented velocity points, completion rates, estimate hours, burndown totals. Banner: not a ClickUp billing estimate; not a performance review. 2. Sprint board map: one numbered row per Inventory card stub or status cue. Missing SprintNotes write NOT IN INPUTS. Use ClickUp Lists, Boards, Statuses, Custom Fields, Sprints, and Goals language when Inventory supports it. Never print velocity-point or completion-rate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed boards stay NOT IN INPUTS. Never invent estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing completion rates, inventing estimate hours, inventing burndown totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity-point VALUES. Teach ClickUp sprint boards, not an Asana or Todoist swap. - Honor Version. No emojis.

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

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

Ppromptstudio·Sep 9, 2026
No rating

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

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.