From Rough Idea to Published Guide: The GuideForge Method, Step by Step

1. 01

   Introduction

   You do not need a finished outline to start. A rough idea is enough, as long as it says what you actually want someone to be able to do. The goal here is not to have AI “write something” for you. It is to keep your original intent intact while giving it structure one step at a time: who it is for; what they will be able to do; which form fits that job; and where it belongs. Every step stays reviewable, and a person decides what gets published. This Guide follows one example all the way through: “I want to show people how to turn a messy idea into a useful checklist.”

2. 02

   Step 1 — Capture the rough idea

   Write the idea down the way you would say it out loud. Do not polish it yet: early polish tends to hide the part you actually care about. For our example, the raw idea is: “I want to show people how to turn a messy idea into a useful checklist.” Before moving on, make sure the sentence captures the outcome you want for the reader. Here that is “a useful checklist”, not “an article about checklists”. It is fine for the idea to stay ambiguous. We do not yet know who “people” are or how messy “messy” is. Resolve that ambiguity on purpose in the next steps rather than guessing it away. Treat this sentence as private working material. Your rough idea is creation intent, not public copy. It should never silently become the description readers see. Check before continuing: can you name the one thing a reader should be able to do when they finish?

3. 03

   Step 2 — Shape the intent with Atlas

   Open the Guide creation page for your network and describe the idea to Atlas. Atlas reads your message and proposes a content type, difficulty, hub and collection, section outline, and questions about gaps it notices. Each proposal appears with a reason, and nothing changes until you accept it. Your prompt stays the source of truth: Atlas offers to add your message to the prompt, but never edits it silently. Use this step to settle three things: 1. Audience: “People” becomes “someone who has a messy idea and wants a checklist others can follow.” 2. Outcome: the reader finishes with a checklist they could hand to someone else. 3. Form: a step-by-step Guide (Tutorial) that ends in a checklist fits better than a single checklist, because the method needs explaining. If Atlas proposes something that does not fit, dismiss it and set the value yourself. Atlas proposes; you decide. It does not approve content or publish anything. Check before continuing: do the proposed type, hub and collection match where a reader would look for this?

4. 04

   Step 3 — Turn intent into a structured brief

   Before generating anything, write a short brief. It is the contract the draft has to meet. For our example: Audience: Someone with a messy idea who wants a checklist other people can follow. Reader outcome: A finished checklist of 5–10 concrete, checkable items. Module: Guide (Tutorial) that walks through the method and ends with the checklist. Scope: Turning one idea into one checklist. Not project management, checklist apps, or team rollout. Unknowns: How long the ideal checklist is; whether items should be ordered. Verification needs: Every item must be something a reader can confirm as done. Placement: Creator Workflow Playbook → Content Planning → Idea to Brief. Compare this with the raw idea. The sentence named an outcome. The brief names a reader, a measurable result, a boundary, and the unknowns you still have to decide. Nothing from the original intent was lost; it was made specific. Check before continuing: could someone else draft from this brief without asking you what you meant?

5. 05

   Step 4 — Generate the first structured draft with ForgeCore

   With the type, difficulty, hub, collection and brief set, generate the draft. ForgeCore turns the approved intent into a structured Guide: a title, a summary and ordered steps shaped by the content type you chose. For our example, a first draft might be organised like this: - why messy ideas fail as checklists; - write the outcome first; - list every action you can think of; - turn each action into a checkable item; - remove anything that is not an action; - order the items; - test the checklist on someone else. Structure is not truth. A well-organised draft can still be wrong, generic or padded. The draft is a starting point, not an answer. Everything generated stays editable. Nothing is saved as final and nothing is published by generating it. Check before continuing: does the draft follow your brief, or did it drift toward a generic article?

6. 06

   Step 5 — Edit in the Builder

   Open the draft in the Guide editor and make it yours. This is where your knowledge and voice replace the generic parts. - Rewrite sentences that sound like filler, such as “In today’s fast-paced world…” - Reorder, merge or delete steps so each one earns its place. - Check that the title and summary say exactly what the reader gets. - Confirm the hub and collection are still right. - Save as you go. Your edits are what gets reviewed. Here is what we would change in the example draft: Draft said: “Why messy ideas fail as checklists” as a full step. Change: shorten it into the introduction. Why: the reader came to build a checklist, not read theory. Draft said: “List every action you can think of.” Change: keep it, and add “Write verbs first: book, send, check.” Why: this makes the step actionable. Draft said: no example checklist. Change: add a finished six-item checklist at the end. Why: the reader can see the target result. Check before continuing: would you be comfortable putting your name on every sentence?

7. 07

   Step 6 — Run the pre-publish check

   Before publishing, go through this list. It mirrors the standard every GuideForge launch network is held to. [ ] Title says what the reader will be able to do. No “Ultimate Guide” or clickbait. [ ] Audience is clear from the title, summary or introduction. [ ] Usefulness: a reader can act on it immediately. [ ] Factual claims are true and within what you actually know. [ ] Sources: anything that depends on outside facts, safety, law or current platform rules is sourced, or left out. [ ] Creator identity: your real public profile is the author. [ ] Placement: the network, hub and collection are the ones a reader would expect. [ ] No raw prompts: your original instructions do not appear as public copy. [ ] No placeholders: no “Lorem”, “TBD”, “Overview and starting points” or template text. [ ] Public copy reads well out of context, for example in search results. [ ] Mobile preview is readable on a phone-width screen. [ ] Navigation links back to the hub and network work. If an item fails, fix it or leave the Guide as a draft.

8. 08

   Step 7 — Publish and verify the public result

   Publish through the product. Then check the result as a reader would see it, not as it looked in the editor. 1. Open the canonical public Guide link from the published result. 2. Confirm the byline shows your public profile. 3. Confirm the Guide appears under the right hub and collection, and the breadcrumbs lead back to the network. 4. Read the whole page signed out. Nothing from the editor or your private workspace should show. 5. Check it on a phone-width screen. Publishing makes the Guide public. It does not make it permanently correct. Set a reminder to reread it when the topic or product changes, and update or archive it when it stops being true.

9. 09

   Closing

   You started with one sentence and finished with a public Guide that says who it is for, what the reader can do, and where it belongs. The same method works for a checklist, a carousel or a network: keep the intent, add structure one step at a time, and keep a person in charge of what gets published. The finished example checklist (the end-state for the worked example): 1. Write the one outcome the checklist produces. 2. List every action, starting each with a verb. 3. Rewrite each action so someone else can tell when it is done. 4. Delete anything that is advice rather than an action. 5. Put the items in the order they happen. 6. Give the checklist to one person and fix every item they ask about.

End of guide · 9 steps