pmx-canvas 0.1.0

package/skills/data-analysis/SKILL.md

@@ -0,0 +1,324 @@
+---
+name: data-analysis
+description: Analytics synthesis with visualizations from engineering and product data sources
+version: 0.1.0
+author: pmx
+tags: [analytics, data, charts, visualization, metrics]
+tools: [dx-data-cloud, jira/linear, github, workiq]
+inputs:
+  - name: question
+    description: The analysis question to answer (e.g. "How has PR cycle time changed over the last quarter?")
+    required: true
+  - name: data_sources
+    description: Array of MCP server names to query for data
+    required: false
+    default: [dx-data-cloud]
+  - name: format
+    description: Output format for the analysis
+    required: false
+    default: markdown
+    enum: [markdown, html]
+  - name: include_charts
+    description: Whether to include visual charts in the output
+    required: false
+    default: true
+outputs:
+  - name: analysis
+    description: Data analysis with findings, tables, charts (if HTML), interpretation, and recommendations
+---
+
+# Data Analysis
+
+Perform analytics synthesis across engineering and product data sources. Answer questions about trends, correlations, comparisons, and distributions by querying MCP servers, analyzing the data, and presenting findings with visualizations.
+
+In `pmx-canvas`, prefer `canvas_add_graph_node` for charts and trend lines and
+`canvas_add_json_render_node` when the analysis should land as a richer dashboard or table inside
+the canvas.
+
+## When to Use
+
+- Answering quantitative questions about engineering performance, delivery, or team health
+- Trend analysis: "How has X changed over time?"
+- Correlation analysis: "Is there a relationship between X and Y?"
+- Comparison analysis: "How does team A compare to team B?"
+- Distribution analysis: "What is the breakdown of X by Y?"
+- Preparing data-backed arguments for planning, retrospectives, or leadership updates
+- Any request that starts with "analyze", "compare", "show me the trend", "what is the distribution"
+
+## How It Works
+
+### Step 1: Parse the Question
+
+Analyze the user's question to determine:
+
+1. **Analysis type**: trend, correlation, comparison, distribution, or summary
+2. **Metrics needed**: What data points are required (cycle time, velocity, bug count, etc.)
+3. **Time range**: What period to analyze (last quarter, last 4 sprints, this year, etc.)
+4. **Grouping**: How to segment the data (by team, by sprint, by week, by component, etc.)
+5. **Data sources**: Which MCP servers have the required data
+
+If the question is ambiguous, ask clarifying questions before proceeding.
+
+### Step 2: Pull Data
+
+Query the relevant MCP servers:
+
+#### DX Data Cloud (DX MCP `queryData` tool in current session)
+Primary source for engineering metrics:
+- DORA metrics (deployment frequency, lead time, change failure rate, MTTR)
+- DX Index (DXI) survey results
+- Cycle time breakdowns
+- Throughput and flow metrics
+- Team-level aggregations
+
+Query using SQL against the DX Data Cloud PostgreSQL database. Tool prefixes vary by deployment (`dx-data-cloud` vs `dx-mcp`), so select the available DX `queryData` tool at runtime. Start with `information_schema` if unsure of available tables and columns.
+
+#### Jira/Linear
+Issue and sprint data:
+- Sprint velocity over time
+- Issue type distribution
+- Bug rates and trends
+- Epic completion rates
+- Cycle time (issue-level)
+
+#### GitHub
+Code and collaboration data:
+- PR cycle time (open to merge)
+- PR size distribution
+- Review turnaround time
+- Merge frequency
+- Contributor activity
+
+#### WorkIQ
+Collaboration and time data:
+- Meeting hours per week
+- Focus time trends
+- Collaboration patterns
+- Context switching indicators
+
+### Step 3: Perform Analysis
+
+Based on the analysis type identified in Step 1:
+
+#### Trend Analysis
+- Calculate the metric value for each time period (week, sprint, month)
+- Compute week-over-week or period-over-period change
+- Identify the overall trend direction (improving, declining, stable)
+- Calculate the rate of change
+- Identify inflection points or anomalies
+- Project forward if asked ("at this rate, when will we reach X?")
+
+#### Correlation Analysis
+- Pull both metrics for the same time periods
+- Calculate correlation coefficient (Pearson r)
+- Interpret strength: |r| > 0.7 strong, 0.4-0.7 moderate, < 0.4 weak
+- Note: correlation does not imply causation (always state this)
+- Show a scatter plot description or data table
+
+#### Comparison Analysis
+- Pull the same metric for different groups (teams, sprints, projects)
+- Calculate absolute and percentage differences
+- Rank groups by performance
+- Identify outliers (groups significantly above or below average)
+- Apply statistical context (is the difference significant or within normal variation?)
+
+#### Distribution Analysis
+- Group data by the specified dimension
+- Calculate counts and percentages for each group
+- Identify the dominant category and any long tails
+- Show as a table and describe what a pie/bar chart would look like
+
+### Step 4: Generate Output
+
+#### Markdown Format
+
+```markdown
+# Analysis: [Question Restated]
+
+**Period**: [time range]
+**Data Sources**: [list of sources queried]
+**Generated**: [timestamp]
+
+## Key Findings
+
+1. [Finding 1 - the most important insight]
+2. [Finding 2]
+3. [Finding 3]
+
+## Data
+
+### [Metric Name] Over Time
+
+| Period | Value | Change |
+|--------|-------|--------|
+| Week 1 | X     | -      |
+| Week 2 | Y     | +Z%    |
+| ...    | ...   | ...    |
+
+### Summary Statistics
+
+- Mean: X
+- Median: Y
+- Min: Z (period)
+- Max: W (period)
+- Standard Deviation: V
+
+## Interpretation
+
+[What the data means in plain language. Connect findings to
+business context. Explain why the trends matter.]
+
+## Recommendations
+
+1. [Actionable recommendation based on the data]
+2. [Another recommendation]
+
+## Methodology
+
+[Brief note on data sources, time ranges, and any caveats
+about data quality or completeness]
+```
+
+#### HTML Format
+
+Generate a self-contained HTML file with:
+
+- **Chart.js visualizations**:
+  - Line charts for trends
+  - Bar charts for comparisons
+  - Scatter plots for correlations
+  - Pie/doughnut charts for distributions
+- **Interactive features**: Hover tooltips, legend toggles
+- **Data tables**: Below each chart with the raw numbers
+- **Styled sections**: Clean typography, responsive layout
+- **Print-friendly**: CSS media queries for clean printing
+
+Include Chart.js via CDN link in the HTML head.
+
+### Analysis Framework: Numbers First, Then Interpretation
+
+Following the PMX vibe rules, always present data in this order:
+
+1. **Numbers**: Show the raw data and calculations first
+2. **Pattern**: Describe what the data shows (trend, correlation, distribution)
+3. **Interpretation**: Explain what it means in context
+4. **Recommendation**: Suggest action based on the findings
+
+Never lead with interpretation. Let the numbers speak first.
+
+## Examples
+
+### Example 1: Trend Analysis
+**Prompt**: "How has our PR cycle time changed over the last quarter?"
+
+Expected behavior:
+1. Query DX Data Cloud for PR cycle time, weekly, last 12 weeks
+2. Calculate week-over-week changes
+3. Identify overall trend (improving/declining)
+4. Generate markdown with data table and findings
+5. If HTML, include a line chart
+
+Output includes:
+- Weekly cycle time values
+- Average, min, max
+- Trend direction and rate of change
+- Comparison to team goals if defined in context.md
+
+### Example 2: Correlation Analysis
+**Prompt**: "Analyze the correlation between meeting load and developer productivity"
+
+Expected behavior:
+1. Query WorkIQ for meeting hours per developer per week
+2. Query DX Data Cloud or Jira for productivity proxy (throughput, cycle time, or velocity)
+3. Align time periods
+4. Calculate correlation coefficient
+5. Present scatter data and interpretation
+6. Note: "Correlation does not imply causation"
+
+### Example 3: Comparison Analysis
+**Prompt**: "Compare velocity across the last 4 sprints"
+
+Expected behavior:
+1. Query Jira/Linear for sprint velocity (story points completed) for last 4 sprints
+2. Calculate average, identify best and worst sprints
+3. Show sprint-over-sprint changes
+4. Identify contributing factors (scope changes, team changes, holidays)
+5. Present as comparison table and bar chart description
+
+### Example 4: Distribution Analysis
+**Prompt**: "What is the breakdown of issues by type this quarter?"
+
+Expected behavior:
+1. Query Jira/Linear for all issues created this quarter
+2. Group by type (feature, bug, task, spike, etc.)
+3. Calculate counts and percentages
+4. Present as table and describe pie chart
+5. Compare to previous quarter if useful
+
+### Example 5: Multi-Source Analysis
+**Prompt**: "Is there a relationship between our deployment frequency and bug reports?"
+
+Expected behavior:
+1. Query DX Data Cloud for deployment frequency (weekly)
+2. Query Jira/Linear for bug count (weekly, created date)
+3. Align time periods
+4. Calculate correlation
+5. Present findings with appropriate caveats
+
+### Example 6: Team Health Dashboard
+**Prompt**: "Give me an overview of engineering health metrics"
+
+Expected behavior:
+1. Pull DORA metrics from DX Data Cloud
+2. Pull DXI from DX Data Cloud
+3. Pull velocity from Jira/Linear
+4. Pull meeting load from WorkIQ
+5. Present dashboard-style summary with all metrics, trends, and RAG indicators
+
+## Statistical Methods
+
+### Trend Detection
+- Calculate linear regression slope over the period
+- Positive slope = improving (for metrics where higher is better)
+- Negative slope = improving (for metrics where lower is better, like cycle time)
+- Classify: strong improvement (>10% change), slight improvement (2-10%), stable (-2% to 2%), slight decline, strong decline
+
+### Correlation
+- Pearson correlation coefficient for linear relationships
+- Report r value and interpretation
+- Minimum 8 data points for meaningful correlation
+- Always caveat: correlation is not causation
+
+### Outlier Detection
+- Values beyond 2 standard deviations from the mean
+- Flag as anomalies with potential explanations (holidays, incidents, team changes)
+
+### Comparison Significance
+- For small sample sizes (< 10), note that differences may not be statistically significant
+- Calculate percentage difference and absolute difference
+- Provide context: "This is within/outside normal variation for this metric"
+
+## Data Source Discovery
+
+If unsure which tables or columns are available in DX Data Cloud, start with:
+
+```sql
+SELECT table_name, column_name, data_type
+FROM information_schema.columns
+WHERE table_schema = 'public'
+ORDER BY table_name, ordinal_position;
+```
+
+This helps discover the available data before writing analysis queries.
+
+## Notes
+
+- Always show numbers first, then interpretation (this is a core PMX principle)
+- Include data freshness: when was the data last updated?
+- If a data source is unavailable, note it and proceed with available sources
+- For time series, use consistent time buckets (don't mix weekly and monthly)
+- Always state the time range explicitly in findings
+- Round numbers appropriately: percentages to 1 decimal, days to 1 decimal, counts as integers
+- For HTML output, ensure the file is self-contained (inline CSS/JS, CDN for Chart.js)
+- When comparing teams, be sensitive: focus on systemic factors, not individual blame
+- If the data is insufficient to answer the question, say so rather than speculating

package/skills/doc-coauthoring/SKILL.md

@@ -0,0 +1,375 @@
+---
+name: doc-coauthoring
+description: Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
+---
+
+# Doc Co-Authoring Workflow
+
+This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
+
+## When to Offer This Workflow
+
+**Trigger conditions:**
+- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
+- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
+- User seems to be starting a substantial writing task
+
+**Initial offer:**
+Offer the user a structured workflow for co-authoring the document. Explain the three stages:
+
+1. **Context Gathering**: User provides all relevant context while Claude asks clarifying questions
+2. **Refinement & Structure**: Iteratively build each section through brainstorming and editing
+3. **Reader Testing**: Test the doc with a fresh Claude (no context) to catch blind spots before others read it
+
+Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.
+
+If user declines, work freeform. If user accepts, proceed to Stage 1.
+
+## Stage 1: Context Gathering
+
+**Goal:** Close the gap between what the user knows and what Claude knows, enabling smart guidance later.
+
+### Initial Questions
+
+Start by asking the user for meta-context about the document:
+
+1. What type of document is this? (e.g., technical spec, decision doc, proposal)
+2. Who's the primary audience?
+3. What's the desired impact when someone reads this?
+4. Is there a template or specific format to follow?
+5. Any other constraints or context to know?
+
+Inform them they can answer in shorthand or dump information however works best for them.
+
+**If user provides a template or mentions a doc type:**
+- Ask if they have a template document to share
+- If they provide a link to a shared document, use the appropriate integration to fetch it
+- If they provide a file, read it
+
+**If user mentions editing an existing shared document:**
+- Use the appropriate integration to read the current state
+- Check for images without alt-text
+- If images exist without alt-text, explain that when others use Claude to understand the doc, Claude won't be able to see them. Ask if they want alt-text generated. If so, request they paste each image into chat for descriptive alt-text generation.
+
+### Info Dumping
+
+Once initial questions are answered, encourage the user to dump all the context they have. Request information such as:
+- Background on the project/problem
+- Related team discussions or shared documents
+- Why alternative solutions aren't being used
+- Organizational context (team dynamics, past incidents, politics)
+- Timeline pressures or constraints
+- Technical architecture or dependencies
+- Stakeholder concerns
+
+Advise them not to worry about organizing it - just get it all out. Offer multiple ways to provide context:
+- Info dump stream-of-consciousness
+- Point to team channels or threads to read
+- Link to shared documents
+
+**If integrations are available** (e.g., Slack, Teams, Google Drive, SharePoint, or other MCP servers), mention that these can be used to pull in context directly.
+
+**If no integrations are detected and in Claude.ai or Claude app:** Suggest they can enable connectors in their Claude settings to allow pulling context from messaging apps and document storage directly.
+
+Inform them clarifying questions will be asked once they've done their initial dump.
+
+**During context gathering:**
+
+- If user mentions team channels or shared documents:
+  - If integrations available: Inform them the content will be read now, then use the appropriate integration
+  - If integrations not available: Explain lack of access. Suggest they enable connectors in Claude settings, or paste the relevant content directly.
+
+- If user mentions entities/projects that are unknown:
+  - Ask if connected tools should be searched to learn more
+  - Wait for user confirmation before searching
+
+- As user provides context, track what's being learned and what's still unclear
+
+**Asking clarifying questions:**
+
+When user signals they've done their initial dump (or after substantial context provided), ask clarifying questions to ensure understanding:
+
+Generate 5-10 numbered questions based on gaps in the context.
+
+Inform them they can use shorthand to answer (e.g., "1: yes, 2: see #channel, 3: no because backwards compat"), link to more docs, point to channels to read, or just keep info-dumping. Whatever's most efficient for them.
+
+**Exit condition:**
+Sufficient context has been gathered when questions show understanding - when edge cases and trade-offs can be asked about without needing basics explained.
+
+**Transition:**
+Ask if there's any more context they want to provide at this stage, or if it's time to move on to drafting the document.
+
+If user wants to add more, let them. When ready, proceed to Stage 2.
+
+## Stage 2: Refinement & Structure
+
+**Goal:** Build the document section by section through brainstorming, curation, and iterative refinement.
+
+**Instructions to user:**
+Explain that the document will be built section by section. For each section:
+1. Clarifying questions will be asked about what to include
+2. 5-20 options will be brainstormed
+3. User will indicate what to keep/remove/combine
+4. The section will be drafted
+5. It will be refined through surgical edits
+
+Start with whichever section has the most unknowns (usually the core decision/proposal), then work through the rest.
+
+**Section ordering:**
+
+If the document structure is clear:
+Ask which section they'd like to start with.
+
+Suggest starting with whichever section has the most unknowns. For decision docs, that's usually the core proposal. For specs, it's typically the technical approach. Summary sections are best left for last.
+
+If user doesn't know what sections they need:
+Based on the type of document and template, suggest 3-5 sections appropriate for the doc type.
+
+Ask if this structure works, or if they want to adjust it.
+
+**Once structure is agreed:**
+
+Create the initial document structure with placeholder text for all sections.
+
+**If access to artifacts is available:**
+Use `create_file` to create an artifact. This gives both Claude and the user a scaffold to work from.
+
+Inform them that the initial structure with placeholders for all sections will be created.
+
+Create artifact with all section headers and brief placeholder text like "[To be written]" or "[Content here]".
+
+Provide the scaffold link and indicate it's time to fill in each section.
+
+**If no access to artifacts:**
+Create a markdown file in the working directory. Name it appropriately (e.g., `decision-doc.md`, `technical-spec.md`).
+
+Inform them that the initial structure with placeholders for all sections will be created.
+
+Create file with all section headers and placeholder text.
+
+Confirm the filename has been created and indicate it's time to fill in each section.
+
+**For each section:**
+
+### Step 1: Clarifying Questions
+
+Announce work will begin on the [SECTION NAME] section. Ask 5-10 clarifying questions about what should be included:
+
+Generate 5-10 specific questions based on context and section purpose.
+
+Inform them they can answer in shorthand or just indicate what's important to cover.
+
+### Step 2: Brainstorming
+
+For the [SECTION NAME] section, brainstorm [5-20] things that might be included, depending on the section's complexity. Look for:
+- Context shared that might have been forgotten
+- Angles or considerations not yet mentioned
+
+Generate 5-20 numbered options based on section complexity. At the end, offer to brainstorm more if they want additional options.
+
+### Step 3: Curation
+
+Ask which points should be kept, removed, or combined. Request brief justifications to help learn priorities for the next sections.
+
+Provide examples:
+- "Keep 1,4,7,9"
+- "Remove 3 (duplicates 1)"
+- "Remove 6 (audience already knows this)"
+- "Combine 11 and 12"
+
+**If user gives freeform feedback** (e.g., "looks good" or "I like most of it but...") instead of numbered selections, extract their preferences and proceed. Parse what they want kept/removed/changed and apply it.
+
+### Step 4: Gap Check
+
+Based on what they've selected, ask if there's anything important missing for the [SECTION NAME] section.
+
+### Step 5: Drafting
+
+Use `str_replace` to replace the placeholder text for this section with the actual drafted content.
+
+Announce the [SECTION NAME] section will be drafted now based on what they've selected.
+
+**If using artifacts:**
+After drafting, provide a link to the artifact.
+
+Ask them to read through it and indicate what to change. Note that being specific helps learning for the next sections.
+
+**If using a file (no artifacts):**
+After drafting, confirm completion.
+
+Inform them the [SECTION NAME] section has been drafted in [filename]. Ask them to read through it and indicate what to change. Note that being specific helps learning for the next sections.
+
+**Key instruction for user (include when drafting the first section):**
+Provide a note: Instead of editing the doc directly, ask them to indicate what to change. This helps learning of their style for future sections. For example: "Remove the X bullet - already covered by Y" or "Make the third paragraph more concise".
+
+### Step 6: Iterative Refinement
+
+As user provides feedback:
+- Use `str_replace` to make edits (never reprint the whole doc)
+- **If using artifacts:** Provide link to artifact after each edit
+- **If using files:** Just confirm edits are complete
+- If user edits doc directly and asks to read it: mentally note the changes they made and keep them in mind for future sections (this shows their preferences)
+
+**Continue iterating** until user is satisfied with the section.
+
+### Quality Checking
+
+After 3 consecutive iterations with no substantial changes, ask if anything can be removed without losing important information.
+
+When section is done, confirm [SECTION NAME] is complete. Ask if ready to move to the next section.
+
+**Repeat for all sections.**
+
+### Near Completion
+
+As approaching completion (80%+ of sections done), announce intention to re-read the entire document and check for:
+- Flow and consistency across sections
+- Redundancy or contradictions
+- Anything that feels like "slop" or generic filler
+- Whether every sentence carries weight
+
+Read entire document and provide feedback.
+
+**When all sections are drafted and refined:**
+Announce all sections are drafted. Indicate intention to review the complete document one more time.
+
+Review for overall coherence, flow, completeness.
+
+Provide any final suggestions.
+
+Ask if ready to move to Reader Testing, or if they want to refine anything else.
+
+## Stage 3: Reader Testing
+
+**Goal:** Test the document with a fresh Claude (no context bleed) to verify it works for readers.
+
+**Instructions to user:**
+Explain that testing will now occur to see if the document actually works for readers. This catches blind spots - things that make sense to the authors but might confuse others.
+
+### Testing Approach
+
+**If access to sub-agents is available (e.g., in Claude Code):**
+
+Perform the testing directly without user involvement.
+
+### Step 1: Predict Reader Questions
+
+Announce intention to predict what questions readers might ask when trying to discover this document.
+
+Generate 5-10 questions that readers would realistically ask.
+
+### Step 2: Test with Sub-Agent
+
+Announce that these questions will be tested with a fresh Claude instance (no context from this conversation).
+
+For each question, invoke a sub-agent with just the document content and the question.
+
+Summarize what Reader Claude got right/wrong for each question.
+
+### Step 3: Run Additional Checks
+
+Announce additional checks will be performed.
+
+Invoke sub-agent to check for ambiguity, false assumptions, contradictions.
+
+Summarize any issues found.
+
+### Step 4: Report and Fix
+
+If issues found:
+Report that Reader Claude struggled with specific issues.
+
+List the specific issues.
+
+Indicate intention to fix these gaps.
+
+Loop back to refinement for problematic sections.
+
+---
+
+**If no access to sub-agents (e.g., claude.ai web interface):**
+
+The user will need to do the testing manually.
+
+### Step 1: Predict Reader Questions
+
+Ask what questions people might ask when trying to discover this document. What would they type into Claude.ai?
+
+Generate 5-10 questions that readers would realistically ask.
+
+### Step 2: Setup Testing
+
+Provide testing instructions:
+1. Open a fresh Claude conversation: https://claude.ai
+2. Paste or share the document content (if using a shared doc platform with connectors enabled, provide the link)
+3. Ask Reader Claude the generated questions
+
+For each question, instruct Reader Claude to provide:
+- The answer
+- Whether anything was ambiguous or unclear
+- What knowledge/context the doc assumes is already known
+
+Check if Reader Claude gives correct answers or misinterprets anything.
+
+### Step 3: Additional Checks
+
+Also ask Reader Claude:
+- "What in this doc might be ambiguous or unclear to readers?"
+- "What knowledge or context does this doc assume readers already have?"
+- "Are there any internal contradictions or inconsistencies?"
+
+### Step 4: Iterate Based on Results
+
+Ask what Reader Claude got wrong or struggled with. Indicate intention to fix those gaps.
+
+Loop back to refinement for any problematic sections.
+
+---
+
+### Exit Condition (Both Approaches)
+
+When Reader Claude consistently answers questions correctly and doesn't surface new gaps or ambiguities, the doc is ready.
+
+## Final Review
+
+When Reader Testing passes:
+Announce the doc has passed Reader Claude testing. Before completion:
+
+1. Recommend they do a final read-through themselves - they own this document and are responsible for its quality
+2. Suggest double-checking any facts, links, or technical details
+3. Ask them to verify it achieves the impact they wanted
+
+Ask if they want one more review, or if the work is done.
+
+**If user wants final review, provide it. Otherwise:**
+Announce document completion. Provide a few final tips:
+- Consider linking this conversation in an appendix so readers can see how the doc was developed
+- Use appendices to provide depth without bloating the main doc
+- Update the doc as feedback is received from real readers
+
+## Tips for Effective Guidance
+
+**Tone:**
+- Be direct and procedural
+- Explain rationale briefly when it affects user behavior
+- Don't try to "sell" the approach - just execute it
+
+**Handling Deviations:**
+- If user wants to skip a stage: Ask if they want to skip this and write freeform
+- If user seems frustrated: Acknowledge this is taking longer than expected. Suggest ways to move faster
+- Always give user agency to adjust the process
+
+**Context Management:**
+- Throughout, if context is missing on something mentioned, proactively ask
+- Don't let gaps accumulate - address them as they come up
+
+**Artifact Management:**
+- Use `create_file` for drafting full sections
+- Use `str_replace` for all edits
+- Provide artifact link after every change
+- Never use artifacts for brainstorming lists - that's just conversation
+
+**Quality over Speed:**
+- Don't rush through stages
+- Each iteration should make meaningful improvements
+- The goal is a document that actually works for readers