{"success":true,"tutorial":{"module_slug":"plans","content_version":"2026-08-19-v6","title":"Plans tutorial","summary":"Why successful projects start with a written plan, how to create and update plans with Server Agent, how to pick a document font, how to fix display issues, how to generate a 1–2 page stakeholder summary (Email and Print at the top, no plan menu), and how to share and turn a plan into a project.","icon":"fas fa-clipboard-list","estimated_minutes":12,"steps":[{"id":"why_plan","title":"Successful projects start with a plan","body":"Every strong project begins the same way: with a **clear written plan** before anyone builds, buys, or commits a schedule.\n\nA good plan answers the questions that keep work on track:\n• What are we trying to achieve, and **why** does it matter?\n• Who is it for, and what does **success** look like?\n• What is **in scope** — and what is deliberately out?\n• What are the phases, decisions, risks, and open questions?\n• What happens first, second, and third?\n\nSkip that thinking and teams rework the same decisions, miss requirements, and discover blockers late. Capture it early and everyone can move with confidence.","tips":["If you cannot explain the goal and the next three steps simply, the plan is not ready yet.","Treat the plan as the source of truth from idea through delivery — and keep updating it as reality changes."]},{"id":"what_plans","title":"What Plans is for","body":"**Plans** is MD Hub’s home for strategy and implementation documents — the living blueprint for an initiative, not a pile of forgotten files.\n\nEach plan is a full document (HTML + metadata) stored in the database. You can refine it, version it, share it, and later turn it into execution.\n\nTypical uses:\n• New products, websites, campaigns, or internal rollouts\n• Client proposals and delivery roadmaps\n• RFP / bid analysis and response outlines\n• Rebuilds, migrations, and multi-step operational changes\n\nUse **Plans** when you need alignment first. Use **Project Manager** when you are ready to assign and track the work.","tips":["You own plans you create; team-shared plans appear in your list as Shared (view/use, not edit).","Version (v1, v2, …) bumps when major regenerations or updates land."]},{"id":"why_written","title":"Why a written plan pays off","body":"Writing the plan down is not bureaucracy — it is how you protect time, budget, and relationships.\n\n• **Clarity** — fuzzy ideas become concrete scope and milestones\n• **Alignment** — clients, partners, and teammates share one story\n• **Fewer surprises** — open questions surface in Q&A before you spend build time\n• **Clean handoffs** — new people read the plan instead of hunting through chat history\n• **Accountability** — status shows whether work is new, blocked on answers, building, done, or abandoned\n\nIn short: the plan becomes the single source of truth from idea through delivery.","tips":["Revisit the plan when facts change. A stale plan is almost as risky as no plan."]},{"id":"how_module_helps","title":"How this module helps you create a solid plan","body":"Plans is a **guided planning workshop**, not just a document list. The Server Agent does the heavy drafting so you can focus on judgment and decisions.\n\n• **New plan** — describe the outcome; pick a **document font**; attach briefs, decks, notes, or research; receive a structured first draft (phases, checklists, questions)\n• **Analyze RFP** — upload a solicitation or bid package; get requirements, gaps, questions, and a response outline\n• **Knowledge Bases** — ground drafts in your real policies, product facts, and playbooks\n• **AI specialists** — add MD AI Agents so their instruction files guide tone and structure\n• **Update** — answer questions, request changes, or add new questions; the agent revises and versions the document\n• **Stakeholder summary** — a 1-page executive brief (2 pages max) with no left menu or plan shell, for people who will not read the full plan\n• **Share** — teams, Address Book contacts, or a public view link so feedback lands on one document\n• **Build project** — when the plan is ready, create a Project Manager project and execute\n\nYou spend time on decisions, not formatting — and the plan stays current as you learn more.","tips":["Better inputs create better plans: clear goals, real constraints, and the source files stakeholders already use.","Vague one-line goals produce vague plans."]},{"id":"rhythm","title":"The planning rhythm that works","body":"Use this loop for almost any initiative:\n\n1. **Frame** — start a New plan with purpose, audience, success criteria, and constraints\n2. **Draft** — let the Server Agent produce the first structured document in the background\n3. **Read critically** — treat version 1 as a strong draft, not a finished promise\n4. **Resolve Q&A** — answer what you know; leave honest unknowns visible\n5. **Refine** — run Update until the plan is buildable and stakeholders agree\n6. **Align** — generate a **stakeholder summary** (1–2 pages, no menu) and Share for review; fold feedback into the next Update\n7. **Execute** — set status to Building, build or link a project, and work the steps\n8. **Close** — mark Completed when outcomes match the plan, or Abandoned if priorities change","tips":["Unanswered questions do not disappear — they become expensive surprises during delivery.","Skipping Q&A is how “solid plans” fail in production."]},{"id":"list","title":"Your plans list","body":"The table is your command center. It shows plans you own and plans shared with your teams.\n\nColumns: **ID**, **Name** (slug under it), **Type**, **Status**, **Version**, **Project**, **Modified**, **Actions**.\n\nFilters:\n• **Search** — name / text\n• **Type** — Plan, RFP, Grant, RCA Report\n• **Status** — New, Q&A, Building, Completed, Abandoned\n• **Show completed** — finished plans stay hidden by default so active work stays front and center\n• **Project** — all / tied to a project / not tied\n• **Refresh** — reload after a Server Agent job finishes\n\nOwner row actions: **View** · **Update** · **Fix** (styles + document font) · **Stakeholder summary** · **Share** · **Delete** · click the **status badge** · **Build project** when none is linked.","tips":["Shared-with-me rows only offer View (and Open summary if one exists). No Update / Share / Delete / Fix / generate summary.","While a job is queued or running, refresh when you get the completion notice. Summarize jobs show a **Summarizing** spinner.","If a job never finishes, open Server Agent → Jobs (see “If a plan fails to build”)."]},{"id":"jobs","title":"New plan, Update, Analyze RFP, and summaries","body":"These enqueue **Server Agent** jobs (you are notified when they finish):\n\n• **New plan** — job type **plan**; agent writes full plan HTML into a new row. Pick a **document font** (Inter, Source Sans, Merriweather, Montserrat, Lora, and others) so the stored plan uses that typeface\n• **Update** (per row) — job type **update_plan**; loads the current plan, applies your notes, saves the same row\n• **Analyze RFP** — job type **create_rfp**; builds a full RFP package stored as a plan\n• **Stakeholder summary** (per row) — job type **summarize_plan**; writes a 1–2 page executive brief onto the plan without changing the full document\n\nJob modal fields (typical): title, **Knowledge Base**, AI model · max turns · timeout, optional analysis sections (FMV, SWOT, gap, compliance, respond to RFP, Grant Response), **AI agents** as chips, and your prompt (or answers / changes / questions on Update). Use **Improve my prompt** to polish notes before enqueue.\n\nAfter enqueue: open **Server Agent → Jobs** and **Run** if needed (or wait for the worker). While a job is queued or running, the Plans list shows a **Building** / **Updating** / **Summarizing** spinner — press **Refresh** after you get the completion notice.","tips":["On Update you do not paste the whole plan — the job loads it automatically.","Best Update prompt: answers to open questions + requested changes + any new questions."]},{"id":"build_failed","title":"If a plan fails to build","body":"Plans are created by background **Server Agent** jobs. When something goes wrong, fix the job first — then re-run or rewrite the request.\n\n**How failure shows up**\n• A temporary row stays on **Building / Queued** and never becomes a real plan ID\n• Or the plan exists but is empty / unfinished after the job finishes with an error\n• Or you get a failure notification and **Server Agent → Jobs** shows status **error** / **failed**\n\n**What to do (in order)**\n1. Open **Server Agent → Jobs** and find the plan / create_rfp / update_plan job\n2. Open the job row and read the **error message** (timeout, rate limit, missing prompt, model, capacity, etc.)\n3. **Common fixes**\n • **Still queued** — press **Run** on the job (or wait for the worker / cron)\n • **Timeout** — enqueue again with a **higher Timeout (minutes)** and/or fewer max turns; split a huge RFP into a shorter first pass\n • **Rate limit / too many active jobs** — wait for other jobs to finish, then **Retry** or re-enqueue\n • **Plan limit / capacity** — delete unused plans or open **Capacity Upgrade**, then try **New plan** again\n • **Server Agent disabled** — an admin must enable Server Agent for the account in **Agent Manager**\n • **Empty or weak prompt** — rewrite the brief (goal, audience, constraints, source material) and use **Improve my prompt**\n • **Update failed** — re-open **Update** on the plan with clearer answers/changes; the current plan content is loaded automatically\n4. If a failed **New plan** never created a plan row, start a fresh **New plan** (or **Analyze RFP**) with the improved prompt — do not wait forever on a dead placeholder row\n5. Back in **Plans**, click **Refresh** so the list matches Server Agent\n\nA failed job is not a permanent block — it is a signal to adjust timeout, capacity, or the brief and try again.","tips":["Check Server Agent → Jobs error text before re-enqueueing the same prompt unchanged.","Large RFPs and multi-section analyses need more timeout and a clearer brief than a one-line goal.","You are notified when jobs finish — if you never get a notice, confirm the job actually ran (Run / worker)."]},{"id":"fix_display","title":"Fix display and layout issues","body":"AI-generated plan HTML sometimes looks broken in the viewer even when the content is fine. Typical symptoms:\n\n• Hard-coded light-only colors that break **dark mode** (or the reverse)\n• Page stuck at a narrow **pinned max-width** or cut-off layout\n• Rigid multi-column grids that overflow on mobile\n• Missing CSS so cards, badges, and sidebars look unstyled\n\n**How to fix it**\n1. Open the plan with **View** to confirm it is a style/layout issue (not empty content)\n2. On your **owned** plan row, click **Fix** (wand icon — “Fix plan styles”)\n3. The dialog sizes to the full form. Expand **Document font** to preview typefaces (Inter, Source Sans, Merriweather, Montserrat, Lora, Source Code Pro, and more), then **Fix styles**\n4. MD Hub repairs theme colors, widths, grids, and missing style blocks **without rewriting the plan text**, and applies the chosen font\n5. If anything changed, a **new version** is saved (v2, v3, …). Open **View** again to verify\n6. If **Fix** reports no issues but the page still looks wrong, try a hard-refresh of the viewer; then use **Update** to ask the agent for a cleaner layout only if content structure is the problem\n\n**Fix** is owner-only (shared teammates can View, not repair). Prefer **Fix** before asking stakeholders to review a broken layout.","tips":["Fix styles does not invent new sections — it only repairs presentation of the HTML you already have, and can change the document font.","If View shows a blank plan after a failed build, go back to “If a plan fails to build” — styles cannot fix empty content.","After a successful Fix, re-share the plan link so reviewers see the cleaned version."]},{"id":"stakeholder_summary","title":"Stakeholder summary (1–2 pages, no menu)","body":"The full plan is for the team that will build. Stakeholders who only need the story should get a **short executive brief**, not a cloned plan with the left-hand menu.\n\n**What it is**\n• **1 US Letter page preferred, 2 pages maximum**\n• Purpose, status, outcomes, approach, timeline, budget/effort (if present), risks, and decisions needed\n• **No plan menu, TOC, or sidebar** — a plain readable article\n• **Email** and **Print** sit at the top of the brief (hidden when you print or when you email it)\n• Stored on the plan row; the full document is not rewritten\n\n**How to use it**\n1. On a plan you own, click the **stakeholder summary** action (file/lines icon)\n2. Pick a **document font** if you want a typeface other than Inter. The font list expands in the form so you can see each face\n3. **Generate summary** queues a Server Agent job (`summarize_plan`). The row shows **Summarizing** until it finishes\n4. When a brief already exists, choose **Open existing** or **Generate new**. Opening an older brief strips leftover plan-shell menus immediately; generate new for a true 1–2 page rewrite\n5. Use **Email** at the top to send the brief via MD Hub Email (pick an Address Book contact or type an address), or **Print** for a hard copy. Share the full plan separately if reviewers need the complete document\n\nIf the job fails, open **Server Agent → Jobs** the same way as a failed New plan / Update.","tips":["If an older summary still looks like the full plan, generate a new one — the prompt now forbids copying the plan HTML and left nav.","Shared teammates can open an existing brief; only the owner can generate or replace it.","Email and Print are on the brief only — they do not appear on the printed page or in the emailed copy."]},{"id":"share_projects","title":"View, share, projects & status","body":"• **View** — open the formatted plan in the plan shell viewer (access-checked). That viewer has the plan menu; the stakeholder summary does not\n• **Fix** — repair broken layout/theme styles and set document font on plans you own (see Fix display)\n• **Stakeholder summary** — 1–2 page executive brief with no menu; Email and Print at the top (see previous step)\n• **Share** — available at any plan status (including Building, Completed, and Abandoned). Grant a team access, email a link to an Address Book contact, and/or copy a public URL. Chain of custody tracks who shared what and when\n• **Build project** — create a Project Manager project from the plan when none is linked so tasks follow the blueprint\n• **Status** — New → Q&A → Building → Completed, or **Abandoned**. Status can also sync from plan content (Q&A sections, checklist progress)\n\nOwners control edits and deletes. Teammates with shared access can open and use the plan according to their access.\n\nReopen this walkthrough anytime with **Tutorial** (header or toolbar).","tips":["Share works at any status. Prefer share links over emailing huge HTML.","Start your next initiative with a plan — before you schedule the build."]}]},"progress":{"completed":1,"last_step":9,"completed_at":"2026-08-01 19:24:08"},"auto_open":false,"content_version":"2026-08-19-v6"}