Consolidate a project context file into a concise, future-proof reference. Preserve all important detail while removing noise.
Input Resolution
- If
$ARGUMENTS is a file path, use that file.
- Otherwise, search for
.mpx/CONTEXT.md first (new format), then .mpx/REQUIREMENTS.md (legacy), then REQUIREMENTS.md in project root.
- If no file found, ask the user for the path.
Process
Step 1: Read & Analyze
Read the full file. Scan for each issue type and build a 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 |
Vocabulary definitions exceeding one sentence |
Step 2: Rewrite
Apply all changes directly — do not ask for confirmation. Produce the consolidated file:
For CONTEXT.md:
- § Domain Language: one sentence max per definition, definition-list format
- § Core Features: index only (name + status + epic#), no implementation details
- § Key Constraints: concise bullets
- Target 250–300 lines total
For legacy REQUIREMENTS.md:
- Group by functional area with clear
## section headings
- Use imperative mood and positive framing
- Remove temporal labels, provenance lines, supersession headers
Content rules (both formats):
- 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
Step 3: Write Result
Write the consolidated file to the original path (overwrite). 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
1---2name: mp-consolidate-requirements3description: Consolidate CONTEXT.md (or legacy REQUIREMENTS.md): remove duplicates, outdated items, tighten language. Use when: "consolidate requirements", "clean up requirements", "consolidate context", "simplify context".4---56Consolidate a project context file into a concise, future-proof reference. Preserve all important detail while removing noise.78## Input Resolution9101. If `$ARGUMENTS` is a file path, use that file.112. Otherwise, search for `.mpx/CONTEXT.md` first (new format), then `.mpx/REQUIREMENTS.md` (legacy), then `REQUIREMENTS.md` in project root.123. If no file found, ask the user for the path.1314## Process1516### Step 1: Read & Analyze1718Read the full file. Scan for each issue type and build a findings list:1920| Issue Type | What to Look For |21|---|---|22| **Duplicates** | Terms or features covering the same concept (keep the most current/complete version) |23| **Superseded** | Content explicitly marked as superseded, replaced, or overridden by newer entries |24| **Negative framing** | "must not", "cannot", "never" — convert to positive imperative |25| **Non-content noise** | Implementation notes, deviation notes, historical provenance, issue-tracking meta, "Plan vN" / date labels |26| **Outdated** | Struck-through items, removed parameters still referenced, resolved issue references |27| **Inconsistencies** | Conflicting definitions or specifications |28| **Bloated definitions** | Vocabulary definitions exceeding one sentence |2930### Step 2: Rewrite3132Apply all changes directly — do not ask for confirmation. Produce the consolidated file:3334**For CONTEXT.md:**35- § Domain Language: one sentence max per definition, definition-list format36- § Core Features: index only (name + status + epic#), no implementation details37- § Key Constraints: concise bullets38- Target 250–300 lines total3940**For legacy REQUIREMENTS.md:**41- Group by functional area with clear `##` section headings42- Use imperative mood and positive framing43- Remove temporal labels, provenance lines, supersession headers4445**Content rules (both formats):**46- Remove implementation/deviation notes (belong in PRs or commit messages)47- Fix inconsistent values (use the most recent/authoritative source)48- Merge sections that were split by version history into unified topics49- Keep full technical detail where it matters: formulas, ranges, defaults5051### Step 3: Write Result5253Write the consolidated file to the original path (overwrite). Git history preserves the original.5455## Report5657After writing, summarize:58- Line count: original vs. consolidated (and lines saved)59- Items removed, merged, or rewritten (counts)60- Inconsistencies fixed
MartinoPolo