Check the input, then compare the complete deliverables
Explore the original materials, item-by-item outcomes and full report below. Attempt the input independently before using the reference to find omissions or disagreements.
Product and competitor material is synthetic. No live sites or Google Docs were accessed, and no market outcome was measured.
Original synthetic material. Try the input independently, then compare the reference results.
Original synthetic input
{
"synthetic": true,
"case": "google-docs-positioning-brief",
"data": {
"reader": "Small teams organizing customer email every week",
"sources": [
{
"id": "P01",
"product": "Our product",
"text": "Turns email into actions and reply drafts with source references. No measured time savings."
},
{
"id": "P02",
"product": "Competitor A",
"text": "Provides email summaries; the public page did not mention source references."
},
{
"id": "P03",
"product": "Competitor B",
"text": "Provides action extraction and drafts. Pricing and permission details were not obtained."
}
],
"feedback": [
{
"id": "C01",
"text": "Remove the unsupported claim that this is unique."
},
{
"id": "C02",
"text": "Remove the unsupported 50% time-saving number."
}
]
}
}Processing rules
Use only P01–P03. A feature not mentioned is unknown, not absent. Separate shared features, supported product capabilities and unverified differentiation. Remove unique/leading claims and invented outcomes. Process C01/C02 without overwriting an online document.
Complete reference results under this tutorial’s rules; nothing was written to a third-party service.Scroll horizontally within the table if needed.
| Claim | Evidence | Usable wording | Limit |
|---|---|---|---|
| Email to actions/drafts | P01 and P03 | Helps organize a small team’s tasks | Shared feature, not unique |
| Source references | P01 | Trace each action to its email | P02 silence does not prove absence |
| 50% greater efficiency | None | Remove the number | Features do not prove measured outcomes |
| Positioning candidate | P01 and reader task | Customer emails into traceable actions and drafts | Needs user validation |
Turn customer emails into traceable actions and reply drafts so a small team can see its next step.
Remove unique and 50%; retain source references without inventing results.
Positioning brief — synthetic exercise Reader: small teams handling weekly customer email. Candidate: customer emails into traceable actions and reply drafts. [P01] Value: extract actions, prepare replies, check sources. Shared: actions and drafts also appear in P03. Unknown: full competitor capabilities, pricing, permissions and user perception. C01: unique removed. C02: unsupported 50% removed. No online document created or changed.
Prepare the materials and check your tools
Start with the practice files
- Inventory reader needs, three sources and two comments.
- Separate feature evidence from outcome claims.
- Draft locally before looking at reference copy.
Before using real services
- Specify permitted official sources and reading scope.
- Keep unreceived pricing and permissions unknown.
- Verify document id, version and proposed range before edits.
Complete one file-based exercise first. For real services, verify the actual account, available tools and operation scope, then follow the acceptance check at each stage.
Download the original input and rules ↓Execution and takeover boundaries
The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.
Can run automatically
Draft a positioning brief from supplied product evidence and comments, preserving fact ids, revision reasons and evidence gaps.
Requires confirmation
Confirm overwriting Google Docs text, submitting comments or sharing documents. Feature and performance claims in the text must have supporting evidence.
Take over after a failure
Preserve the original and proposed changes when evidence conflicts or writes are uncertain. Have the user inspect versions, comments and saved content before further edits.
Inventory sources and the reader’s job
Positioning expresses value for a concrete reader. Incomplete source material narrows what a comparison can establish.
Use source-data.json only. Map the reader’s job, visible P01–P03 text and missing material. Do not search other competitors. Save source-map.md before writing promotional claims.A reader/source map.
Missing pricing, permissions and features stay unknown.
Separate shared features from possible differences
Not mentioned does not mean unavailable. Explain what the product evidence supports without asserting competitors cannot do it.
Build a claim→evidence→shared/candidate difference/unknown matrix. Cite P ids. Exclude unique, leading and unmeasured performance numbers.An evidence matrix.
Actions/drafts are shared; missing competitor information is not a negative fact.
Write concrete positioning and three value points
Use observable tasks and outputs rather than abstract adjectives. Channel length can vary while facts stay consistent.
Write one positioning sentence, three value points and one candidate paragraph each for website, X and LinkedIn. Attach source ids and flag wording requiring user validation. Promise no time or revenue gains.Channel copy with evidence.
Capabilities trace to P01 and no unsupported outcome number appears.
Revise against comments with a change trail
Resolve the referenced claim and explain the edit. Keep a single revision chain instead of creating new documents to bypass feedback.
Apply C01/C02: remove unique and unsupported 50%; clarify source references. Return revised copy and a response for each comment. Add no feature, testimonial or new achievement.Revised brief and two resolutions.
Both comments are handled without introducing new exaggeration.
Check the actual Docs target and version
Creating a document, replacing text and resolving comments are separate operations. Protect unrelated user changes.
Read <Docs id/current version> first and show the proposed paragraph diff. After specific confirmation, edit that range only and read back text/comment status. If unsupported, deliver a file marked unwritten; do not create duplicate documents.A verified revision or local file.
The same document id is used and unrelated edits remain intact.
Validate positioning through real feedback
Finished copy does not prove market acceptance. Keep hypotheses visible for user interviews or experiments.
Draft a positioning-brief Skill covering reader, source dates, claim matrix, channel copy, comment handling, versions and open validation questions. Stop at a document draft; do not change the site, publish or schedule promotion.A reusable process with research questions.
Candidate positioning is not reported as proven differentiation.
Find the evidence before choosing the next action
A competitor did not mention it
Say not established in the supplied material, then request authoritative evidence if needed.
Copy becomes vague
Return to a concrete task and observable deliverable.
Comments led to another document
Check target id and keep one revision chain.
Where did the performance number come from?
Remove it without a measurement record.
Check every item before finishing
These page-local checkboxes reset on refresh. Checking them does not verify a real service connection.
Checked 0 / 6 items
Download the inputs separately from the reference answers
Start with input and rules without showing the reference answers. After acceptance, save the report and complete prompt set.
source-data.json↓Rules and scopeDefinitions, exceptions and delivery requirements.workflow-rules.md↓Item-by-item reference resultsCompare every input with its outcome.expected-results.csv↓Complete reference reportResults, evidence and missing information.reference-report.md↓All stage prompts6 instructions with expected outputs and acceptance checks.practice-prompts.txt↓Check documented capabilities and exercise results separately
Content updated: · Editing a page does not reverify its sources or live workflow.
Documentation review: Unverified · no review date recorded
No case-specific documentation review is recorded. References below are provided for review and do not establish verification.
Live workflow verification: Unverified
Live accounts, external writes, scheduled execution and long-term operation are unverified. Synthetic exercises and page checkboxes do not establish live verification.
Product and competitor material is synthetic. No live sites or Google Docs were accessed, and no market outcome was measured.
- Grok Bot: files and results ↗
Check uploaded inputs, actual output paths and delivered files.
- Grok Bot: apps and the shared computer ↗
Check connected accounts, available tools, visibility and user takeover.
- Grok Bot: Skills and Routines ↗
Validate a manual run before saving a method or scheduling it.
Try another small batch of your own material
Retain original input and operation records. Verify that each result can be traced before adding connections or recurring runs.