Consolidate .mpx/CONTEXT.md into a concise, future-proof reference. Preserve all important detail while removing noise.
See skills/shared/DOCUMENTATION_STRATEGY.md for format details.
Input Resolution
- If
$ARGUMENTS is a file path, use that file.
- Otherwise, use
.mpx/CONTEXT.md.
- If not found, ask the user for the path.
Process
Step 1: Read & Analyze
Read every line of the full file against each issue type and build a classified findings list:
| Issue Type |
What to Look For |
| Duplicates |
Terms or features covering the same concept (keep the most current/complete version) |
| Superseded |
Content explicitly marked as superseded, replaced, or overridden by newer entries |
| Negative framing |
"must not", "cannot", "never" — convert to positive imperative |
| Non-content noise |
Implementation notes, deviation notes, historical provenance, issue-tracking meta, "Plan vN" / date labels |
| Outdated |
Struck-through items, removed parameters still referenced, resolved issue references |
| Inconsistencies |
Conflicting definitions or specifications |
| Bloated definitions |
Domain Language definitions exceeding one sentence |
| Misplaced content |
Architectural decisions that belong in DECISIONS.md, implementation details that belong in epics |
Step 2: Rewrite
Apply all changes directly and automatically. Produce the consolidated file:
- § Domain Language: one sentence max per definition, definition-list format (
**Term** — Definition.)
- § Core Features: index only (name + status + epic#), no implementation details
- § Key Constraints: concise bullets
- § Flagged Ambiguities: resolved term conflicts with rationale
- Target 250–300 lines total
Content rules:
- Remove implementation/deviation notes (belong in PRs or commit messages)
- Fix inconsistent values (use the most recent/authoritative source)
- Merge sections that were split by version history into unified topics
- Keep full technical detail where it matters: formulas, ranges, defaults
- Move any settled architectural decisions to DECISIONS.md instead
Step 3: Write Result
Write the consolidated file to the original path (overwrite), then re-read it to confirm the intended sections and retained technical details. Git history preserves the original.
Report
After writing, summarize:
- Line count: original vs. consolidated (and lines saved)
- Items removed, merged, or rewritten (counts)
- Inconsistencies fixed
- Items moved to DECISIONS.md (if any)
1---2name: consolidate-context3description: Consolidates CONTEXT.md by removing duplicates and outdated items and tightening the language.4---56Consolidate `.mpx/CONTEXT.md` into a concise, future-proof reference. Preserve all important detail while removing noise.78See `skills/shared/DOCUMENTATION_STRATEGY.md` for format details.910## Input Resolution11121. If `$ARGUMENTS` is a file path, use that file.132. Otherwise, use `.mpx/CONTEXT.md`.143. If not found, ask the user for the path.1516## Process1718### Step 1: Read & Analyze1920Read every line of the full file against each issue type and build a classified findings list:2122| Issue Type | What to Look For |23|---|---|24| **Duplicates** | Terms or features covering the same concept (keep the most current/complete version) |25| **Superseded** | Content explicitly marked as superseded, replaced, or overridden by newer entries |26| **Negative framing** | "must not", "cannot", "never" — convert to positive imperative |27| **Non-content noise** | Implementation notes, deviation notes, historical provenance, issue-tracking meta, "Plan vN" / date labels |28| **Outdated** | Struck-through items, removed parameters still referenced, resolved issue references |29| **Inconsistencies** | Conflicting definitions or specifications |30| **Bloated definitions** | Domain Language definitions exceeding one sentence |31| **Misplaced content** | Architectural decisions that belong in DECISIONS.md, implementation details that belong in epics |3233### Step 2: Rewrite3435Apply all changes directly and automatically. Produce the consolidated file:3637- § Domain Language: one sentence max per definition, definition-list format (`**Term** — Definition.`)38- § Core Features: index only (name + status + epic#), no implementation details39- § Key Constraints: concise bullets40- § Flagged Ambiguities: resolved term conflicts with rationale41- Target 250–300 lines total4243**Content rules:**44- Remove implementation/deviation notes (belong in PRs or commit messages)45- Fix inconsistent values (use the most recent/authoritative source)46- Merge sections that were split by version history into unified topics47- Keep full technical detail where it matters: formulas, ranges, defaults48- Move any settled architectural decisions to DECISIONS.md instead4950### Step 3: Write Result5152Write the consolidated file to the original path (overwrite), then re-read it to confirm the intended sections and retained technical details. Git history preserves the original.5354## Report5556After writing, summarize:57- Line count: original vs. consolidated (and lines saved)58- Items removed, merged, or rewritten (counts)59- Inconsistencies fixed60- Items moved to DECISIONS.md (if any)
MartinoPolo