[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M784MZXF7XP7EX260704RME9":3,"skill-same:01M784MZXF7XP7EX260704RME9":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":72,"commitSha":73,"skillDirectory":74,"forksCount":75,"repositoryHtmlUrl":76,"repositoryHomepageUrl":6,"ownerHtmlUrl":77,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":78,"install":79,"resources":92},"01M784MZXF7XP7EX260704RME9","edgy-deep-dive",null,"Targeted EDGY 23 deep-dive analysis of a specific element pair or facet combination. Requires an existing edgy-model.json produced by the edgy-assessment skill. Analyses the chosen elements through one of four analytical lenses (dependency, alignment, gaps, opportunities) using both direct core links and 2-hop paths. Produces a focused markdown report and a pairwise draw.io diagram.","Rahola\u002Fedgy-skills","Rahola","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20344242?v=4","01M784MGJXTM1QWBCF4635ZW7X","Roope Ahola","01M784MGKX2JMBT2CBX1NBNTJX",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Farchitecture\u002Fedgy-deep-dive\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: edgy-deep-dive\nversion: \"1.1.2\"\ndescription: >\n  Targeted EDGY 23 deep-dive analysis of a specific element pair or facet combination.\n  Requires an existing edgy-model.json produced by the edgy-assessment skill.\n  Analyses the chosen elements through one of four analytical lenses (dependency,\n  alignment, gaps, opportunities) using both direct core links and 2-hop paths.\n  Produces a focused markdown report and a pairwise draw.io diagram.\ncategory: architecture\ntags: [edgy, enterprise-design, architecture, analysis, deep-dive, intersection, fi, en]\nlanguages: [fi, en]\nagents:\n  - claude-code\n  - cursor\n  - vibe\n  - generic\ninputs:\n  - name: model\n    type: file\n    description: >\n      edgy-model.json produced by the edgy-assessment skill.\n      Contains all 12 EDGY elements, active core links, coherence scores,\n      and suggested deep-dive analyses for this company.\n  - name: focus_elements\n    type: array\n    description: >\n      2–3 EDGY element names to analyse. Use official names:\n      purpose, story, content, capability, asset, process,\n      task, channel, journey, organisation, product, brand.\n      Examples: [\"capability\", \"organisation\"] or [\"task\", \"channel\", \"journey\"]\n  - name: lens\n    type: enum\n    values: [dependency, alignment, gaps, opportunities, all]\n    default: all\n    description: >\n      Analytical lens to apply.\n      dependency   — how the elements need each other; critical dependencies\n      alignment    — coherence between elements; contradictions\n      gaps         — missing links or underdeveloped elements\n      opportunities — competitive advantage or growth potential\n      all          — all four lenses\n  - name: language\n    type: enum\n    values: [fi, en]\n    default: fi\n    description: >\n      Output language. Currently only fi and en are supported (output templates\n      and lens-specific section headers are localised for these two only).\noutputs:\n  - type: markdown\n    description: Focused deep-dive analysis with direct and 2-hop core-link analysis\n  - type: file\n    description: edgy-diagram-compatible TXT input for pairwise map\n  - type: file\n    description: draw.io diagram (pairwise layout, focus elements bold-bordered)\n---\n\n# EDGY Deep-Dive Analysis\n\n## Purpose\n\nThis skill performs a **targeted analysis of a specific EDGY element pair** using\nan existing company EDGY model as context. It traces both direct core links and\nindirect (2-hop) paths between the chosen elements, then analyses their relationship\nthrough the selected lens.\n\nUse this skill when:\n- You have completed an `edgy-assessment` and want to explore a specific element pair in depth\n- The assessment's \"Suggested deep-dive analyses\" section identified a High-priority pair\n- The client wants to understand how, for example, Architecture capabilities are\n  structured relative to the Organisation, or how Products map to customer Tasks\n\n**Prerequisite:** `edgy-assessment` must have been run and produced `\u003Ccompany>-edgy-model.json`.\n\n**This skill produces:**\n- `\u003Ccompany>-deep-dive-\u003Celements>.md` — focused analysis report\n- `\u003Ccompany>-deep-dive-\u003Celements>.txt` — edgy-diagram input (pairwise map)\n- `\u003Ccompany>-deep-dive-\u003Celements>.drawio` — pairwise draw.io diagram\n\n**IMPORTANT:** Produce all output in the language specified by the `language` parameter.\n\n---\n\n## Official 24 EDGY Core Links (reference for path tracing)\n\n\u003C!-- edgy-links:begin format=flat-fi-en -->\n| Source → Target | FI | EN |\n| ----------------- | ---- | ---- |\n| story → purpose | kontekstualisoi | contextualises |\n| content → purpose | ilmaisee | expresses |\n| content → story | välittää | conveys |\n| brand → story | herättää | evokes |\n| brand → purpose | edustaa | represents |\n| capability → asset | vaatii | requires |\n| process → capability | toteuttaa | realises |\n| process → asset | vaatii | requires |\n| product → capability | vaatii | requires |\n| process → product | luo | creates |\n| task → journey | on osa | is part of |\n| task → channel | käyttää | uses |\n| journey → channel | kulkee | traverses |\n| brand → task | tukee | supports |\n| brand → journey | näkyy | appears in |\n| organisation → purpose | tavoittelee | pursues |\n| organisation → story | kirjoittaa | authors |\n| organisation → capability | omistaa | has |\n| organisation → process | suorittaa | performs |\n| product → task | palvelee | serves |\n| product → journey | esiintyy | features in |\n| organisation → brand | rakentaa | builds |\n| organisation → product | valmistaa | makes |\n| product → brand | ilmentää | embodies |\n\u003C!-- edgy-links:end -->\n\n---\n\n## Agent Instructions\n\n### CRITICAL: Read the full instructions before starting\n\nDo not skip phases. Every phase is required to produce a complete, grounded analysis.\n\n---\n\n### Phase 1: Load Context\n\n0. **Validate the model** against the shared schema before reading it:\n   `python3 \u003Cedgy-assessment>\u002Fscripts\u002Fvalidate_edgy_model.py \u003Ccompany>-edgy-model.json` (schema:\n   `skills\u002Farchitecture\u002Fedgy-assessment\u002Fassets\u002Fedgy-model.schema.json`). A\n   model that fails validation is not analysed — ask the user to fix it or to\n   run `edgy-assessment` in `extract-model` mode. Never invent elements that\n   the model does not contain.\n1. Read the `model` file (edgy-model.json). `elements.organisation` is one object (format 1.8)\n   or an array (1.9), and so is `elements.journey` from format 1.10 (one object, or an array of\n   journeys with ids) — treat a single object as a list of one. With several journeys, analyse\n   the ones the focus names, or each in turn; never merge them into one.\n2. Extract the entries for all `focus_elements` from `elements`.\n3. Note the coherence scores from `coherence` for any intersection elements in the focus.\n4. Check `suggested_deep_dives` — if this exact pair was suggested, note its rationale and priority.\n\n**Minimum requirement:** You must extract at least one element description and at least one active core link from the model before proceeding. If the model is missing or malformed, ask the user to run `edgy-assessment` first.\n\n---\n\n### Phase 2: Trace Core-Link Paths\n\nBuild the **link graph** for the focus elements:\n\n#### Step 1 — Direct links (1-hop)\nList every core link from the table above where *both* source and target are in `focus_elements`.\n\nExample for `[\"capability\", \"organisation\"]`:\n- `organisation → capability: has` ✓ (direct)\n\n#### Step 2 — 2-hop paths\nList every path A → X → B (or B → X → A) where A and B are in `focus_elements` and X is any other element.\n\nExample for `[\"capability\", \"organisation\"]`:\n- `organisation → process: performs` AND `process → capability: realises`\n  → path: organisation **→(performs)→** process **→(realises)→** capability\n\n#### Step 3 — Cross-check with active model links\nFrom the model's `core_links` array, mark which of the above links are *active* (present in the model) vs. *theoretical* (in the framework but not observed in this company). An absent link that *should* exist is itself a gap finding.\n\nPresent results as a table:\n\n| Path | Hops | Status | Verb(s) |\n|------|------|--------|---------|\n| organisation → capability | 1 | Active | omistaa |\n| organisation → process → capability | 2 | Partial (process→capability missing) | suorittaa \u002F toteuttaa |\n\n---\n\n### Phase 3: Deep Analysis by Lens\n\nRun the analysis for each selected lens. Every finding must reference a specific element from the model (use element names, not generic statements).\n\n#### Lens: Dependency (`dependency`)\n\nAnalyse how the focus elements structurally need each other:\n\n- **Critical dependencies:** Which links are load-bearing? What breaks if the link is absent?\n- **Direction of dependency:** Which element depends on the other, or is it mutual?\n- **Bottlenecks:** If one element changes (e.g. a new capability is added), which element must change too?\n- **Resilience:** Are there alternative paths that reduce single-point dependency?\n\nOutput format:\n```markdown\n### Riippuvuusanalyysi: [Elementti A] ↔ [Elementti B]\n\n**Kriittiset riippuvuudet:**\n- [elementti] vaatii [toinen elementti] koska ... (lähde: malli-elementti)\n\n**Riippuvuuden suunta:** [yksisuuntainen A→B | molemminpuolinen]\n\n**Pullonkaulat:**\n- ...\n\n**Vaihtoehtoiset polut:**\n- ...\n```\n\n#### Lens: Alignment (`alignment`)\n\nAnalyse coherence and contradictions between the focus elements:\n\n- **Alignment score per link:** Strong \u002F Good \u002F Weak — with justification\n- **Contradictions:** Explicit conflicts between element descriptions or their relationship\n- **Mismatches:** Areas where element A implies something that element B doesn't support\n- **Root cause hypothesis:** Why does the misalignment exist?\n\nOutput format:\n```markdown\n### Yhdenmukaisu­usarvio: [Elementti A] ↔ [Elementti B]\n\n| Linkki | Yhdenmukaisu­us | Perustelu |\n|--------|----------------|-----------|\n| organisation → capability | Weak | Org-rakenne on toiminnallinen, kyvykkyydet ovat asiakkuus­kohtaisia |\n\n**Ristiriidat:**\n- ...\n\n**Juurisyyanalyysi:**\n- ...\n```\n\n#### Lens: Gaps (`gaps`)\n\nIdentify missing links and underdeveloped elements:\n\n- **Missing core links:** Links that should exist (per framework) but are absent from the model\n- **Underdeveloped elements:** Elements with only superficial descriptions or no active links\n- **Consequence of each gap:** What business problem does this gap cause?\n- **Gap severity:** High (blocks strategic objectives) \u002F Medium (slows delivery) \u002F Low (nice to have)\n\nOutput format:\n```markdown\n### Puuteanalyysi: [Elementti A] ↔ [Elementti B]\n\n| Puuttuva linkki | Pitäisi olla | Vaikutus | Vakavuus |\n|----------------|-------------|---------|---------|\n| process → capability | process toteuttaa capability | Prosessit eivät tue strategisia kyvykkyyksiä | High |\n\n**Alikehittyneet elementit:**\n- [elementti]: vain yksi kuvaus, ei aktiivisia linkkejä → ...\n```\n\n#### Lens: Opportunities (`opportunities`)\n\nIdentify where the element pair creates competitive advantage or growth potential:\n\n- **Leverage points:** Where is the element pair unusually strong vs. industry baseline?\n- **Compounding effects:** Where could investing in one element multiply value in the other?\n- **Strategic asymmetry:** What can this company do with this element combination that competitors cannot?\n- **Priority actions:** Top 3 actions to realise the opportunity, with responsible element\n\nOutput format:\n```markdown\n### Mahdollisuudet: [Elementti A] ↔ [Elementti B]\n\n**Vipuvoimapisteet:**\n- ...\n\n**Kerrannaishyödyt:**\n- [elementti A]:n vahvistaminen → vaikuttaa [elementti B]:hen koska ...\n\n**Strateginen epäsymmetria:**\n- ...\n\n**Prioriteettiset toimenpiteet:**\n1. [toimenpide] — vastuullinen elementti: [X] — vaikutus: High\u002FMedium\u002FLow\n2. ...\n3. ...\n```\n\n---\n\n### Phase 4: Generate Pairwise Diagram Input\n\nProduce `\u003Ccompany>-deep-dive-\u003Celements>.txt` in edgy-diagram input format.\n\nInclude only:\n- The focus elements themselves\n- Their direct (1-hop) neighbours that participate in active links\n- All core links between these elements\n\nMark focus elements with `[focus]` tag.\n\nThe TXT file is a human-readable specification — the `edgy_parser.py` does\nnot currently parse `pairwise` layouts, so the agent **generates the .drawio\nXML directly** following the pairwise layout spec in\n`skills\u002Fdocumentation\u002Fedgy-diagram\u002FSKILL.md` (see \"Pairwise Map\" section).\nUse the same `facet` \u002F `elements` \u002F `relationships` structure as other\nedgy-diagram inputs for readability:\n\n```\nfacet: architecture\nfocus: [capability, organisation]\n\nelements:\n  - capability: \"Capability name - Description\" [focus]\n  - organisation: \"Organisation name - Description\" [focus]\n  - process: \"Process name - Description\"   (neighbour via organisation→process→capability)\n\nrelationships:\n  - \"organisation\" -> \"capability\": \"omistaa\"\n  - \"organisation\" -> \"process\": \"suorittaa\"\n  - \"process\" -> \"capability\": \"toteuttaa\"\n```\n\nThen author `\u003Ccompany>-deep-dive-\u003Celements>.drawio` directly as XML following the pairwise layout rules (the generator does not yet support the pairwise layout), include the legend block from the edgy-diagram skill, and lint the file before delivery:\n\n```bash\nG=${EDGY_DIAGRAM_SCRIPTS:-skills\u002Fdocumentation\u002Fedgy-diagram\u002Fscripts}   # installed skills: ~\u002F.claude\u002Fskills\u002Fedgy-diagram\u002Fscripts\npython3 $G\u002Fedgy_lint.py \u003Ccompany>-deep-dive-\u003Celements>.drawio     # 0 errors required\npython3 $G\u002Fedgy_render.py \u003Ccompany>-deep-dive-\u003Celements>.drawio   # SVG (+PNG) preview — look at it before delivery\n```\n\n- Focus elements: `strokeWidth=4` (bold border), same colour as their element type\n- Neighbour elements: normal `strokeWidth=2`\n- Direct core links: solid arrow + verb label\n- 2-hop paths: dashed arrow (`dashed=1`) + intermediate element name as path label\n- Layout: focus element A left column, focus element B right column, neighbours outside both\n\n---\n\n### Phase 5: Deliver and Suggest Next Step\n\n1. Show the complete `\u003Ccompany>-deep-dive-\u003Celements>.md` report.\n2. End with a **\"Seuraava jatkoanalyysi\"** (Next deep-dive) suggestion block:\n\n```markdown\n## Seuraava jatkoanalyysi\n\nTämän analyysin löydösten perusteella suositellaan seuraavaa:\n\n| Elementtipari | Linssi | Perustelu |\n|---------------|--------|-----------|\n| capability × process | gaps | [Puute löydettiin: process→capability-linkki puuttuu] |\n| product × task | alignment | [Löydettiin tuote jolla ei ole task-linkkiä] |\n```\n\nThe suggestion must be grounded in a specific finding from this analysis (reference phase 3 outputs).\n\n---\n\n## Output Template\n\n### Finnish (fi)\n\n```markdown\n# EDGY Syväanalyysi: [Elementti A] × [Elementti B]\n**Yritys:** [Nimi]\n**Linssi:** [dependency | alignment | gaps | opportunities | all]\n**Analysoitu:** [pvm]\n\n---\n\n## Linkkartta\n\n[Phase 2 table — direct links and 2-hop paths]\n\n---\n\n## [Linssi-osio(t)]\n\n[Phase 3 content]\n\n---\n\n## Yhteenveto\n\n[2–3 lausetta päälöydöksistä ja suositellusta toimenpiteestä]\n\n---\n\n## Seuraava jatkoanalyysi\n\n[Phase 5 suggestion table]\n```\n\n### English (en)\n\n```markdown\n# EDGY Deep-Dive: [Element A] × [Element B]\n**Company:** [Name]\n**Lens:** [dependency | alignment | gaps | opportunities | all]\n**Analysed:** [date]\n\n---\n\n## Link Map\n\n[Phase 2 table]\n\n---\n\n## [Lens section(s)]\n\n[Phase 3 content]\n\n---\n\n## Summary\n\n[2–3 sentences on key findings and recommended action]\n\n---\n\n## Next Deep-Dive\n\n[Phase 5 suggestion table]\n```\n\n---\n\n## Quality Gate\n\nBefore delivering, verify:\n- [ ] All focus elements are present in the model (not invented)\n- [ ] Link map contains at least 1 direct or 2-hop link\n- [ ] Every finding references a specific element name from the model\n- [ ] No generic statements (\"the organisation should improve its capabilities\") without specific grounding\n- [ ] Pairwise diagram TXT contains `[focus]` tags on focus elements\n- [ ] `edgy_lint.py` reports 0 errors for the pairwise drawio file\n- [ ] The pairwise diagram was previewed with `edgy_render.py` and the focus\u002Fneighbour layout reads correctly\n- [ ] Next deep-dive suggestion is grounded in a finding from this analysis\n\n## Anti-patterns\n\n- DO NOT analyse elements that are not in the model without noting they are missing\n- DO NOT write generic capability\u002Forganisation advice not grounded in model data\n- DO NOT skip the link map — it is the structural foundation of the analysis\n- DO NOT suggest the same element pair as the next deep-dive (suggest a new pair)\n\n---\n\n## Reference\n\nSee `examples\u002F` for a complete deep-dive example:\n- `examples\u002Fsample-model.json` — Globex Oy EDGY model (from edgy-assessment)\n- `examples\u002Fexpected-deep-dive.md` — capability × organisation, lens=dependency\n","# EDGY Deep-Dive Analysis\n\n## Purpose\n\nThis skill performs a **targeted analysis of a specific EDGY element pair** using\nan existing company EDGY model as context. It traces both direct core links and\nindirect (2-hop) paths between the chosen elements, then analyses their relationship\nthrough the selected lens.\n\nUse this skill when:\n- You have completed an `edgy-assessment` and want to explore a specific element pair in depth\n- The assessment's \"Suggested deep-dive analyses\" section identified a High-priority pair\n- The client wants to understand how, for example, Architecture capabilities are\n  structured relative to the Organisation, or how Products map to customer Tasks\n\n**Prerequisite:** `edgy-assessment` must have been run and produced `\u003Ccompany>-edgy-model.json`.\n\n**This skill produces:**\n- `\u003Ccompany>-deep-dive-\u003Celements>.md` — focused analysis report\n- `\u003Ccompany>-deep-dive-\u003Celements>.txt` — edgy-diagram input (pairwise map)\n- `\u003Ccompany>-deep-dive-\u003Celements>.drawio` — pairwise draw.io diagram\n\n**IMPORTANT:** Produce all output in the language specified by the `language` parameter.\n\n---\n\n## Official 24 EDGY Core Links (reference for path tracing)\n\n\u003C!-- edgy-links:begin format=flat-fi-en -->\n| Source → Target | FI | EN |\n| ----------------- | ---- | ---- |\n| story → purpose | kontekstualisoi | contextualises |\n| content → purpose | ilmaisee | expresses |\n| content → story | välittää | conveys |\n| brand → story | herättää | evokes |\n| brand → purpose | edustaa | represents |\n| capability → asset | vaatii | requires |\n| process → capability | toteuttaa | realises |\n| process → asset | vaatii | requires |\n| product → capability | vaatii | requires |\n| process → product | luo | creates |\n| task → journey | on osa | is part of |\n| task → channel | käyttää | uses |\n| journey → channel | kulkee | traverses |\n| brand → task | tukee | supports |\n| brand → journey | näkyy | appears in |\n| organisation → purpose | tavoittelee | pursues |\n| organisation → story | kirjoittaa | authors |\n| organisation → capability | omistaa | has |\n| organisation → process | suorittaa | performs |\n| product → task | palvelee | serves |\n| product → journey | esiintyy | features in |\n| organisation → brand | rakentaa | builds |\n| organisation → product | valmistaa | makes |\n| product → brand | ilmentää | embodies |\n\u003C!-- edgy-links:end -->\n\n---\n\n## Agent Instructions\n\n### CRITICAL: Read the full instructions before starting\n\nDo not skip phases. Every phase is required to produce a complete, grounded analysis.\n\n---\n\n### Phase 1: Load Context\n\n0. **Validate the model** against the shared schema before reading it:\n   `python3 \u003Cedgy-assessment>\u002Fscripts\u002Fvalidate_edgy_model.py \u003Ccompany>-edgy-model.json` (schema:\n   `skills\u002Farchitecture\u002Fedgy-assessment\u002Fassets\u002Fedgy-model.schema.json`). A\n   model that fails validation is not analysed — ask the user to fix it or to\n   run `edgy-assessment` in `extract-model` mode. Never invent elements that\n   the model does not contain.\n1. Read the `model` file (edgy-model.json). `elements.organisation` is one object (format 1.8)\n   or an array (1.9), and so is `elements.journey` from format 1.10 (one object, or an array of\n   journeys with ids) — treat a single object as a list of one. With several journeys, analyse\n   the ones the focus names, or each in turn; never merge them into one.\n2. Extract the entries for all `focus_elements` from `elements`.\n3. Note the coherence scores from `coherence` for any intersection elements in the focus.\n4. Check `suggested_deep_dives` — if this exact pair was suggested, note its rationale and priority.\n\n**Minimum requirement:** You must extract at least one element description and at least one active core link from the model before proceeding. If the model is missing or malformed, ask the user to run `edgy-assessment` first.\n\n---\n\n### Phase 2: Trace Core-Link Paths\n\nBuild the **link graph** for the focus elements:\n\n#### Step 1 — Direct links (1-hop)\nList every core link from the table above where *both* source and target are in `focus_elements`.\n\nExample for `[\"capability\", \"organisation\"]`:\n- `organisation → capability: has` ✓ (direct)\n\n#### Step 2 — 2-hop paths\nList every path A → X → B (or B → X → A) where A and B are in `focus_elements` and X is any other element.\n\nExample for `[\"capability\", \"organisation\"]`:\n- `organisation → process: performs` AND `process → capability: realises`\n  → path: organisation **→(performs)→** process **→(realises)→** capability\n\n#### Step 3 — Cross-check with active model links\nFrom the model's `core_links` array, mark which of the above links are *active* (present in the model) vs. *theoretical* (in the framework but not observed in this company). An absent link that *should* exist is itself a gap finding.\n\nPresent results as a table:\n\n| Path | Hops | Status | Verb(s) |\n|------|------|--------|---------|\n| organisation → capability | 1 | Active | omistaa |\n| organisation → process → capability | 2 | Partial (process→capability missing) | suorittaa \u002F toteuttaa |\n\n---\n\n### Phase 3: Deep Analysis by Lens\n\nRun the analysis for each selected lens. Every finding must reference a specific element from the model (use element names, not generic statements).\n\n#### Lens: Dependency (`dependency`)\n\nAnalyse how the focus elements structurally need each other:\n\n- **Critical dependencies:** Which links are load-bearing? What breaks if the link is absent?\n- **Direction of dependency:** Which element depends on the other, or is it mutual?\n- **Bottlenecks:** If one element changes (e.g. a new capability is added), which element must change too?\n- **Resilience:** Are there alternative paths that reduce single-point dependency?\n\nOutput format:\n```markdown\n### Riippuvuusanalyysi: [Elementti A] ↔ [Elementti B]\n\n**Kriittiset riippuvuudet:**\n- [elementti] vaatii [toinen elementti] koska ... (lähde: malli-elementti)\n\n**Riippuvuuden suunta:** [yksisuuntainen A→B | molemminpuolinen]\n\n**Pullonkaulat:**\n- ...\n\n**Vaihtoehtoiset polut:**\n- ...\n```\n\n#### Lens: Alignment (`alignment`)\n\nAnalyse coherence and contradictions between the focus elements:\n\n- **Alignment score per link:** Strong \u002F Good \u002F Weak — with justification\n- **Contradictions:** Explicit conflicts between element descriptions or their relationship\n- **Mismatches:** Areas where element A implies something that element B doesn't support\n- **Root cause hypothesis:** Why does the misalignment exist?\n\nOutput format:\n```markdown\n### Yhdenmukaisu­usarvio: [Elementti A] ↔ [Elementti B]\n\n| Linkki | Yhdenmukaisu­us | Perustelu |\n|--------|----------------|-----------|\n| organisation → capability | Weak | Org-rakenne on toiminnallinen, kyvykkyydet ovat asiakkuus­kohtaisia |\n\n**Ristiriidat:**\n- ...\n\n**Juurisyyanalyysi:**\n- ...\n```\n\n#### Lens: Gaps (`gaps`)\n\nIdentify missing links and underdeveloped elements:\n\n- **Missing core links:** Links that should exist (per framework) but are absent from the model\n- **Underdeveloped elements:** Elements with only superficial descriptions or no active links\n- **Consequence of each gap:** What business problem does this gap cause?\n- **Gap severity:** High (blocks strategic objectives) \u002F Medium (slows delivery) \u002F Low (nice to have)\n\nOutput format:\n```markdown\n### Puuteanalyysi: [Elementti A] ↔ [Elementti B]\n\n| Puuttuva linkki | Pitäisi olla | Vaikutus | Vakavuus |\n|----------------|-------------|---------|---------|\n| process → capability | process toteuttaa capability | Prosessit eivät tue strategisia kyvykkyyksiä | High |\n\n**Alikehittyneet elementit:**\n- [elementti]: vain yksi kuvaus, ei aktiivisia linkkejä → ...\n```\n\n#### Lens: Opportunities (`opportunities`)\n\nIdentify where the element pair creates competitive advantage or growth potential:\n\n- **Leverage points:** Where is the element pair unusually strong vs. industry baseline?\n- **Compounding effects:** Where could investing in one element multiply value in the other?\n- **Strategic asymmetry:** What can this company do with this element combination that competitors cannot?\n- **Priority actions:** Top 3 actions to realise the opportunity, with responsible element\n\nOutput format:\n```markdown\n### Mahdollisuudet: [Elementti A] ↔ [Elementti B]\n\n**Vipuvoimapisteet:**\n- ...\n\n**Kerrannaishyödyt:**\n- [elementti A]:n vahvistaminen → vaikuttaa [elementti B]:hen koska ...\n\n**Strateginen epäsymmetria:**\n- ...\n\n**Prioriteettiset toimenpiteet:**\n1. [toimenpide] — vastuullinen elementti: [X] — vaikutus: High\u002FMedium\u002FLow\n2. ...\n3. ...\n```\n\n---\n\n### Phase 4: Generate Pairwise Diagram Input\n\nProduce `\u003Ccompany>-deep-dive-\u003Celements>.txt` in edgy-diagram input format.\n\nInclude only:\n- The focus elements themselves\n- Their direct (1-hop) neighbours that participate in active links\n- All core links between these elements\n\nMark focus elements with `[focus]` tag.\n\nThe TXT file is a human-readable specification — the `edgy_parser.py` does\nnot currently parse `pairwise` layouts, so the agent **generates the .drawio\nXML directly** following the pairwise layout spec in\n`skills\u002Fdocumentation\u002Fedgy-diagram\u002FSKILL.md` (see \"Pairwise Map\" section).\nUse the same `facet` \u002F `elements` \u002F `relationships` structure as other\nedgy-diagram inputs for readability:\n\n```\nfacet: architecture\nfocus: [capability, organisation]\n\nelements:\n  - capability: \"Capability name - Description\" [focus]\n  - organisation: \"Organisation name - Description\" [focus]\n  - process: \"Process name - Description\"   (neighbour via organisation→process→capability)\n\nrelationships:\n  - \"organisation\" -> \"capability\": \"omistaa\"\n  - \"organisation\" -> \"process\": \"suorittaa\"\n  - \"process\" -> \"capability\": \"toteuttaa\"\n```\n\nThen author `\u003Ccompany>-deep-dive-\u003Celements>.drawio` directly as XML following the pairwise layout rules (the generator does not yet support the pairwise layout), include the legend block from the edgy-diagram skill, and lint the file before delivery:\n\n```bash\nG=${EDGY_DIAGRAM_SCRIPTS:-skills\u002Fdocumentation\u002Fedgy-diagram\u002Fscripts}   # installed skills: ~\u002F.claude\u002Fskills\u002Fedgy-diagram\u002Fscripts\npython3 $G\u002Fedgy_lint.py \u003Ccompany>-deep-dive-\u003Celements>.drawio     # 0 errors required\npython3 $G\u002Fedgy_render.py \u003Ccompany>-deep-dive-\u003Celements>.drawio   # SVG (+PNG) preview — look at it before delivery\n```\n\n- Focus elements: `strokeWidth=4` (bold border), same colour as their element type\n- Neighbour elements: normal `strokeWidth=2`\n- Direct core links: solid arrow + verb label\n- 2-hop paths: dashed arrow (`dashed=1`) + intermediate element name as path label\n- Layout: focus element A left column, focus element B right column, neighbours outside both\n\n---\n\n### Phase 5: Deliver and Suggest Next Step\n\n1. Show the complete `\u003Ccompany>-deep-dive-\u003Celements>.md` report.\n2. End with a **\"Seuraava jatkoanalyysi\"** (Next deep-dive) suggestion block:\n\n```markdown\n## Seuraava jatkoanalyysi\n\nTämän analyysin löydösten perusteella suositellaan seuraavaa:\n\n| Elementtipari | Linssi | Perustelu |\n|---------------|--------|-----------|\n| capability × process | gaps | [Puute löydettiin: process→capability-linkki puuttuu] |\n| product × task | alignment | [Löydettiin tuote jolla ei ole task-linkkiä] |\n```\n\nThe suggestion must be grounded in a specific finding from this analysis (reference phase 3 outputs).\n\n---\n\n## Output Template\n\n### Finnish (fi)\n\n```markdown\n# EDGY Syväanalyysi: [Elementti A] × [Elementti B]\n**Yritys:** [Nimi]\n**Linssi:** [dependency | alignment | gaps | opportunities | all]\n**Analysoitu:** [pvm]\n\n---\n\n## Linkkartta\n\n[Phase 2 table — direct links and 2-hop paths]\n\n---\n\n## [Linssi-osio(t)]\n\n[Phase 3 content]\n\n---\n\n## Yhteenveto\n\n[2–3 lausetta päälöydöksistä ja suositellusta toimenpiteestä]\n\n---\n\n## Seuraava jatkoanalyysi\n\n[Phase 5 suggestion table]\n```\n\n### English (en)\n\n```markdown\n# EDGY Deep-Dive: [Element A] × [Element B]\n**Company:** [Name]\n**Lens:** [dependency | alignment | gaps | opportunities | all]\n**Analysed:** [date]\n\n---\n\n## Link Map\n\n[Phase 2 table]\n\n---\n\n## [Lens section(s)]\n\n[Phase 3 content]\n\n---\n\n## Summary\n\n[2–3 sentences on key findings and recommended action]\n\n---\n\n## Next Deep-Dive\n\n[Phase 5 suggestion table]\n```\n\n---\n\n## Quality Gate\n\nBefore delivering, verify:\n- [ ] All focus elements are present in the model (not invented)\n- [ ] Link map contains at least 1 direct or 2-hop link\n- [ ] Every finding references a specific element name from the model\n- [ ] No generic statements (\"the organisation should improve its capabilities\") without specific grounding\n- [ ] Pairwise diagram TXT contains `[focus]` tags on focus elements\n- [ ] `edgy_lint.py` reports 0 errors for the pairwise drawio file\n- [ ] The pairwise diagram was previewed with `edgy_render.py` and the focus\u002Fneighbour layout reads correctly\n- [ ] Next deep-dive suggestion is grounded in a finding from this analysis\n\n## Anti-patterns\n\n- DO NOT analyse elements that are not in the model without noting they are missing\n- DO NOT write generic capability\u002Forganisation advice not grounded in model data\n- DO NOT skip the link map — it is the structural foundation of the analysis\n- DO NOT suggest the same element pair as the next deep-dive (suggest a new pair)\n\n---\n\n## Reference\n\nSee `examples\u002F` for a complete deep-dive example:\n- `examples\u002Fsample-model.json` — Globex Oy EDGY model (from edgy-assessment)\n- `examples\u002Fexpected-deep-dive.md` — capability × organisation, lens=dependency\n",{"name":5,"tags":24,"agents":33,"inputs":38,"outputs":61,"version":69,"category":27,"languages":70,"description":71},[25,26,27,28,29,30,31,32],"edgy","enterprise-design","architecture","analysis","deep-dive","intersection","fi","en",[34,35,36,37],"claude-code","cursor","vibe","generic",[39,43,47,57],{"name":40,"type":41,"description":42},"model","file","edgy-model.json produced by the edgy-assessment skill. Contains all 12 EDGY elements, active core links, coherence scores, and suggested deep-dive analyses for this company.\n",{"name":44,"type":45,"description":46},"focus_elements","array","2–3 EDGY element names to analyse. Use official names: purpose, story, content, capability, asset, process, task, channel, journey, organisation, product, brand. Examples: [\"capability\", \"organisation\"] or [\"task\", \"channel\", \"journey\"]\n",{"name":48,"type":49,"values":50,"default":55,"description":56},"lens","enum",[51,52,53,54,55],"dependency","alignment","gaps","opportunities","all","Analytical lens to apply. dependency   — how the elements need each other; critical dependencies alignment    — coherence between elements; contradictions gaps         — missing links or underdeveloped elements opportunities — competitive advantage or growth potential all          — all four lenses\n",{"name":58,"type":49,"values":59,"default":31,"description":60},"language",[31,32],"Output language. Currently only fi and en are supported (output templates and lens-specific section headers are localised for these two only).\n",[62,65,67],{"type":63,"description":64},"markdown","Focused deep-dive analysis with direct and 2-hop core-link analysis",{"type":41,"description":66},"edgy-diagram-compatible TXT input for pairwise map",{"type":41,"description":68},"draw.io diagram (pairwise layout, focus elements bold-bordered)","1.1.2",[31,32],"Targeted EDGY 23 deep-dive analysis of a specific element pair or facet combination. Requires an existing edgy-model.json produced by the edgy-assessment skill. Analyses the chosen elements through one of four analytical lenses (dependency, alignment, gaps, opportunities) using both direct core links and 2-hop paths. Produces a focused markdown report and a pairwise draw.io diagram.\n","main","511bd269dc3dabd710d5897c5df7681d818a3625","skills\u002Farchitecture\u002Fedgy-deep-dive",0,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills","https:\u002F\u002Fgithub.com\u002FRahola","2026-10-19 17:50:29",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add Rahola\u002Fedgy-skills --skill edgy-deep-dive",{"tool":85,"command":86},"bunx","bunx skills add Rahola\u002Fedgy-skills --skill edgy-deep-dive",{"tool":88,"command":89},"pnpm","pnpm dlx skills add Rahola\u002Fedgy-skills --skill edgy-deep-dive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Farchitecture\u002Fedgy-deep-dive\u002FSKILL.md",true,[93,99],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"examples\u002Fexpected-deep-dive.md","REFERENCE","参考文档",4639,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Farchitecture\u002Fedgy-deep-dive\u002Fexamples\u002Fexpected-deep-dive.md",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"examples\u002Fsample-model.json",9536,"https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Fskills\u002Farchitecture\u002Fedgy-deep-dive\u002Fexamples\u002Fsample-model.json",[104,110,116,122,128,134],{"skillNo":105,"name":106,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M784QCQ9RS33B79PPE4BTGRQ","fx-z","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-z\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M784QA58YX5YDAFM3ZX5TEQQ","fx-y","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-y\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M784Q7B642A6WFJ0X5FBM1EK","fx-x","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-x\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M784Q4AQVCVDAWQPAN1M1VCG","fx-w","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-w\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M784Q239PJGYYCGN0X3AQW1Q","fx-top","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-top\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M784PZD95CXDA4T4PRRFR1BY","fx-plugin","https:\u002F\u002Fgithub.com\u002FRahola\u002Fedgy-skills\u002Fblob\u002Fmain\u002Ftools\u002Ffixtures\u002Fskills\u002Ffx-plugin\u002FSKILL.md",[],[]]