30 Claude Prompts That Build Kanban Boards

You are a productivity coach who teaches Getting Things Done. <context> I need a personal GTD kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to run my whole life from one board. </context> <inputs> - My main roles: [E.G. WORK, SIDE PROJECT, HOME, HEALTH] - Columns: [E.G. INBOX, TODAY, THIS WEEK, WAITING FOR, DONE] - Sample tasks to seed: [6-10 REAL TASKS FROM MY LIFE] - Context tags: [E.G. @COMPUTER, @CALLS, @ERRANDS] - Card fields: [E.G. CONTEXT, ENERGY LEVEL, DUE DATE] </inputs> <task> Build a board where each task card shows a title, a context tag, an energy-level chip (low/medium/high), and an optional due date, with per-column counts. Make cards draggable, persist to localStorage, add a context filter, and give the Today column a visible cap that warns when I add more than a set number of tasks. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Today WIP cap must trigger a visible warning; drag, filter, counts functional. - Seed with realistic personal tasks across roles, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the WIP-cap logic and how to add a weekly-review reset button. </format>

You are a personal productivity strategist who runs a weekly review ritual. <context> I need a weekly planning kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in from my real inputs. </context> <inputs> - This week's top goals: [1-3 OUTCOMES THAT MATTER MOST] - Columns: [E.G. THIS WEEK, MONDAY, TUESDAY... , DONE OR BY-DAY LANES] - Recurring commitments: [MEETINGS, HABITS, CHORES] - Loose tasks to schedule: [6-12 THINGS ON MY MIND] - Card fields: [E.G. PRIORITY, TIME ESTIMATE, LINKED GOAL] </inputs> <task> Produce a board spec that turns my dump of tasks into a planned week. Distribute the loose tasks across day lanes, each card carrying a priority, a time estimate, and which top goal it advances. Balance the load so no single day is overstuffed, protect time for the top goals, and note any tasks that should be dropped or delegated. </task> <constraints> - Output clean markdown: a lane per day, cards as sub-bullets or a table, plus a short "cut or delegate" list, no filler. - Every card should link to a goal or be flagged as maintenance; realistic time estimates. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a short note on how to run this as a repeatable Sunday planning session. </format>

You are a behavior-change coach who builds simple, sticky trackers. <context> I need a habit-and-goal kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to track habits and the goals they ladder up to. </context> <inputs> - Goals for this quarter: [2-4 OUTCOMES] - Columns: [E.G. TO BUILD, BUILDING, CONSISTENT, PAUSED] - Habits to seed: [5-8 HABITS TIED TO THE GOALS] - Cadence per habit: [DAILY / WEEKLY] - Card fields: [E.G. LINKED GOAL, STREAK COUNT, CADENCE] </inputs> <task> Build a board where each habit card shows the habit, its cadence, the goal it supports, and a streak counter with a plus button that increments the streak. Make cards draggable between columns, persist streaks and positions to localStorage, and visually celebrate any card whose streak crosses a milestone (e.g. 7 or 30). </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Streak increment and milestone highlight must actually work and persist; drag functional. - Seed with realistic habits tied to the stated goals, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the streak and milestone logic and how to add a daily reset. </format>

You are a career coach who helps people run an organized job search. <context> I need a job-search kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to track every application from lead to offer. </context> <inputs> - Target roles and industry: [WHAT I AM APPLYING FOR] - Columns: [E.G. LEADS, APPLIED, SCREENING, INTERVIEWING, OFFER, REJECTED] - Sample applications to seed: [5-8 REAL COMPANIES OR ROLES] - Priority tiers: [E.G. DREAM, STRONG FIT, BACKUP] - Card fields: [E.G. COMPANY, ROLE, NEXT STEP, DATE APPLIED] </inputs> <task> Build a board where each application card shows the company, role, a priority-tier pill, the next action, and the date applied, with per-column counts. Make cards draggable, persist to localStorage, add a priority filter, and flag any card sitting in a stage for more than 10 days with no next-step date so nothing goes stale. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Staleness flag compares real dates; drag, filter, counts functional. - Seed with realistic company and role names, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the staleness logic and how to add a notes field for interview prep. </format>

You are a project coordinator who manages home renovation projects. <context> I need a home-renovation kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in for a real project. </context> <inputs> - Project scope: [E.G. KITCHEN REMODEL, WHOLE-HOUSE REFRESH] - Rooms or zones: [WHICH SPACES] - Columns: [E.G. TO PLAN, QUOTES, SCHEDULED, IN PROGRESS, DONE] - Budget ceiling: [TOTAL BUDGET] - Card fields: [E.G. ROOM, VENDOR, COST ESTIMATE, TARGET DATE] </inputs> <task> Produce a board spec with the columns above. Seed 8-12 realistic renovation tasks across rooms and columns, each card carrying a room tag, a vendor or DIY note, a cost estimate, and a target date. Add a running budget tally that sums the cost estimates and flags if the total exceeds the ceiling, plus a note on the dependency order (e.g. plumbing before tiling). </task> <constraints> - Output clean markdown: heading per column, cards as a table with cost estimates, plus a budget summary line, no filler. - Tasks must be realistic and sequenced sensibly; estimates believable. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a note on how to track actual-vs-estimate spend per card. </format>

You are a sales operations leader who runs a clean deal pipeline. <context> I need a sales pipeline kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to move deals from lead to closed. </context> <inputs> - What we sell and to whom: [PRODUCT AND ICP] - Stages / columns: [E.G. LEAD, QUALIFIED, PROPOSAL, NEGOTIATION, WON, LOST] - Sample deals to seed: [6-10 REAL DEALS] - Deal-size tiers: [E.G. SMB, MID, ENTERPRISE] - Card fields: [E.G. COMPANY, VALUE, OWNER, NEXT STEP] </inputs> <task> Build a board where each deal card shows the company, a deal value, a size-tier pill, an owner, and the next step, with per-column counts and a live sum of deal value at the top of each stage. Make cards draggable, persist to localStorage, add an owner filter, and show total weighted pipeline value using a simple probability per stage. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Per-stage value sums and weighted total must compute correctly; drag, filter, counts functional. - Seed with realistic company names and deal values, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the stage-probability weighting and how to sync deals from a CRM. </format>

You are a sales development leader building an outbound prospecting board. <context> I need an SDR outbound kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in for a prospecting sprint. </context> <inputs> - Target segment: [WHO WE PROSPECT] - Columns: [E.G. TO RESEARCH, SEQUENCED, ENGAGED, MEETING BOOKED, HANDED OFF] - Sample prospects to seed: [6-10 COMPANIES OR PERSONAS] - Sequence steps: [E.G. EMAIL 1, LINKEDIN, CALL, EMAIL 2] - Card fields: [E.G. COMPANY, CONTACT, LAST TOUCH, NEXT TOUCH DATE] </inputs> <task> Produce a board spec with the columns above. Seed 6-10 realistic prospect cards across columns, each carrying a company, a contact and title, the last touch made, and the next-touch date. Under each Sequenced card, list the remaining sequence steps as a checklist, and add a daily activity target (dials, emails) at the top of the board. </task> <constraints> - Output clean markdown: heading per column, cards as a table, sequence checklists, and an activity-target header, no filler. - Prospects and cadence must be realistic; next-touch dates believable. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a note on how to reset it for a fresh prospecting sprint each week. </format>

You are a business development lead managing partnership deals. <context> I need a partnership pipeline kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to track partner deals from first contact to launched. </context> <inputs> - Partnership type: [E.G. INTEGRATIONS, RESELLERS, CO-MARKETING] - Columns: [E.G. PROSPECTING, INTRO CALL, EVALUATING, AGREEMENT, LAUNCHED] - Sample partners to seed: [5-8 REAL PARTNER NAMES] - Partner tiers: [E.G. STRATEGIC, GROWTH, LONG-TAIL] - Card fields: [E.G. PARTNER, OWNER, POTENTIAL VALUE, NEXT STEP] </inputs> <task> Build a board where each partner card shows the partner name, a tier pill, an owner, a potential-value estimate, and the next step, with per-column counts. Make cards draggable, persist to localStorage, add a tier filter, and flag any card with no next step defined so no partnership stalls silently. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Missing-next-step flag must work; drag, filter, counts functional. - Seed with realistic partner names and value estimates, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the tier color system and how to add an agreement-status field. </format>

You are a customer success leader running renewals and expansion. <context> I need a renewals-and-upsell kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in for my account base. </context> <inputs> - Product and segment: [WHAT WE SELL AND TO WHOM] - Columns: [E.G. UPCOMING, AT RISK, IN CONVERSATION, RENEWED, EXPANDED, CHURNED] - Sample accounts to seed: [6-10 ACCOUNTS] - Health signals: [E.G. USAGE, NPS, SUPPORT TICKETS] - Card fields: [E.G. ACCOUNT, ARR, RENEWAL DATE, HEALTH, OWNER] </inputs> <task> Produce a board spec with the columns above. Seed 6-10 realistic account cards across columns, each carrying ARR, a renewal date, a health rating (green/yellow/red), an upsell opportunity, and an owner. Sort the At Risk column by renewal date, add a total-ARR-at-risk tally, and note the recommended play for each at-risk account. </task> <constraints> - Output clean markdown: heading per column, cards as a table, an ARR-at-risk summary, and per-account plays, no filler. - Accounts, ARR, and dates must be realistic; health ratings justified. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a note on how to review it in a weekly renewals stand-up. </format>

You are a real-estate operations manager tracking listings to close. <context> I need a listing-pipeline kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to move properties from lead to closed. </context> <inputs> - Market and property types: [E.G. RESIDENTIAL, COMMERCIAL, RENTALS] - Columns: [E.G. NEW LEAD, LISTING PREP, LIVE, UNDER OFFER, CLOSING, CLOSED] - Sample listings to seed: [5-8 PROPERTIES] - Status tags: [E.G. HOT, WARM, COLD] - Card fields: [E.G. ADDRESS, PRICE, AGENT, NEXT ACTION] </inputs> <task> Build a board where each listing card shows the address, list price, a status tag, the agent, and the next action, with per-column counts and a live sum of list prices per stage. Make cards draggable, persist to localStorage, add a status filter, and flag any Live listing older than 30 days on market. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Days-on-market flag compares real dates; price sums, drag, filter, counts functional. - Seed with realistic addresses and prices, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the days-on-market logic and how to add a commission field per card. </format>

You are a customer support lead who runs a triaged ticket queue. <context> I need a support-ticket kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to move tickets from new to resolved. </context> <inputs> - Product and common issues: [WHAT WE SUPPORT] - Columns: [E.G. NEW, TRIAGED, IN PROGRESS, WAITING ON CUSTOMER, RESOLVED] - Priority levels: [E.G. URGENT, HIGH, NORMAL, LOW] - Sample tickets to seed: [6-10 REAL TICKET SUBJECTS] - Card fields: [E.G. CUSTOMER, PRIORITY, AGENT, SLA DUE] </inputs> <task> Build a board where each ticket card shows a subject, a color-coded priority pill, the customer, the assigned agent, and an SLA-due chip, with per-column counts. Make cards draggable, persist to localStorage, add a priority filter, and turn the SLA chip red when a ticket is past due and not yet Resolved. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - SLA breach logic compares real times; drag, filter, counts functional. - Seed with realistic ticket subjects, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the SLA logic and how to route tickets to agents automatically. </format>

You are a support operations manager who handles escalations to engineering. <context> I need an escalation kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in, that tracks tickets escalated beyond tier-1. </context> <inputs> - Product and typical escalations: [WHAT GETS ESCALATED] - Columns: [E.G. ESCALATED, ENG INVESTIGATING, FIX IN PROGRESS, VERIFYING, CLOSED] - Severity scale: [E.G. S1, S2, S3] - Sample escalations to seed: [5-8 REAL ISSUES] - Card fields: [E.G. TICKET ID, CUSTOMER IMPACT, ENG OWNER, SLA] </inputs> <task> Produce a board spec with the columns above. Seed 5-8 realistic escalation cards across columns, each carrying a ticket ID, a customer-impact statement, a severity level, an eng owner, and an SLA target. Order each column by severity, add an aging note for cards open beyond their SLA, and include a short handoff template capturing what support must provide when escalating. </task> <constraints> - Output clean markdown: heading per column, cards as a table, plus the handoff template, no filler. - Impact statements must be specific; severities and SLAs realistic. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a note on how support and engineering should review it in a daily sync. </format>

You are an onboarding specialist who guides new customers to first value. <context> I need a customer-onboarding kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, to move each new account through onboarding. </context> <inputs> - Product and onboarding goal: [WHAT SUCCESS LOOKS LIKE, THE AHA MOMENT] - Columns: [E.G. KICKOFF, SETUP, TRAINING, FIRST VALUE, LIVE] - Sample accounts to seed: [5-8 CUSTOMERS] - Onboarding tiers: [E.G. SELF-SERVE, GUIDED, WHITE-GLOVE] - Card fields: [E.G. ACCOUNT, CSM, START DATE, TARGET GO-LIVE] </inputs> <task> Build a board where each account card shows the account, a tier pill, the CSM owner, a start date, and a target go-live date, plus a small progress bar that fills as it moves through the stages. Make cards draggable, persist to localStorage, and flag any account whose target go-live has passed while not yet Live. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Progress bar reflects current stage; go-live flag compares real dates; drag and counts functional. - Seed with realistic account names, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the progress and go-live logic and how to add an onboarding checklist per card. </format>

You are a product operations manager who triages customer feature requests. <context> I need a feature-request kanban delivered as a structured spec I can paste into Notion or Trello, with columns and seeded cards filled in, that turns raw feedback into a prioritized queue. </context> <inputs> - Product: [WHAT WE BUILD] - Columns: [E.G. NEW, UNDER REVIEW, PLANNED, IN PROGRESS, SHIPPED, DECLINED] - Common request themes: [3-5 RECURRING ASKS] - Sample requests to seed: [6-10 REAL REQUESTS] - Card fields: [E.G. REQUESTER COUNT, SEGMENT, EFFORT, THEME] </inputs> <task> Produce a board spec with the columns above. Seed 6-10 realistic feature-request cards across columns, each carrying the number of customers who asked, the segment they belong to, an effort estimate, and a theme label. Order the Under Review column by a demand-vs-effort score, and for each Declined card write a one-line reason to reuse in customer replies. </task> <constraints> - Output clean markdown: heading per column, cards as a table with demand and effort, plus decline reasons, no filler. - Requests must be specific and realistic; scores justified. - Format must paste cleanly into Notion or Trello. </constraints> <format> Return the board spec as a markdown artifact, then a note on how to link each card back to the customers who requested it. </format>

You are a support operations engineer who enforces SLAs across a shared queue. <context> I need an SLA priority-queue kanban built as one self-contained HTML file with inline CSS and vanilla JavaScript, previewable as an artifact, that always shows what to work next. </context> <inputs> - Support tiers and hours: [E.G. 24/7, BUSINESS HOURS] - Columns: [E.G. QUEUE, ASSIGNED, WORKING, PENDING, DONE] - Priority-to-SLA map: [E.G. URGENT 1H, HIGH 4H, NORMAL 24H] - Sample tickets to seed: [6-10 TICKETS WITH TIMES] - Card fields: [E.G. PRIORITY, TIME LEFT, AGENT] </inputs> <task> Build a board where each ticket card shows the subject, a priority pill, and a live countdown of time remaining against its SLA, sorted so the most-at-risk ticket sits at the top of each column. Make cards draggable, persist to localStorage, recompute the countdowns on load, and color cards green/amber/red as they approach breach. </task> <constraints> - One self-contained HTML file; runnable vanilla JS, no dependencies. - Countdown and color-by-time-left logic must actually compute from the SLA map; drag and sort functional. - Seed with realistic tickets and staggered timestamps, not placeholders. </constraints> <format> Return the full HTML as an artifact, then explain the countdown and color-threshold logic and how to alert on imminent breaches. </format>