**Markers legend:** | `▲` top / answer | `●` first-level group | `⚠` violation (mixed kinds, unexplainable order) | `⇄` wrong order type | --- **Annotated text:** ▲ This memorandum describes how project teams identify and deliver significant profit improvements. It is organized in six sections: ● Background ⚠ ● Principles of the project-team approach ⚠ ● Definition of project work ⚠ ● Organization of the program ⚠ ● Distinctive benefits and results ⚠ ● Conditions required for success --- **Fi...
$npx -y skills add welltraum/minto --skill raw --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Raw?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/welltraum-raw-f4fedafe)
**Markers legend:**
| `▲` top / answer | `●` first-level group | `⚠` violation (mixed kinds, unexplainable order) | `⇄` wrong order type |
---
**Annotated text:**
▲ This memorandum describes how project teams identify and deliver significant profit improvements. It is organized in six sections:
● Background
⚠ ● Principles of the project-team approach
⚠ ● Definition of project work
⚠ ● Organization of the program
⚠ ● Distinctive benefits and results
⚠ ● Conditions required for success
---
**Findings:**
| Location | Violation | Fix |
|---|---|---|
| Opening line | No answer — topic label, not a claim | Replace with a one-sentence answer: "Project teams will deliver X because…" or "We recommend adopting project teams because…" |
| Six headings | Mixed kinds — Background (context), Principles (concepts), Definition (definition), Organization (structure), Benefits (outcomes), Conditions (prerequisites) | Group by same kind: either how-to steps, or benefits + enablers + risks |
| Six headings | No order explicable — recall order or ad-hoc sequence, not time/structure/ranking/deduction | Assign an order type and restructure: e.g., ranking by reader's needs, or time for a roll-out sequence |
| Vertical | Headings do not summarize into the opening — "how teams identify and deliver" does not obviously cover Background or Conditions | Rebuild the top as a precise claim that the six sections actually support |
---
**Score:**
| Axis | Rating | Notes |
|---|---|---|
| Top | 0/2 | Topic label only; no answer to a reader's question |
| Same-kind groups | 0/2 | Full mix of context, concepts, definitions, structures, outcomes, prerequisites |
| Order | 0/2 | Unexplainable sequence |
| MECE | 1/2 | Overlap between Conditions and Organization; gaps in implementation how-to |
| Display | 2/2 | Skeleton is immediately visible |
| **Total** | **3/10** | Not structured yet |
---
**Three highest-impact fixes:**
1. Replace the topic opening with an answer — a one-sentence claim about what project teams will achieve or why the reader should act.
2. Sort the six headings by kind — regroup into same-kind categories (e.g., *how to run it:* Definition, Organization, Conditions; or *why it works:* Principles, Benefits, Conditions).
3. Name an order principle and restructure — e.g., ranking by reader decision (Why → What → How), or time for a deployment sequence.
