task icon Task

Analyze Writing Style

Instructions
You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).
6

Analyze the writing samples and describe the style in natural prose.
Write to uiWriting Style under the section header for this source: - ## Slack Style (if source is slack) - ## Gmail Style (if source is gmail) - etc
Start each section with 'Last analyzed: [ISO datetime]' on its own line.
Include: tone, formality level, sentence patterns, vocabulary, and topics they write about. Preserve any existing sections for other services.

7

Briefly tell the user what you observed: 'I noticed you write in a [tone] style, [key observations]. Saved to your writing style profile.'

                    You MUST use a todo list to complete these steps in order. Never move on to one step if you haven't completed the previous step. If you have multiple read steps in a row, read them all at once (in parallel).

Add all steps to your todo list now and begin executing.

## Steps

1. [Read Writing Style Analysis Framework]: Read the documentation in: `./skills/sauna/[skill_id]/references/context.style.framework.md` (DILS framework for style observation)

2. [Read Writing Style Analysis Rules]: Read the documentation in: `./skills/sauna/[skill_id]/references/context.style.rules.md` (How to observe and describe style)

3. [Read Style Analysis Process]: Read the documentation in: `./skills/sauna/[skill_id]/references/context.style.process.md` (Process for analyzing writing samples)

4. [Read Writing Style]: Read the file at `./documents/user/writing_style.md` and analyze its contents (Existing style to preserve other service sections)

5. [Read Writing Samples]: Read the file at `./documents/tmp/writing-samples.json` and analyze its contents (The actual writing samples to analyze)

6. Analyze the writing samples and describe the style in natural prose.
Write to `./documents/user/writing_style.md` under the section header for this source: - ## Slack Style (if source is slack) - ## Gmail Style (if source is gmail) - etc
Start each section with 'Last analyzed: [ISO datetime]' on its own line.
Include: tone, formality level, sentence patterns, vocabulary, and topics they write about. Preserve any existing sections for other services.

7. Briefly tell the user what you observed: 'I noticed you write in a [tone] style, [key observations]. Saved to your writing style profile.'