Point → Line → Plane → Solid (点–线–面–体)

SKILL.md

---
name: point-line-plane-solid
description: "Activate when: user says 'we're good at X but not growing,' 'we need a moat,' 'we're just a feature not a platform,' 'competition keeps copying us,' 'we want to build something hard to replicate,' or asks how to move from product to platform to ecosystem. Do NOT activate when: the user is still searching for product-market fit (the point-level value hasn't been validated yet); or when the question is purely about execution speed or cost within an existing market (a line-level optimization, not a dimension problem)."
---

# Point → Line → Plane → Solid (点–线–面–体)

## Overview

Maps competitive position across four strategic dimensions: **Point** (one capability, easily copied) → **Line** (integrated pipeline, integration is the asset) → **Plane** (platform/ecosystem where others transact, network effects emerge) → **Solid** (multi-layer reinforcing system — technology, data, network, culture, capital — that requires replicating all layers simultaneously). Answers why some organizations build enduring competitive distance while excellent point-level competitors remain perpetually vulnerable.

**Cross-skill sequencing:** Use AFTER [first-principles] to decompose your current position; BEFORE [dynamic-core-competence] to identify which capabilities move you to the next dimension; WITH [network-effects] at the plane→solid transition.

## When to Use

Use this skill when:
- Competitors copy your core capability within 12–18 months of each launch
- You want a moat but are unclear what kind or at what level
- Strategic planning generates feature lists instead of platform thinking
- A product has hit a growth ceiling that better execution cannot solve
- Evaluating acquisitions, partnerships, or expansion for strategic fit

**When NOT to use:**
- Pre-product-market-fit: dimension elevation on a broken point is expensive failure
- Commodity execution problems (speed, cost, service level) — that's line optimization
- Resources are insufficient for transition — knowing you need a plane without funding it creates frustration, not direction

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has a concrete case → run The Process directly.
- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. **One-line framing:** "Most competition happens at the point level — fighting over who does X best. This framework asks: can you stop competing there by moving to the line, plane, or solid level, where the competition doesn't exist yet?"
2. **Check fit:** "Tell me about your current position. What do you do? Who copies it? How fast? That copy speed tells us what dimension you're competing at."
3. **Elicit their real case:** "Carnegie started with one steel mill — a point. He integrated mines, railroads, and coke into a line. Then a distribution ecosystem — a plane. By 1901, U.S. Steel paid ~$17 billion equivalent because you cannot replicate a solid; you must buy it. Now: what is your current situation?"
> **[WAIT — do not advance until user responds]**
4. **Run The Process one step at a time with their input:** "Name your current dimension honestly. What is ONE structural requirement to move to the next level?"
> **[WAIT — do not advance until user responds]**
5. **Close by naming the insight they uncovered:** "The payoff is competitive durability. Point-level competition is perpetual. Solid-level competition is near-zero — replicating a multi-layer system takes a decade and enormous capital even if you know what to build."
> **[WAIT — do not advance until user responds]**

## The Process

**Gate:** Confirm the current point-level value proposition is genuinely working before designing dimension elevation.

1. **Diagnose the current dimension.** Point: one capability, one sentence, directly comparable. Line: reliable integrated sequence, customers cannot decompose and rebuild it. Plane: more users creates more value for existing users; third parties participate. Solid: 4+ co-reinforcing layers (platform + data + brand + network effects + capital).
2. **Identify what prevents moving to the next dimension.** Point→Line: what adjacent capabilities must be integrated and what blocks it? Line→Plane: what must be true for third parties to participate (density, tools, economics, trust)? Plane→Solid: what additional layers must be added and how do they reinforce each other?
3. **Apply the business selection filter.** For each candidate path: score on 能 (capability fit) + 想 (organizational desire) + 值得 (economic return) + 该做 (strategic/ethical alignment). Fail multiple criteria = wrong-direction elevation.
4. **Design the first concrete transition step.** Specific: what is built, acquired, or partnered in the next 90 days. Not "become a platform" — "sign 3 API partners and build the tools they need."
5. **Establish the milestone for declaring dimension achievement.** "Platform declared when third-party-generated value exceeds 20% of total platform value."

**Stop-rule:** If the plan skips an intermediate dimension, return to line-building. Each dimension is the structural prerequisite for the next.

### Output: Dimension Progression Map

```
Current dimension: [Point/Line/Plane/Solid] — Evidence: [...]
Target dimension: [next level]
Gap analysis: 1. [...] 2. [...] 3. [...]
Selection filter: | Path | 能 | 想 | 值得 | 该做 | Decision |
90-day step: [what / who / partners / date / metric]
Milestone: [specific metric confirming next dimension]
Stop-rule: plan skip any intermediate dimension? [Yes–return / No–proceed]
```

*→ Method in Action: [Carnegie Steel's Dimension Progression (1875–1901)](examples/carnegie-steel-dimension-progression-1875-1901.md)*

## Dimension Packs

- **Software/platforms:** Point = one feature. Line = workflow integration + switching costs. Plane = API ecosystem + third-party builders. Solid = data + talent + capital flywheel (Salesforce, Microsoft, Apple).
- **Professional services:** Individual = point. Repeatable methodology = line. IP + alumni network = plane. Brand + proprietary knowledge + talent flywheel = solid.
- **Local businesses:** Single location = point. Standardized chain = line. Franchise system = plane. Supply chain + brand loyalty + inimitable culture = solid.
- **Contribution surface:** Line→plane structural requirements in your specific industry is the highest-value community contribution.

## Applying It Well

1. Diagnose dimension before prescribing strategy — point-level strategy (differentiation) is wrong at plane level (ecosystem development).
2. The line is the most underbuilt dimension. The unglamorous pipeline is the essential precondition for any platform ambition.
3. Network effects confirm the plane — if adding a new user doesn't make the system more valuable for existing users, the plane has not been achieved.
4. Solid-level defense requires active maintenance — neglect any layer and the solid delaminate.
5. Sequence strictly: line before plane, plane before solid. Multiple simultaneous jumps typically achieve none.

## Common Rationalizations

**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**

| Rationalization / Fake Move | Why It's a Trap |
|---|---|
| [D] "We're building a platform" (while still a point). | If no third-party value is created and no network effects are measurable, it is not yet a plane. The label does not create the dimension. |
| [D] "We need to scale before we can build the moat." | Scale at point level creates a bigger point, not a line. The line must be built alongside scale or before it. |
| [D] "Our technology is too hard to copy — that's our moat." | Technology moats are point-level defenses. They erode in 2–5 years unless embedded in a line, plane, or solid. |
| [D] "We'll worry about the business model once we have more users." | Business model clarity is a prerequisite for line-building — you cannot design a pipeline without knowing how value is captured. |
| [D] "We can skip the line phase — we'll go straight to platform." | Lines are the structural foundation for planes. A platform without a reliable underlying pipeline offers third parties nothing consistent. |
| [D] "The solid will emerge naturally once we're at scale." | Solids are designed and built layer by layer. Scale without intentional solid-building produces a large point vulnerable to platform disruption. |
| [D] "Platforms don't work in our industry — we tried." | Failed ecosystem attempts almost always lack underlying line density. The failure was the plane attempted without the line. |
| [D] "Our culture is our solid." | Culture is an element of a solid but not sufficient alone. Solid requires technological, platform, data, and capital layers co-reinforcing. |
| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |

## Red Flags

- Competitive advantage described in terms of a single product's quality only; competitors replicate it within 12–18 months.
- Growth requires proportional sales/marketing investment — linear, not exponential; network effects absent.
- Strategic plan describes "building an ecosystem" without specifying what third parties create or why they participate.
- Adjacent products produce complexity without integration — the line has not been built.

## Verification

- [ ] Current dimension diagnosed with specific evidence — not aspirationally labeled.
- [ ] Stop-rule applied: no intermediate dimension skipped without addressing structural prerequisites.
- [ ] Gap analysis names ≥3 specific structural requirements for the next dimension.
- [ ] Business selection filter (能+想+值得+该做) applied to ≥2 candidate paths.
- [ ] 90-day step specific enough to execute (what / who / partners / date / metric).
- [ ] Diagnosis stress-tested: if plane, are network effects measurable? If solid, are 4+ reinforcing layers identified?

*→ Primary sources: [references/sources.md](references/sources.md)*

---
*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/point-line-plane-solid** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*