feat(v1.1.0): Services Hub pattern + 3-mode studio readiness

[lapc506]

Summary

Replaces auto-closed PR #4. Same scope, rebased on main after merge of #1, #2, #3.

• New skill services-hub-setup (patrón feat(v1.1.0): Services Hub pattern + 3-mode studio readiness #6) — middle ground between Multi-LLC and formal studio
• Refactored when-to-become-studio from binary ready/not-ready → 3-mode routing (Mode 1/2/3)
• Updated structure-decision, shared-services-ledger, attached-fund-structure to integrate with Services Hub
• New canonical reference lapc506-services-hub-canonical.md
• v1.1.0 release in plugin.json + CHANGELOG

Greptile 5/5 on prior PR #4 (commit a06396e).

Test plan

• CI green on rebased branch
• Greptile re-confirms 5/5

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR introduces the Services Hub pattern (patrón #6) as a middle ground between serial-entrepreneur Multi-LLCs and a formal studio with an attached fund, and refactors when-to-become-studio from binary ready/not-ready into a 3-mode routing system. All 5 updated/new skills are coherently cross-referenced and the new lapc506 canonical reference provides concrete numbers grounding the pattern.

Confidence Score: 5/5

Safe to merge — all findings are P2 style/consistency improvements with no blocking logic errors.

All remaining findings are P2: a missing table row (covered by the rules section below it), a transfer pricing range that understates the default, a stale version field, a missing integration link, and a missing keyword. None affect functional skill routing correctness. The core 3-mode routing logic, cross-skill references, legal disclaimers, and canonical case are internally consistent and well-documented.

skills/when-to-become-studio/SKILL.md (decision table gap + TP range), skills/structure-decision/SKILL.md (version field), .claude-plugin/plugin.json (missing keyword)

Important Files Changed

Filename	Overview
skills/when-to-become-studio/SKILL.md	Major refactor to 3-mode routing; well-structured but the primary Decisión table omits the explicit 8-9 ✓ WITHOUT fund → Mode 2 row, and the transfer pricing range cited (5-10%) understates the 10%-default used in services-hub-setup.
skills/services-hub-setup/SKILL.md	New skill; 7-step flow is well-structured, strong legal/tax disclaimers present, good cross-references to related skills and OECD guidelines.
skills/structure-decision/SKILL.md	Correctly adds patrón #6 and renumbers #7; Regla 2 decision table updated accurately; YAML frontmatter version remains 1.0.0 despite significant content changes, unlike the other skills updated in this PR.
skills/shared-services-ledger/SKILL.md	Operating mode table correctly added at the top; differencias operacionales are clear; Integración con otras skills section at the bottom does not list services-hub-setup despite it being the complementary skill for Services Hub mode.
skills/attached-fund-structure/SKILL.md	Well-placed guard clause added upfront; correctly routes non-qualifying users to services-hub-setup or when-to-become-studio; version bumped to 1.1.0.
references/lapc506-services-hub-canonical.md	Concrete canonical case with real numbers; architecture diagram, setup cost breakdown, and evolution triggers all present; appropriate privacy note on omitted personal data.
.claude-plugin/plugin.json	Version correctly bumped to 1.1.0; services-hub is not present in keywords despite being the headline feature of this release, unlike other patterns which are all listed.
CHANGELOG.md	Comprehensive changelog entry with Linear issue links, clear added/fixed/pending sections, and accurate description of all changed skills.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Start: when-to-become-studio]) --> B[Evaluate 9 readiness signals]
    B --> C{Score?}
    C -->|0–4 ✓| D[**Modo 1**\nSerial entrepreneur puro]
    C -->|5–7 ✓| E[**Modo 2**\nServices Hub operator]
    C -->|8–9 ✓| F{Real fund plan?\nLP conversations initiated?}
    F -->|Yes| G[**Modo 3**\nFormal studio con fund]
    F -->|No| E
    D --> D1[structure-decision\npatrones 1–5]
    D --> D2[Re-assess in 6–12 months]
    E --> E1[structure-decision\npatrón #6]
    E --> E2[services-hub-setup\nMSAs + transfer pricing]
    E --> E3[shared-services-ledger\nServices Hub mode]
    G --> G1[structure-decision\npatrón #7]
    G --> G2[attached-fund-structure\nMgmt Co + GP + LP]
    G --> G3[shared-services-ledger\nFull Studio mode]
    G --> G4[studio-thesis / studio-focus\n/ secret-sauce]

Loading

Comments Outside Diff (3)

1. skills/structure-decision/SKILL.md, line 1-15 (link)

   Version not bumped despite significant content changes

   structure-decision remains at version: 1.0.0 while the other three skills updated in this PR (when-to-become-studio, shared-services-ledger, attached-fund-structure) were all bumped to 1.1.0. This skill received equally substantive changes: new patrón feat(v1.1.0): Services Hub pattern + 3-mode studio readiness #6, renumbered patrón feat(v1.2.0): gastronomic analogy + Mermaid diagrams + bilingual/MCP guides #7, updated Regla 2 decision table, and a new canonical case 4.

2. skills/shared-services-ledger/SKILL.md, line 362-368 (link)

   services-hub-setup missing from integration section

   The operating mode table at the top of the skill explicitly lists services-hub-setup as the complementary skill for Services Hub mode, but the "Integración con otras skills" section at the bottom omits it. Users following the integrations list as a checklist won't be directed there.

3. .claude-plugin/plugin.json, line 12-29 (link)

   services-hub keyword missing from plugin manifest

   Every other named corporate-structure pattern has a dedicated keyword (cayman-sandwich, delaware-tostada, skip-cr-pattern), but the headline feature of this release — the Services Hub Model — has no corresponding keyword. This reduces discoverability for users searching the plugin registry by pattern name.

_{Reviews (1): Last reviewed commit: "fix(Greptile 4/5→5/5): align output temp..." | Re-trigger Greptile}

[greptile-apps]

Decisión table missing explicit 8-9 ✓ without fund → Mode 2 row

The table only covers three scenarios, but there are four: a user scoring 8-9 with no real fund plan will find no matching row and may incorrectly default to Mode 3 (the only row shown for their score range). The correct routing (→ Mode 2) is documented in "Reglas adicionales" below, but the summary table should be self-contained.

Suggested change

	**Decisión** (updated v1.1 — 3 modes):
	| Score | Recomendación | Siguiente skill |
	|---|---|---|
	| 0-4 ✓ | **Modo 1 — Serial entrepreneur puro** | Multi-LLCs via `structure-decision` (patrones 1-5). No formalizar más allá. |
	| 5-7 ✓ | **Modo 2 — Services Hub operator** (NUEVO) | `services-hub-setup` skill + `structure-decision` patrón #6 |
	| 8-9 ✓ + plan fund atado | **Modo 3 — Formal venture studio con fund** | `attached-fund-structure` skill + `structure-decision` patrón #7 |
	| Score | Recomendación | Siguiente skill |
	|---|---|---|
	| 0-4 ✓ | **Modo 1 — Serial entrepreneur puro** | Multi-LLCs via `structure-decision` (patrones 1-5). No formalizar más allá. |
	| 5-7 ✓ | **Modo 2 — Services Hub operator** (NUEVO) | `services-hub-setup` skill + `structure-decision` patrón #6 |
	| 8-9 ✓ + plan fund atado REAL (LP conversations iniciadas) | **Modo 3 — Formal venture studio con fund** | `attached-fund-structure` skill + `structure-decision` patrón #7 |
	| 8-9 ✓ SIN plan fund atado real | **Modo 2 — Services Hub operator** | `services-hub-setup` skill + `structure-decision` patrón #6. Re-evaluar a Modo 3 cuando haya LP conversations iniciadas. |

[greptile-apps]

Transfer pricing range inconsistency with services-hub-setup

This section states cost-plus (5-10% markup típico), but services-hub-setup establishes 10% as the standard default with 5% reserved for low-value services and 15% for highly specialized work. A user reading only this roadmap step would underestimate the recommended markup, potentially producing documentation that conflicts with what services-hub-setup generates.

Suggested change

	- Ver skill `services-hub-setup` para:
	- MSA template bilateral (Services LLC ↔ cada Venture LLC)
	- SOW templates por service type
	- Transfer pricing cost-plus 10% markup (OECD-defensible; ver `services-hub-setup` para rangos por tipo de servicio)