# Rock Doc Builder

**Status:** <mark style="color:$primary;">Live</mark>

### What It Does

Company leaders open a Claude Project, answer a series of guided questions about their quarterly Rock, and receive a fully branded Rock Overview Document as a .docx file they can save directly to Google Drive. Claude handles the content drafting and formatting automatically based on the Rock Doc template and The Mailworks brand system.

Examples of what leaders can say:

* "I need to build a Rock Doc."
* "I need to create a Rock Doc for our Portal 2.0 migration work this quarter."
* "Here are my notes on a new Rock, help me turn this into a Rock Doc."

### Architecture

{% code overflow="wrap" %}

```
Custom Instructions (interview logic) → SKILL.md (generation rules) → generate_rock_doc_template.js (branded .docx output) → Google Drive
```

{% endcode %}

The Custom Instructions define what Claude asks and how it writes. When the leader approves the content, Claude reads SKILL.md for generation rules, populates the JavaScript template with the approved content, and produces a branded .docx. The leader saves it to Google Drive with one click.

### Document Structure

Every Rock Doc contains these sections in this exact order:

1. Title
2. "Rock Overview Document"
3. Rock Owner with Primary Owner, Supporting Department, Related One-Year Goal(s)
4. Rock Outcome, "Done Means" with completion criteria
5. Context & Intent
6. Alignment with One-Year Plan
7. Scope Boundaries with In Scope and Explicitly Out of Scope
8. Anticipated Work & Sequencing with task table
9. Dependencies & Considerations
10. Supporting Documents & Artifacts

Divider lines separate each major section.

### Brand System

| Element   | Font                         | Color                  | Capitalization |
| --------- | ---------------------------- | ---------------------- | -------------- |
| Title     | Proxima Nova ExtraBold, 30pt | Navy `#0B3B60`         | Title Case     |
| Heading 1 | Proxima Nova, 16pt, Bold     | Indicia Pink `#E81F76` | Title Case     |
| Heading 2 | Proxima Nova, 14pt, Bold     | Navy `#0B3B60`         | Title Case     |
| Heading 3 | Proxima Nova, 14pt, Bold     | Teal `#3FBEAC`         | Title Case     |
| Body Text | Proxima Nova, 11pt, Regular  | Graphite `#58595B`     | Sentence case  |
| Divider   | Solid 1px                    | Graphite `#58595B`     |                |

Additional formatting:

* Line spacing is 1.15 on all text including headings
* Done Means bullets are italic with bold keywords
* Table header row uses Navy `#0B3B60` background with white text
* Alternating table rows use light gray `#F5F5F5`
* Specific boilerplate phrases have bold keywords ("high-level, chronological outline", "single source of truth", "Done")
* No em dashes anywhere in generated content

### Project Components

| Component           | File                            | Location            | Description                                                          |
| ------------------- | ------------------------------- | ------------------- | -------------------------------------------------------------------- |
| System Prompt       | Content pasted directly         | Custom Instructions | Interview flow, writing standards, section-by-section question guide |
| Knowledge File      | `rock-doc-knowledge-file.md`    | Project Files       | EOS terminology, One-Year Goals, Rock Doc conventions                |
| Skill Instructions  | `SKILL.md`                      | Project Files       | Rules for .docx generation, formatting specs, document structure     |
| Generation Template | `generate_rock_doc_template.js` | Project Files       | JavaScript template that produces the branded .docx                  |
| Example Rock Docs   | 8 PDF files                     | Project Files       | Existing Rock Docs used for tone and depth calibration               |

### Access

* This skill currently lives in a private Claude Project called "Rock Doc Builder." Only users with access to the project can use it. It is not available organization-wide.

### Current Limitations

* Claude cannot edit Google Docs directly with this method. The output after talking to Claude needs to be "Opened With Google Drive" via the Google Drive button in the artifact.

### What's Next

* Allow Claude to create and edit Google Docs directly via MCP.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledge.themailworks.com/skills/rock-doc-builder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.