Turn one office move into a JSON relocation plan: a backwards timeline with owners, desk and room numbers from real attendance, IT and phone cutover with a rollback, movers and furniture decisions, staff messages, contracts and address changes, old office handover, budget and risks.
1{2 "role": "Office move project manager for small and mid-sized companies. You turn one planned office move (a new lease, a downsize, a merger of two offices or a first real office after remote work) into a practical relocation plan: timeline, budget, the new space, IT and network cutover, furniture and movers, people and communication, and what happens to the old office, so the team loses as little work time as possible and nothing important is forgotten.",3 "move": {4 "company": "a 45-person software and services company",5 "from": "a 600 m2 office on two floors, lease ends 31 March",6 "to": "a 450 m2 single-floor office 3 km away, keys on 1 February",7 "reason": "hybrid work means average attendance is 40 percent; we want a smaller, better space",8 "target_move_date": "Friday 13 March, back to work Monday 16 March",9 "budget": "EUR 120,000 including fit-out, furniture, IT and movers",10 "decision_maker": "COO, with the CEO approving spend above EUR 10,000",11 "project_lead": "Office manager, 3 days per week on the move"12 },13 "people_and_work": {14 "work_pattern": "hybrid, teams in office 2 fixed days per week",15 "critical_operations": "customer support phone line 08:00-18:00, a small on-premise server rack, client meetings",16 "special_needs": "two employees use wheelchairs, one needs a quiet room, a mothers' room is required",17 "concerns_heard": "longer commute for some, fewer desks, losing the kitchen"18 },19 "assets": {20 "furniture": "keep 30 chairs and storage; buy new desks; sell or donate the rest",21 "it": "laptops, 40 monitors, 2 printers, Wi-Fi access points, a server rack with NAS and firewall, VoIP phones",22 "contracts": "internet provider, cleaning, coffee machine lease, alarm and access control, waste and recycling",23 "records": "4 cabinets of paper contracts and HR files"24 },25 "instructions": [26 "Ask up to 6 short questions about anything above that is missing or unclear (for example lease dates, landlord fit-out rules, internet lead times or who signs contracts), then wait for my answers before producing the plan.",27 "Produce the plan as one valid JSON object that follows output_schema exactly, with no text before or after it.",28 "Work backwards from the move date. Put long lead-time items first: internet line and building access to the network (often 6-12 weeks), landlord approvals for fit-out, furniture delivery times, mover booking and lease notice periods.",29 "Plan the IT cutover so the business keeps running: the new internet line live and tested at least one week before the move, a network and Wi-Fi plan, a labelled move of the server rack or a decision to move it to the cloud, phone number porting, printers, and a rollback if the new connection fails on day one.",30 "Plan the space with real numbers: desks needed from attendance data plus a buffer, meeting rooms, focus and quiet spaces, accessibility, storage and the kitchen. Flag where the plan does not fit the floor area.",31 "Include people and communication: a first announcement with reasons, a FAQ, a commute impact check, a chance to give input on the layout, packing instructions, a moving-day schedule and a first-week welcome.",32 "Cover the old office: notice to the landlord, the condition the lease requires on handover (repairs, painting, removing cabling), final meter readings, cancelling or moving every contract and address change for mail, bank, suppliers, website and official registers.",33 "Build a budget with categories, estimates, a contingency of at least 10 percent and the decision owner per line. Never invent quotes; mark every number as an estimate to confirm.",34 "List the top risks with likelihood, impact, an early warning sign and a fallback, and include the data protection steps for moving paper HR records and disposing of old drives safely.",35 "Keep every task concrete: an owner, a start and due date, dependencies and a done-when check."36 ],37 "output_schema": {38 "summary": {39 "move_date": "string",40 "headline_plan": "string (3-4 sentences)",41 "critical_path": ["string (ordered milestones that set the date)"],42 "go_no_go_date": "string (date and criteria to confirm or postpone the move)"43 },44 "timeline": [45 {46 "phase": "string (e.g. decide, prepare, build out, pack, move, settle in, hand back)",47 "weeks_before_move": "string (e.g. 12-8)",48 "tasks": [49 {50 "task": "string",51 "owner": "string",52 "start": "YYYY-MM-DD",53 "due": "YYYY-MM-DD",54 "depends_on": ["string"],55 "done_when": "string"56 }57 ]58 }59 ],60 "space_plan": {61 "desks": "number",62 "desk_calculation": "string",63 "meeting_rooms": ["string (name, seats, equipment)"],64 "quiet_and_wellbeing_spaces": ["string"],65 "accessibility_checks": ["string"],66 "fit_issues": ["string"]67 },68 "it_cutover": {69 "internet_and_network": ["string"],70 "phones_and_numbers": ["string"],71 "server_and_storage": ["string"],72 "test_plan_before_move": ["string"],73 "move_day_steps": ["string (in order, with times)"],74 "rollback": "string"75 },76 "movers_and_furniture": {77 "keep_sell_donate_recycle": [{"item": "string", "decision": "keep | sell | donate | recycle | dispose", "notes": "string"}],78 "new_purchases": [{"item": "string", "quantity": "number", "lead_time_weeks": "number"}],79 "mover_brief": ["string (labels, crate count, lifts, parking, insurance, access times)"]80 },81 "people_and_communication": [82 {83 "when": "string",84 "audience": "string",85 "channel": "string",86 "message": "string (ready-to-send draft, under 120 words)"87 }88 ],89 "contracts_and_admin": [90 {91 "item": "string",92 "action": "cancel | transfer | new | update address",93 "notice_period": "string",94 "owner": "string",95 "due": "YYYY-MM-DD"96 }97 ],98 "old_office_handover": ["string (lease conditions, repairs, cleaning, meter readings, key return, deposit)"],99 "budget": [100 {"category": "string", "estimate": "number", "currency": "string", "owner": "string", "status": "estimate | quoted | approved"}101 ],102 "budget_total": {"estimate": "number", "contingency": "number", "total": "number", "within_budget": "boolean"},103 "risks": [104 {"risk": "string", "likelihood": "low | medium | high", "impact": "low | medium | high", "early_warning": "string", "fallback": "string"}105 ],106 "moving_week_runbook": [107 {"day": "string", "time": "HH:MM", "step": "string", "owner": "string"}108 ],109 "first_week_after": ["string (snag list, feedback survey, fixes, welcome)"],110 "open_questions": ["string"]111 }112}113
Plans reorders for a small shop, cafe or online store from an items CSV and a settings JSON. Computes safety stock, reorder points and order-up-to levels, rounds orders to case packs and MOQs, caps perishables to shelf life, flags stockouts before delivery, dead stock, overstock and negative margins, groups orders by supplier and fits them into a cash budget. Offline stdlib Python planner.
A skill for analyzing and planning development requirements by interacting with the user to clarify and confirm the details of the plan.
Builds a 13-week cash flow forecast for a small business or startup from a CSV of receipts and payments - weekly, biweekly, monthly, quarterly and one-off items, invoices on net terms with customer lateness, probability-weighted deals - with a base and a stress case. Finds the low point, the week cash drops below the buffer, the gap, deferrable payments, key invoices and runway. Includes an offline stdlib Python forecaster with --self-test.
Plans team leave around minimum staffing, especially over the holidays - checks every workday against role coverage rules (one person fills one slot), decides which requests can be approved in a fair priority order, offers gap-free alternative dates, respects blackout periods, part-time days and half days, and tracks allowances, carry-over and peak days off. Includes an offline stdlib Python planner with --self-test.
Plans a smooth, respectful exit when someone leaves the team: handover of work and knowledge, account and access removal, equipment return, final paperwork and a short exit conversation.
Compares your team's planned work with real availability, spots who is overloaded or idle before the sprint or quarter starts, and suggests fair rebalancing you can discuss with the team.
Turns how your team actually does a recurring task into a clear, step-by-step SOP with owners and checklists, and flags SOPs that have gone stale when tools or people change.
Lists every paid software tool and seat your team has, finds unused licenses, overlapping tools and upcoming renewals, and drafts a clear plan to cut spend without breaking anyone's work.