PriorityDesk — the spec

An internal dashboard where Ryan's team sees, owns, and updates the things that matter most right now. It replaces the scattered state of priorities across Jira, Linear, and wherever else work lives, pulling everything into one authoritative view where the lead or team consensus sets the stack rank and everyone can act on it without a meeting.

---

Decisions locked

---

The core loop

1. A team member opens PriorityDesk and sees the ranked priority list for today, ordered by lead decision or team consensus score.
2. They find their owned items and flip a status toggle — Not Started, In Progress, or Blocked.
3. If a task is blocked, they flag the dependency that is causing it, which surfaces visually on the board.
4. The lead reviews the ranked list, adjusts consensus weights or manually re-ranks if the situation has shifted, and confirms the order.
5. At the end of the week, the team opens the Weekly Review template, walks through what moved and what didn't, then archives the snapshot and resets for the next cycle.

---

v1 scope

Real-time priority ranking — The ranked list is computed from lead input or team consensus scores and updates immediately when either changes. Lives on the main Dashboard screen; the current top ten are always visible above the fold.

Quick status toggle — Every priority row shows a three-state toggle: Not Started / In Progress / Blocked. One click updates the record and timestamps the change. Lives inline on the Dashboard and the detail card.

Owner assignment and dependency mapping — Each task has a single owner and an optional list of blocking tasks. Blocked items render a dependency indicator so the team can see what is gating what at a glance. Lives on the task detail card and is summarised on the Dashboard.

Bulk import from Jira and Linear — A one-time or recurring import pulls tasks from connected Jira projects or Linear teams via their APIs. Field mapping is configurable. Lives on the Integrations settings screen so it does not crowd the main flow.

Weekly priority review template and archive — A structured one-page review form captures what shipped, what moved, and what stays top of stack. Submitting it archives the week's ranked snapshot. Archived snapshots are browsable on the History screen.

---

Deliberately later

• Priority-change feed with timestamps and reasons — useful once the team has enough history to make the audit trail meaningful; noisy in week one.
• Slack notifications for new blockers or top-rank shifts — high value but requires the team to have settled on which signals actually warrant interruption; ship after the core process is stable.
• Drag-to-reorder interface — fast for power users, but consensus scoring and lead overrides cover the v1 ranking need without the interaction complexity.

---

Data model sketch

• users — id, name, email, role (lead / member)
• priorities — id, title, description, rank, status (not_started / in_progress / blocked), owner_id, created_at, updated_at
• dependencies — id, blocking_priority_id, blocked_priority_id
• consensus_votes — id, priority_id, user_id, score, cast_at
• imports — id, source (jira / linear), config_json, last_run_at, status
• weekly_reviews — id, week_start_date, summary_json, archived_at
• priority_snapshots — id, weekly_review_id, priority_id, rank_at_archive, status_at_archive

---

Screens

• Dashboard — ranked priority list for today with inline status toggles and owner labels; the team's home base.
• Task Detail Card — full view of a single priority: description, owner, status, dependency list, history of status changes.
• Weekly Review — structured form for the end-of-week process; submitting archives the current snapshot.
• History — browsable archive of past weekly snapshots ranked exactly as they were.
• Integrations — configure Jira and Linear connections, field mapping, and import schedule.
• Team Settings — manage users, roles, and who has lead-level ranking authority.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build PriorityDesk with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
• Keep it as the single source of truth while you build, so every feature decision has a reference point that the whole team has seen.