confluence-explain-doc

原文涵盖的主题

• confluence-explain-doc
• 0. Load the domain profile first
• 1. Page structure (fixed order)
• 2. Code captures
• 3. Cause rows: blame plus original background
• 4. Noise removal (before every publish)
• 5. Publish and check
• Writing

Goal: a reader who opens the page once can explain the problem to someone else. Real code carries the explanation; prose stays minimal. Company/project specifics (site, space, branch names, glossary, label language, token location) live outside this skill so the skill stays portable. Read the first one that exists: 1. the file in $EXPLAINDOCDOMAIN 2. /.explain-doc/domain.md 3. /docs/agents/explain-doc-domain.md No profile: ask for the Confluence site, space key, and the "before" ref (usually the production branch). Template: references/domain-profile.md. No format headings ("Summary", "Overview", "TL;DR", "Click to expand"). Headings name the content. 1. Opening paragraph (no heading, 2-3 sentences): how many problems, the shared object they touch (one table, one value), and how they differ (e.g. one writes the wrong value, the other reads it and sends it). 2. One section per problem, numbered in the priority the user sets ( Problem N. : ). When you renumber, fix every "Problem N" reference too. Four lines ( , keyword — one plain sentence): symptom → cause → evidence it really happened or original background (with blame) → fix (commits). Define each term the first time it appears;

这里只展示节选，请以完整原文和当前要求为准。