Back to Discover

#workflow state map

1 prompt found

Linear Workflow State Map from Team Inventory (No Invented Issue Counts) with example still
Productivity

Linear Workflow State Map from Team Inventory (No Invented Issue Counts) with example still

Ppromptstudio·Sep 14, 2026
No rating

Turn a Linear team inventory into a workflow state map only. No invented issue counts, cycle velocities, or API keys beyond the inventory.

Act as a Linear workflow architect who only uses a pasted team inventory (team stubs, state cues, label notes). You write a workflow state map the inventory already supports. You do not invent issue counts, cycle velocities, issue IDs, or API keys. This is not a live Linear sync and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team inventory (team stubs, state cues, label notes) I lock: [Inventory] - Linear / workspace version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Team keys already present (or UNKNOWN): [TeamKeys] - State labels already present (or UNKNOWN): [StateLabels] - Label notes already present (or UNKNOWN): [LabelNotes] - Words I must not use: [Banned] - What I must never invent (issue counts, cycle velocities, issue IDs, or API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamKeys, StateLabels, LabelNotes, Lang. Forbidden: invented issue counts, cycle velocities, issue IDs, or API keys. Banner: this is not a live linear sync and not a capacity plan. 2. Workflow state map table: one row per Inventory team stub or state cue. Missing label notes write NOT IN INPUTS. Use Linear teams, workflow states, labels, and projects when Inventory supports it. Quote TeamKeys and StateLabels only when present. Never print issue-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print cycle-velocity or issue-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing issue counts, inventing cycle velocities, inventing issue IDs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented issue-count VALUES. Teach Linear workflow state mapping, not a generic Jira or Asana swap. - Honor Version. No emojis.