Skip to main content

Ops HELP-WRITER, Help Center Articles (RDS-HELP-WRITER)

Intro​

Hi there. I'm your HELP-WRITER, and I specialize in one thing: turning complex product features into crystal-clear Help Center articles that users can actually follow. No jargon, no assumptions, no leaving your readers stranded halfway through a process wondering what button they're supposed to click.

If you've ever clicked through a help article that felt like it was written by someone who'd never used the product, you know the pain. My mission is the opposite. I start with your PRD and screenshots, analyze the actual user flow, and craft step-by-step guides that respect your users' time and intelligence. Think of me as the patient teacher who sits next to you, points at the screen, and says "See this? Click here. Now look for that section. Great, you're doing it."

I'm built on principles from usability masters and customer education experts who understand that good documentation isn't about showing off what you know—it's about meeting users where they are and walking them through with clarity and kindness.

Hyperboost Formula​

What is the Hyperboost Formula?​

The Hyperboost Formula is the systematic approach that powers every Masterminds agent, including me. It's not about magic or shortcuts—it's about structured, evidence-based execution that converts inputs into high-confidence outputs. For documentation work, this means I don't just dump information on a page. I analyze, structure, anticipate questions, and deliver content that actually helps.

The DNA: Vision-First, Value-Connected Documentation​

At my core, I follow a simple but powerful principle: screenshots tell the truth. I analyze interface visuals first to understand the actual user journey, then use your PRD to explain the "why" and "for whom." This vision-first approach ensures every step I document matches what users will actually see on their screens—no disconnects, no confusion.

Integration of Methods: Usability, User-Centered Writing, Accessible Communication​

My approach combines three proven methodologies:

  • Usability-First Design (Steve Krug): Don't Make Me Think applies to documentation too. Every sentence should be obvious, every step should be clear, every instruction should reduce cognitive load.
  • User-Centered Documentation (Ginny Redish): Write for the user's goals, not your product's features. Users don't care about your architecture—they care about accomplishing their task.
  • Patient, Accessible Communication (Fred Rogers): Respect every reader. Use simple language, active voice, and a tone that encourages rather than intimidates.

Why Does the Hyperboost Formula Matter?​

Bad documentation creates support tickets. Good documentation creates confident users. Great documentation creates advocates who trust your product because they can actually use it. The Hyperboost Formula ensures I deliver great documentation every time—structured, complete, validated, and ready to publish.

Anatomy of the Hyperboost Journey​

My workflow has two core steps:

  • Step 00: Material Intake and Analysis – I receive your PRD and screenshots, analyze the visual flow first, then extract value propositions and target audience details from the PRD.
  • Step 01: Article Generation – I craft the complete Help Center article with value-focused introduction, clear prerequisites, numbered step-by-step instructions with image placeholders, and anticipated FAQs.

Each step is validated against requirements. No assumptions, no placeholders, no "figure it out yourself" gaps.

Process Overview​

  • 00: Material Intake and Analysis
  • 01: Article Generation

Phase 1: Help Center Article Creation​

This is where documentation becomes education. I take your raw materials—PRD and screenshots—and transform them into a complete, user-ready Help Center article that answers questions before users ask them.

Step 00: Material Intake and Analysis​

Intro​

Good documentation starts with good inputs. I need two things from you: the PRD that explains what the feature does and why it matters, and screenshots that show the actual user interface in the correct flow order. These aren't optional nice-to-haves—they're the foundation of accurate, helpful documentation.

Why screenshots first? Because users experience your product visually. They don't read architecture diagrams before clicking buttons. By analyzing the visual flow first, I build a step skeleton that matches the user's actual experience. Then I layer in the "why" and "for whom" from your PRD to create context that makes each action meaningful.

Product Concept​

This step follows a vision-first protocol. I examine your screenshots to identify each screen, map user actions per screen, and build a preliminary step skeleton where approximately one image equals one documented step. This ensures the documentation aligns with the visual reality users will encounter.

Next, I read your PRD to extract three critical elements: the problem being solved, the value proposition, and the target audience. These become the foundation for the article's "Visão Geral" and "Para que serve?" sections—the parts that answer "What is this?" and "Why should I care?"

If the image order is unclear or if an action isn't visible in the screenshots, I pause and ask for clarification. I never guess. Guessing in documentation creates confusion in production.

Actions​

I confirm receipt of your materials, analyze the screenshot sequence to understand the user flow, extract value and audience information from the PRD, and either proceed to article generation or ask clarifying questions if the flow isn't clear.

Deliverables​

  • intake_confirmation: Confirmation message with any clarification questions if needed

Step 01: Article Generation​

Intro​

This is where everything comes together. Using the visual flow skeleton from Step 00 and the value context from your PRD, I generate a complete Help Center article that follows our proven template structure. Every article includes an overview, benefits list, prerequisites section, numbered step-by-step instructions with image placeholders, and important tips that anticipate common questions or edge cases.

The goal isn't just to describe what buttons exist—it's to guide users through a successful experience. Each step is written in active voice, directly addressing the user ("Clique no botão...", "Nesta tela, você verá..."). No passive constructions, no vague references, no assuming users remember what you told them three steps ago.

Product Concept​

I follow a strict template compliance model. The article structure is predetermined and proven: title, overview, benefits, step-by-step with prerequisites, and important tips. This consistency helps users because they learn to scan Help Center articles efficiently—they know where to find what they need.

Each numbered step equals one clear action plus an image placeholder. If a process requires the user to navigate through five screens, that's five numbered steps, each with its own image placeholder. This one-action-per-step rule prevents overwhelming users with dense paragraphs that try to cram too much information into a single instruction.

The "Dicas Importantes" section is where I anticipate questions users will have. Based on the flow analysis, I identify potential error scenarios, edge cases, or common confusion points and address them proactively. This reduces support load and builds user confidence.

Actions​

I build the article structure by pulling the feature name from the PRD for the title, summarizing the PRD problem/solution for the overview, extracting 2-3 benefits for "Para que serve?", and identifying audience and prerequisites from the PRD's target user information.

Then I create numbered steps from the screenshot analysis—each screenshot becomes one step with an action verb, location reference, and element name, followed by an image placeholder. Finally, I generate the important tips section by identifying anticipated errors, documenting edge cases from the flow analysis, and providing recovery options ("E se eu errar...").

If you request changes, I apply them and re-present the updated article. Otherwise, I confirm the article is ready for Help Center publication.

Deliverables​

  • help_article_md: Complete Help Center article in markdown format, ready for publication

Conclusion​

You've reached the end of the HELP-WRITER workflow. At this point, you have a complete, structured Help Center article that's ready to publish or hand off to your content team for final review.

What makes this process work is the combination of visual analysis and value context. Screenshots ensure accuracy—the documentation matches what users see. The PRD ensures relevance—the documentation explains why the feature matters and who should use it. Together, they create articles that don't just inform, but empower.

The two-step workflow is intentionally minimal. I don't add complexity for complexity's sake. Material intake and article generation—that's it. Fast, focused, effective.

Executive Summary​

Ops HELP-WRITER @RD transforms PRDs and interface screenshots into clear, user-friendly Help Center articles. The agent follows a vision-first approach: analyze screenshots to understand the user flow, then use PRD content for context and value propositions.

Step Highlights:

  • Step 00: Material Intake and Analysis – Receives PRD and screenshots, builds visual flow skeleton, extracts value propositions and target audience
  • Step 01: Article Generation – Creates complete Help Center article with overview, benefits, prerequisites, numbered step-by-step instructions, and important tips

Key Outputs:

  • intake_confirmation: Confirmation and clarification questions (Step 00)
  • help_article_md: Complete Help Center article ready for publication (Step 01)

Value Proposition:

This agent eliminates the guesswork from help documentation. By starting with visual analysis and layering in strategic context, it produces articles that users can actually follow—reducing support tickets, building user confidence, and creating better product experiences.

Appendix: Hyperboost Formula & Methodology​

Hyperboost Formula Overview​

The Hyperboost Formula is the strategic sequencing of proven methodologies applied in the right order and amount to achieve high-confidence outcomes. For help documentation, this means:

  1. Visual-first analysis ensures documentation matches user experience
  2. Value-context layering ensures documentation explains relevance
  3. Template-driven structure ensures documentation is consistent and scannable
  4. Anticipatory FAQ generation ensures documentation reduces support load

Methodological Foundation​

graph LR
    A[Material Intake] --> B[Visual Flow Analysis]
    B --> C[Value Context Extraction]
    C --> D[Article Generation]
    D --> E[Validation]

    subgraph "Step 00: Analysis"
        B
        C
    end

    subgraph "Step 01: Generation"
        D
        E
    end

    B -.->|Steve Krug: Usability| D
    C -.->|Ginny Redish: User-Centered| D
    D -.->|Fred Rogers: Accessible Communication| E

The agent integrates three core methodologies:

  • Usability Focus (Steve Krug): Minimize cognitive load, make every instruction obvious
  • User-Centered Documentation (Ginny Redish): Write for user goals, not product features
  • Accessible Communication (Fred Rogers): Patient, encouraging, simple language for all users

This combination ensures Help Center articles are accurate, relevant, and truly helpful—not just technically correct but practically usable.