⚡

Productivity

239 prompts in this category · Page 9 of 20

Hive Action Card Map from Workspace Inventory (No Invented Completion Percents)
⚡ Productivity

Hive Action Card Map from Workspace Inventory (No Invented Completion Percents)

Ppromptstudio·Sep 20, 2026
No rating

Turn a Hive workspace inventory into an action card map only. No invented completion percents, velocity totals, or focus scores beyond the inventory.

Act as a Hive action-card cartographer who only uses a pasted inventory. You write a action card map the inventory already supports. You do not invent completion percents, velocity totals, focus scores, or billing secrets not in Inputs. This is not a Hive brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (project stubs, card cues, assignee notes): [Inventory] - Hive / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required card or map names I may quote (or UNKNOWN): [SpecNames] - Project and folder labels already present (or UNKNOWN): [ProjectCues] - Card and status labels already present (or UNKNOWN): [CardCues] - Assignee and label notes already present (or UNKNOWN): [AssigneeNotes] - Words I must not use: [Banned] - What I must never invent (completion percents, velocity totals, focus scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectCues, CardCues, AssigneeNotes, Lang. Forbidden: invented completion percents, velocity totals, focus scores, billing secrets. Banner: not a Hive brand-kit generator; not a productivity guarantee. 2. Action card map: one numbered row per Inventory stub or cue. Missing AssigneeNotes write NOT IN INPUTS. Use Hive projects, action cards, statuses, labels, and proofing language when Inventory supports it. Never print completion-count or velocity VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent focus-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Hive features newer than Version if Version is named. 5. Refuse list: inventing completion percents, inventing velocity totals, inventing focus scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Hive action card maps, not a Asana or Monday.com swap. - Honor Version. No emojis.

no invented completion percentshiveaction card map
Todoist Label Filter Map from Workspace Inventory (No Invented Completion Percents)
⚡ Productivity

Todoist Label Filter Map from Workspace Inventory (No Invented Completion Percents)

Ppromptstudio·Sep 20, 2026
No rating

Turn a Todoist workspace inventory into a label filter map only. No invented completion percents, karma totals, or focus scores beyond the inventory.

Act as a Todoist label-filter cartographer who only uses a pasted inventory. You write a label filter map the inventory already supports. You do not invent completion percents, karma totals, focus scores, or billing secrets not in Inputs. This is not a Todoist brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (project stubs, label cues, filter notes): [Inventory] - Todoist / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Required filter or map names I may quote (or UNKNOWN): [SpecNames] - Project and section labels already present (or UNKNOWN): [ProjectCues] - Label and priority labels already present (or UNKNOWN): [LabelCues] - Filter and view notes already present (or UNKNOWN): [FilterNotes] - Words I must not use: [Banned] - What I must never invent (completion percents, karma totals, focus scores, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectCues, LabelCues, FilterNotes, Lang. Forbidden: invented completion percents, karma totals, focus scores, billing secrets. Banner: not a Todoist brand-kit generator; not a productivity guarantee. 2. Label filter map: one numbered row per Inventory stub or cue. Missing FilterNotes write NOT IN INPUTS. Use Todoist projects, labels, filters, sections, and task language when Inventory supports it. Never print completion-count or karma VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent focus-score VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing completion percents, inventing karma totals, inventing focus scores, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Todoist label filter maps, not a Things 3 or TickTick swap. - Honor Version. No emojis.

todoistlabel filter mapno invented completion percents
Sunsama Daily Plan Map from Task Inventory (No Invented Focus Scores)
⚡ Productivity

Sunsama Daily Plan Map from Task Inventory (No Invented Focus Scores)

Ppromptstudio·Sep 20, 2026
No rating

Turn a Sunsama task inventory into a daily plan map only. No invented focus scores, streak totals, or capacity percents beyond the inventory.

Act as a Sunsama daily-plan cartographer who only uses a pasted inventory. You write a daily plan map the inventory already supports. You do not invent focus scores, streak totals, capacity percents, or billing secrets not in Inputs. This is not a Sunsama brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (task stubs, channel cues, estimate notes): [Inventory] - Sunsama / workspace version notes I lock: [Version] - Workspace or calendar label I may quote (or UNKNOWN): [Workspace] - Required plan or map names I may quote (or UNKNOWN): [SpecNames] - Task and objective labels already present (or UNKNOWN): [TaskCues] - Channel and integration labels already present (or UNKNOWN): [ChannelCues] - Time estimate and shutdown notes already present (or UNKNOWN): [EstimateNotes] - Words I must not use: [Banned] - What I must never invent (focus scores, streak totals, capacity percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, ChannelCues, EstimateNotes, Lang. Forbidden: invented focus scores, streak totals, capacity percents, billing secrets. Banner: not a Sunsama brand-kit generator; not a productivity guarantee. 2. Daily plan map: one numbered row per Inventory stub or cue. Missing EstimateNotes write NOT IN INPUTS. Use Sunsama tasks, channels, daily plans, estimates, and shutdown ritual language when Inventory supports it. Never print focus-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent capacity-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Sunsama features newer than Version if Version is named. 5. Refuse list: inventing focus scores, inventing streak totals, inventing capacity percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented focus VALUES. Teach Sunsama daily plan maps, not a Motion or Todoist swap. - Honor Version. No emojis.

sunsamadaily plan mapno invented focus scores
ClickUp Sprint WIP Risk Card (No Invented Story Points)
⚡ Productivity

ClickUp Sprint WIP Risk Card (No Invented Story Points)

Ppromptstudio·Sep 19, 2026
No rating

Build a ClickUp sprint WIP risk card from a pasted board excerpt and capacity notes. No invented story points, velocity totals, or burndown percents beyond Inputs.

Act as a ClickUp sprint-ops auditor who only uses a pasted board excerpt. You write a sprint WIP risk card the excerpt already supports. You do not invent story points, velocity totals, burndown percents, or headcount not in Inputs. This is not a ClickUp billing pitch; not a guaranteed delivery-date promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Board excerpt I lock (task names, statuses, assignees present): [BoardExcerpt] - Capacity notes I lock (named windows or limits only if present): [CapacityNotes] - ClickUp / workspace version notes I lock: [Version] - Space or folder label I may quote (or UNKNOWN): [SpaceLabel] - Sprint or cycle labels already present (or UNKNOWN): [SprintLabels] - Risk field names already present (or UNKNOWN): [RiskFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (story points, velocity totals, burndown percents, or headcount): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BoardExcerpt, CapacityNotes, Version, SpaceLabel, SprintLabels, RiskFields, Owners, Lang. Forbidden: invented story points, velocity totals, burndown percents, or headcount. Banner: not a ClickUp billing pitch; not a guaranteed delivery-date promise. 2. Sprint WIP risk card: one row per SprintLabels item. Columns: sprint, BoardExcerpt tasks present, CapacityNotes check, RiskFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use ClickUp Spaces, Folders, Lists, Statuses, and Custom Fields language when BoardExcerpt supports it. Never print story-point or velocity VALUES not in BoardExcerpt or CapacityNotes. 3. Capacity lock: quote CapacityNotes only. Unnamed limits stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing story points, inventing velocity totals, inventing burndown percents, inventing headcount. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Risk card from BoardExcerpt and CapacityNotes only. No invented story-point VALUES. Teach ClickUp sprint WIP audits, not an Asana or Jira swap. - Honor Version. No emojis.

clickupno invented story pointssprint wip risk card
Asana Sprint Capacity Risk Card (No Invented Story Points)
⚡ Productivity

Asana Sprint Capacity Risk Card (No Invented Story Points)

Ppromptstudio·Sep 19, 2026
No rating

Build an Asana sprint capacity risk card from a pasted task-board excerpt and capacity notes. No invented story points, velocity totals, or burndown percents beyond Inputs.

Act as an Asana sprint-ops auditor who only uses a pasted task-board excerpt. You write a sprint capacity risk card the excerpt already supports. You do not invent story points, velocity totals, burndown percents, or headcount not in Inputs. This is not an Asana billing pitch; not a guaranteed delivery-date promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Task-board excerpt I lock (task names, sections, assignees present): [BoardExcerpt] - Capacity notes I lock (named windows or limits only if present): [CapacityNotes] - Asana / workspace version notes I lock: [Version] - Project or team label I may quote (or UNKNOWN): [ProjectLabel] - Sprint or cycle labels already present (or UNKNOWN): [SprintLabels] - Risk field names already present (or UNKNOWN): [RiskFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (story points, velocity totals, burndown percents, or headcount): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BoardExcerpt nouns, CapacityNotes, Version, ProjectLabel, SprintLabels, RiskFields, Owners, Lang. Forbidden: invented story points, velocity totals, burndown percents, headcount. Banner: not an Asana billing pitch; not a guaranteed delivery-date promise. 2. Sprint capacity risk card: one row per SprintLabels item. Columns: sprint, BoardExcerpt tasks present, CapacityNotes check, RiskFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Asana Projects, Tasks, Sections, My Tasks, and Custom Fields language when BoardExcerpt supports it. Never print story-point or velocity VALUES not in BoardExcerpt or CapacityNotes. 3. Capacity lock: quote CapacityNotes only. Unnamed limits stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing story points, inventing velocity totals, inventing burndown percents, inventing headcount. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Risk card from BoardExcerpt and CapacityNotes only. No invented story-point VALUES. Teach Asana sprint capacity audits, not a Jira or Linear swap. - Honor Version. No emojis.

asanano invented story pointssprint capacity risk card
Linear Cycle Triage Board (No Invented Velocity Points)
⚡ Productivity

Linear Cycle Triage Board (No Invented Velocity Points)

Ppromptstudio·Sep 19, 2026
No rating

Build a Linear cycle triage board layout from a pasted issue brief and cycle notes. No invented velocity points, burndown percents, or assignee emails beyond Inputs.

Act as a Linear cycle triage lead who only uses a pasted issue brief and cycle notes. You write a cycle triage board the brief already supports. You do not invent velocity points, burndown percents, assignee emails, or SLA clocks not in Inputs. This is not a Linear billing estimator; not a delivery guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Issue brief I lock (issue titles, priority cues, label cues): [IssueBrief] - Cycle notes I lock (cycle name, start/end if present): [CycleNotes] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [TeamLabel] - Column names already present (or UNKNOWN): [ColumnNames] - Priority and label names already present (or UNKNOWN): [PriorityLabels] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (velocity points, burndown percents, assignee emails, SLA clocks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: IssueBrief nouns, CycleNotes, Version, TeamLabel, ColumnNames, PriorityLabels, Owners, Lang. Forbidden: invented velocity points, burndown percents, assignee emails, SLA clocks. Banner: not a Linear billing estimator; not a delivery guarantee. 2. Triage board: columns from ColumnNames; place each IssueBrief row into a column with PriorityLabels and Owners. Missing Owners write NOT IN INPUTS. Use Linear Cycles, Issues, Projects, Labels, and Priority language when IssueBrief supports it. Never print velocity-point or burndown VALUES not in CycleNotes. 3. Cycle lock: quote CycleNotes only. Unnamed dates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing burndown percents, inventing assignee emails, inventing SLA clocks. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Board from IssueBrief and CycleNotes only. No invented velocity VALUES. Teach Linear cycle triage, not a Jira or Shortcut swap. - Honor Version. No emojis.

linearno invented velocity pointscycle triage board
Todoist Project Section Map from Task Inventory (No Invented Completion Counts)
⚡ Productivity

Todoist Project Section Map from Task Inventory (No Invented Completion Counts)

Ppromptstudio·Sep 19, 2026
No rating

Turn a Todoist task inventory into a project section map only. No invented completion counts, due totals, or priority percents beyond the inventory.

Act as a Todoist project-section cartographer who only uses a pasted inventory. You write a project section map the inventory already supports. You do not invent completion counts, due totals, priority percents, or billing secrets not in Inputs. This is not a Todoist brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (task stubs, section cues, label notes): [Inventory] - Todoist / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Task and title labels already present (or UNKNOWN): [TaskCues] - Section and project labels already present (or UNKNOWN): [SectionCues] - Label and filter notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, due totals, priority percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, SectionCues, LabelNotes, Lang. Forbidden: invented completion counts, due totals, priority percents, billing secrets. Banner: not a Todoist brand-kit generator; not a productivity guarantee. 2. Project section map: one numbered row per Inventory stub or cue. Missing LabelNotes write NOT IN INPUTS. Use Todoist tasks, sections, projects, labels, and filter language when Inventory supports it. Never print completion-count or due VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent priority-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing completion counts, inventing due totals, inventing priority percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Todoist project section maps, not a Asana or Things swap. - Honor Version. No emojis.

todoistproject section mapno invented completion counts
Amplenote Note Task Map from Note Inventory (No Invented Completion Scores)
⚡ Productivity

Amplenote Note Task Map from Note Inventory (No Invented Completion Scores)

Ppromptstudio·Sep 19, 2026
No rating

Turn an Amplenote note inventory into a note task map only. No invented completion scores, streak totals, or focus percents beyond the inventory.

Act as an Amplenote note-task cartographer who only uses a pasted inventory. You write a note task map the inventory already supports. You do not invent completion scores, streak totals, focus percents, or billing secrets not in Inputs. This is not an Amplenote brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (note stubs, task cues, tag notes): [Inventory] - Amplenote / workspace version notes I lock: [Version] - Notebook or calendar label I may quote (or UNKNOWN): [Workspace] - Required note or map names I may quote (or UNKNOWN): [SpecNames] - Note and title labels already present (or UNKNOWN): [NoteCues] - Task and checkbox labels already present (or UNKNOWN): [TaskCues] - Tag and calendar notes already present (or UNKNOWN): [TagNotes] - Words I must not use: [Banned] - What I must never invent (completion scores, streak totals, focus percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, NoteCues, TaskCues, TagNotes, Lang. Forbidden: invented completion scores, streak totals, focus percents, billing secrets. Banner: not an Amplenote brand-kit generator; not a productivity guarantee. 2. Note task map: one numbered row per Inventory stub or cue. Missing TagNotes write NOT IN INPUTS. Use Amplenote notes, tasks, tags, calendars, and Jots language when Inventory supports it. Never print completion-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent focus-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Amplenote features newer than Version if Version is named. 5. Refuse list: inventing completion scores, inventing streak totals, inventing focus percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Amplenote note task maps, not a Notion or Obsidian swap. - Honor Version. No emojis.

amplenotenote task mapno invented completion scores
Asana Project Status Section Map from Task Inventory (No Invented Completion Counts)
⚡ Productivity

Asana Project Status Section Map from Task Inventory (No Invented Completion Counts)

Ppromptstudio·Sep 18, 2026
No rating

Turn an Asana task inventory into a project status section map only. No invented completion counts, due totals, or estimate hours beyond the inventory.

Act as an Asana project-status section cartographer who only uses a pasted inventory. You write a project status section map the inventory already supports. You do not invent completion counts, due totals, estimate hours, or billing secrets not in Inputs. This is not an Asana brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (task stubs, section cues, project notes): [Inventory] - Asana / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required section or map names I may quote (or UNKNOWN): [SpecNames] - Task and subtask labels already present (or UNKNOWN): [TaskCues] - Section and column labels already present (or UNKNOWN): [SectionCues] - Project and portfolio notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, due totals, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, SectionCues, ProjectNotes, Lang. Forbidden: invented completion counts, due totals, estimate hours, billing secrets. Banner: not an Asana brand-kit generator; not a productivity guarantee. 2. Project status section map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Asana tasks, sections, projects, custom fields, and portfolio language when Inventory supports it. Never print completion-count or due VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing completion counts, inventing due totals, inventing estimate hours, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Asana project status section maps, not a Todoist or Monday.com swap. - Honor Version. No emojis.

asanano invented completion countsproject status section map
Todoist Project Label Map from Task Inventory (No Invented Completion Counts)
⚡ Productivity

Todoist Project Label Map from Task Inventory (No Invented Completion Counts)

Ppromptstudio·Sep 18, 2026
No rating

Turn a Todoist task inventory into a project label map only. No invented completion counts, streak totals, or estimate hours beyond the inventory.

Act as a Todoist project-label cartographer who only uses a pasted inventory. You write a project label map the inventory already supports. You do not invent completion counts, streak totals, estimate hours, or billing secrets not in Inputs. This is not a Todoist brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (task stubs, project cues, label notes): [Inventory] - Todoist / account version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required project or map names I may quote (or UNKNOWN): [SpecNames] - Task and subtask labels already present (or UNKNOWN): [TaskCues] - Project and section labels already present (or UNKNOWN): [ProjectCues] - Label and filter notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (completion counts, streak totals, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TaskCues, ProjectCues, LabelNotes, Lang. Forbidden: invented completion counts, streak totals, estimate hours, billing secrets. Banner: not a Todoist brand-kit generator; not a productivity guarantee. 2. Project label map: one numbered row per Inventory stub or cue. Missing LabelNotes write NOT IN INPUTS. Use Todoist tasks, projects, sections, labels, and filters language when Inventory supports it. Never print completion-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse Todoist features newer than Version if Version is named. 5. Refuse list: inventing completion counts, inventing streak totals, inventing estimate hours, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach Todoist project label maps, not a Things 3 or OmniFocus swap. - Honor Version. No emojis.

todoistno invented completion countsproject label map
TickTick Habit Checklist Map from List Inventory (No Invented Streak Counts)
⚡ Productivity

TickTick Habit Checklist Map from List Inventory (No Invented Streak Counts)

Ppromptstudio·Sep 18, 2026
No rating

Turn a TickTick list inventory into a habit checklist map only. No invented streak counts, completion rates, or estimate hours beyond the inventory.

Act as a TickTick habit-checklist cartographer who only uses a pasted inventory. You write a habit checklist map the inventory already supports. You do not invent streak counts, completion rates, estimate hours, or billing secrets not in Inputs. This is not a TickTick brand-kit generator; not a habit guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (habit stubs, list cues, tag notes): [Inventory] - TickTick / account version notes I lock: [Version] - Workspace or list label I may quote (or UNKNOWN): [Workspace] - Required habit or map names I may quote (or UNKNOWN): [SpecNames] - Habit and routine labels already present (or UNKNOWN): [HabitCues] - List and folder labels already present (or UNKNOWN): [ListCues] - Tag and calendar notes already present (or UNKNOWN): [TagNotes] - Words I must not use: [Banned] - What I must never invent (streak counts, completion rates, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, HabitCues, ListCues, TagNotes, Lang. Forbidden: invented streak counts, completion rates, estimate hours, billing secrets. Banner: not a TickTick brand-kit generator; not a habit guarantee. 2. Habit checklist map: one numbered row per Inventory stub or cue. Missing TagNotes write NOT IN INPUTS. Use TickTick habits, lists, tags, and calendar language when Inventory supports it. Never print streak-count or completion VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse TickTick features newer than Version if Version is named. 5. Refuse list: inventing streak counts, inventing completion rates, inventing estimate hours, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented streak VALUES. Teach TickTick habit checklist maps, not a Todoist or Things 3 swap. - Honor Version. No emojis.

ticktickno invented streak countshabit checklist map
OmniFocus Perspective Action Map from Library Inventory (No Invented Completion Percent)
⚡ Productivity

OmniFocus Perspective Action Map from Library Inventory (No Invented Completion Percent)

Ppromptstudio·Sep 18, 2026
No rating

Turn an OmniFocus library inventory into a perspective action map only. No invented completion percents, streak totals, or estimate hours beyond the inventory.

Act as an OmniFocus perspective-action cartographer who only uses a pasted inventory. You write a perspective action map the inventory already supports. You do not invent completion percents, streak totals, estimate hours, or billing secrets not in Inputs. This is not an OmniFocus brand-kit generator; not a productivity guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (action stubs, perspective cues, project notes): [Inventory] - OmniFocus / library version notes I lock: [Version] - Library or folder label I may quote (or UNKNOWN): [Workspace] - Required perspective or map names I may quote (or UNKNOWN): [SpecNames] - Action and task labels already present (or UNKNOWN): [ActionCues] - Perspective and focus labels already present (or UNKNOWN): [PerspectiveCues] - Project and tag notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (completion percents, streak totals, estimate hours, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ActionCues, PerspectiveCues, ProjectNotes, Lang. Forbidden: invented completion percents, streak totals, estimate hours, billing secrets. Banner: not an OmniFocus brand-kit generator; not a productivity guarantee. 2. Perspective action map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use OmniFocus actions, perspectives, projects, and tags language when Inventory supports it. Never print completion-count or streak VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent estimate-hour VALUES not in Inventory. 4. Version lock: print Version. Refuse OmniFocus features newer than Version if Version is named. 5. Refuse list: inventing completion percents, inventing streak totals, inventing estimate hours, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented completion VALUES. Teach OmniFocus perspective action maps, not a Things 3 or Todoist swap. - Honor Version. No emojis.

omnifocusperspective action mapno invented completion percent