[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EQPWJ2SWDAFJEHPTJPHPJS":3,"skill-same:01M6EQPWJ2SWDAFJEHPTJPHPJS":63},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6EQPWJ2SWDAFJEHPTJPHPJS","delivery-factory",null,"Use when the user wants to produce all deliverables for an SAP Activate phase in one orchestrated run. This is the factory — it chains skills, dispatches agents in parallel, collects artifacts, and produces a phase-complete deliverable package with quality scoring.","vigneshbarani24\u002Fsap-superpowers","vigneshbarani24","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20842962?v=4","01M6EQKRW2KZ2M0H75J985XGDX","Vignesh Barani Sivakumar","01M6EQKS0E6EWFSXP4XWK6Y760",11,"MIT","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Fdelivery-factory\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"delivery factory","delivery","factory","use","it","quality scoring","complete","sap","scoring","activate","run","user","quality","parallel","package","produce","artifacts","2026-11-10 10:12:30",false,"---\nname: delivery-factory\ndescription: Use when the user wants to produce all deliverables for an SAP Activate phase in one orchestrated run. This is the factory — it chains skills, dispatches agents in parallel, collects artifacts, and produces a phase-complete deliverable package with quality scoring.\n---\n\n# SAP Delivery Factory\n\nThis skill orchestrates the production of **all deliverables for an SAP Activate phase** in a single coordinated run. It is not a skill — it is a factory that invokes skills, manages their inputs\u002Foutputs, tracks deliverable status, and scores quality.\n\n**What makes this different:** Individual skills produce individual artifacts. The factory produces a **complete, cross-referenced, quality-scored deliverable package** — what a consulting firm bills $50K-$500K to create manually.\n\n## Iron Laws\n\n1. **EVERY PHASE HAS A MANDATORY DELIVERABLE SET.** You cannot mark a phase complete with missing deliverables. The factory knows exactly what each phase requires — no cherry-picking, no \"we'll do that later.\"\n\n2. **DELIVERABLES CHAIN — OUTPUT OF ONE IS INPUT TO THE NEXT.** The project charter feeds estimation. Estimation feeds architecture. Architecture feeds development. The factory manages these dependencies automatically.\n\n3. **QUALITY IS SCORED, NOT ASSUMED.** Every deliverable gets a maturity score (L1-L5). The factory reports aggregate quality per phase. You ship when quality meets the threshold — not when you run out of time.\n\n4. **CONTEXT FLOWS ACROSS SKILLS.** Industry, country, SAP version, project scope — set once, applied everywhere. A retail project in Germany gets different templates than a pharma project in India.\n\n5. **THE FACTORY NEVER PRODUCES EMPTY TEMPLATES.** Templates pre-filled with project context, industry defaults, country-specific regulatory items, and SAP version-appropriate recommendations. The consultant refines — they don't start from blank.\n\n## Phase Pipelines\n\n### DISCOVER Phase\n**Command:** `\u002Fsap-deliver discover`\n**Duration:** 1-2 weeks equivalent\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| D1 | Project Charter | `project-kickoff` | — |\n| D2 | Stakeholder Map & RACI | `project-kickoff` | — |\n| D3 | Requirements Document | `deep-interview` | — |\n| D4 | Risk Register (initial) | `project-kickoff` | — |\n| D5 | High-Level Scope | `brainstorming` | `sap-architect` |\n\n**Dependency chain:** D1 → D2 → D3 → D4 → D5\n**Phase gate:** All 5 deliverables at L2+ quality. Stakeholder sign-off on scope.\n\n### PREPARE Phase\n**Command:** `\u002Fsap-deliver prepare`\n**Prerequisites:** DISCOVER phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| P1 | Effort Estimate (WBS) | `estimation` | `sap-estimator` |\n| P2 | Solution Architecture | `solution-architecture` | `sap-architect` |\n| P3 | Change Management Plan | `change-management` | — |\n| P4 | Business Case \u002F ROI | `value-advisory` | `sap-value-calculator` |\n| P5 | Project Plan (timeline) | `estimation` | — |\n\n**Dependency chain:** P1 ∥ P2 (parallel) → P3 → P4 → P5\n**Phase gate:** All 5 deliverables at L3+ quality. Budget approved.\n\n### EXPLORE Phase\n**Command:** `\u002Fsap-deliver explore`\n**Prerequisites:** PREPARE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| E1 | Fit\u002FGap Analysis Matrix | `fit-gap-analysis` | Module consultants (parallel) |\n| E2 | Process Design Documents (per module) | `process-design` | `sap-process-modeler` |\n| E3 | Functional Specifications | `deep-interview` + module skills | `sap-doc-generator` |\n| E4 | Data Migration Strategy | `data-migration` | `sap-data-analyst` |\n| E5 | Test Strategy | `testing-strategy` | `sap-test-designer` |\n| E6 | Integration Architecture | `solution-architecture` | `sap-architect` |\n\n**Dependency chain:** E1 → E2 → E3, and E4 ∥ E5 ∥ E6 (parallel)\n**Phase gate:** All gaps resolved or accepted. Functional specs signed off.\n\n### REALIZE Phase\n**Command:** `\u002Fsap-deliver realize`\n**Prerequisites:** EXPLORE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| R1 | Technical Specifications | `program-to-spec` or `code-generation` | `sap-doc-generator` |\n| R2 | Developed Objects (code) | `autopilot` | Full team (parallel) |\n| R3 | Unit Test Results | `self-correcting-loop` | `sap-test-designer` |\n| R4 | Code Review Reports | `code-review` | `sap-reviewer`, `sap-security-auditor` |\n| R5 | SIT Test Scripts & Results | `testing-strategy` | `sap-test-designer` |\n| R6 | Training Materials | module skills | `sap-doc-generator` |\n\n**Dependency chain:** R1 → R2 → R3 → R4 → R5 ∥ R6\n**Phase gate:** All code ATC-clean. SIT passed. Training materials reviewed.\n\n### DEPLOY Phase\n**Command:** `\u002Fsap-deliver deploy`\n**Prerequisites:** REALIZE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| Y1 | Data Migration Plan & Results | `data-migration` | `sap-data-analyst` |\n| Y2 | Cutover Runbook | `cutover-planning` | — |\n| Y3 | Go-Live Readiness Assessment | `go-live-readiness` | Full team (parallel) |\n| Y4 | UAT Results & Sign-Off | `testing-strategy` | `sap-test-designer` |\n| Y5 | Transport Release Log | `transport-release` | — |\n\n**Dependency chain:** Y1 → Y2 → Y4 → Y3 → Y5\n**Phase gate:** Go\u002FNo-Go decision GREEN. All transports imported.\n\n### RUN Phase\n**Command:** `\u002Fsap-deliver run`\n**Prerequisites:** DEPLOY phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| N1 | Hypercare Plan | `hypercare` | — |\n| N2 | Daily Status Reports | `hypercare` | — |\n| N3 | Value Realization Report | `value-advisory` | `sap-value-calculator` |\n| N4 | Lessons Learned | `hypercare` | — |\n| N5 | Knowledge Transfer Log | `hypercare` | `sap-doc-generator` |\n\n**Phase gate:** Hypercare exit criteria met. Knowledge transferred.\n\n## Quality Scoring\n\nEvery deliverable is scored on a 5-level maturity model:\n\n| Level | Name | Definition | Evidence |\n|-------|------|-----------|----------|\n| **L1** | Draft | Structure created, sections identified, placeholders present | File exists with correct structure |\n| **L2** | Working | Content filled for all sections, no placeholders remaining | All sections have substantive content |\n| **L3** | Reviewed | Peer reviewed, gaps identified and resolved | Review comments addressed |\n| **L4** | Approved | Client\u002Fstakeholder sign-off ready | Meets all hard gate criteria |\n| **L5** | Baselined | Signed off, version-controlled, change-managed | Sign-off record exists |\n\n**Phase completion thresholds:**\n- DISCOVER: All deliverables at L2+\n- PREPARE: All deliverables at L3+\n- EXPLORE: All deliverables at L3+\n- REALIZE: All deliverables at L4+\n- DEPLOY: All deliverables at L4+\n- RUN: All deliverables at L3+\n\n## Context Injection\n\nThe factory injects project context into every deliverable:\n\n```\nPROJECT CONTEXT (set once, used everywhere)\n═══════════════════════════════════════════\nClient:       [Client name]\nProject:      [Project name]\nSAP Version:  [From .sap-superpowers\u002Fconfig.json]\nABAP Release: [From config]\nIndustry:     [Loads industry\u002F{name}.md]\nCountry:      [Loads country\u002F{name}.md]\nModules:      [In-scope SAP modules]\nTimeline:     [Project start → go-live]\nTeam Size:    [Number of consultants]\n```\n\nIndustry context auto-populates:\n- Module-specific processes relevant to the industry\n- Regulatory requirements for the country\n- Common customizations for the industry\n- Risk patterns typical for the industry\u002Fcountry combination\n\n## Factory Status Report\n\n```\nSAP DELIVERY FACTORY — PROJECT STATUS\n═══════════════════════════════════════\nProject: [Name] | Client: [Name]\nIndustry: [Name] | Country: [Name]\nSAP: [Version] | Release: [ABAP release]\n\nPHASE STATUS\n────────────\n[✅] DISCOVER  — 5\u002F5 deliverables (avg L3.2)\n[✅] PREPARE   — 5\u002F5 deliverables (avg L3.8)\n[?] EXPLORE   — 3\u002F6 deliverables (avg L2.5)  ← CURRENT\n[ ] REALIZE   — 0\u002F6 deliverables\n[ ] DEPLOY    — 0\u002F5 deliverables\n[ ] RUN       — 0\u002F5 deliverables\n\nDELIVERABLE DETAIL (EXPLORE)\n────────────────────────────\n[L3 ✅] E1 Fit\u002FGap Matrix\n[L3 ✅] E2 Process Designs (MM, SD, FI)\n[L2 ?] E3 Functional Specifications — 4\u002F7 modules complete\n[L1 ⏳] E4 Data Migration Strategy — draft started\n[ ] E5 Test Strategy\n[ ] E6 Integration Architecture\n\nNEXT ACTION: Complete E3 (functional specs for PP, PM, QM)\n```\n\n## Verification\n\nThis skill is complete when:\n- [ ] All deliverables for the target phase are produced\n- [ ] Each deliverable meets the phase quality threshold\n- [ ] Cross-references between deliverables are consistent\n- [ ] Factory status report produced\n- [ ] Next phase prerequisites documented\n\n## Cross-References\n\n- Every skill in `skills\u002Fconsulting\u002F` and `skills\u002Fdelivery\u002F` — invoked by the factory\n- Every agent in `agents\u002F` — dispatched by the factory\n- `industry\u002F` files — loaded for context injection\n- `country\u002F` files — loaded for regulatory context\n- `accelerators\u002F` — pre-built solution packages that fast-track specific phases\n","# SAP Delivery Factory\n\nThis skill orchestrates the production of **all deliverables for an SAP Activate phase** in a single coordinated run. It is not a skill — it is a factory that invokes skills, manages their inputs\u002Foutputs, tracks deliverable status, and scores quality.\n\n**What makes this different:** Individual skills produce individual artifacts. The factory produces a **complete, cross-referenced, quality-scored deliverable package** — what a consulting firm bills $50K-$500K to create manually.\n\n## Iron Laws\n\n1. **EVERY PHASE HAS A MANDATORY DELIVERABLE SET.** You cannot mark a phase complete with missing deliverables. The factory knows exactly what each phase requires — no cherry-picking, no \"we'll do that later.\"\n\n2. **DELIVERABLES CHAIN — OUTPUT OF ONE IS INPUT TO THE NEXT.** The project charter feeds estimation. Estimation feeds architecture. Architecture feeds development. The factory manages these dependencies automatically.\n\n3. **QUALITY IS SCORED, NOT ASSUMED.** Every deliverable gets a maturity score (L1-L5). The factory reports aggregate quality per phase. You ship when quality meets the threshold — not when you run out of time.\n\n4. **CONTEXT FLOWS ACROSS SKILLS.** Industry, country, SAP version, project scope — set once, applied everywhere. A retail project in Germany gets different templates than a pharma project in India.\n\n5. **THE FACTORY NEVER PRODUCES EMPTY TEMPLATES.** Templates pre-filled with project context, industry defaults, country-specific regulatory items, and SAP version-appropriate recommendations. The consultant refines — they don't start from blank.\n\n## Phase Pipelines\n\n### DISCOVER Phase\n**Command:** `\u002Fsap-deliver discover`\n**Duration:** 1-2 weeks equivalent\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| D1 | Project Charter | `project-kickoff` | — |\n| D2 | Stakeholder Map & RACI | `project-kickoff` | — |\n| D3 | Requirements Document | `deep-interview` | — |\n| D4 | Risk Register (initial) | `project-kickoff` | — |\n| D5 | High-Level Scope | `brainstorming` | `sap-architect` |\n\n**Dependency chain:** D1 → D2 → D3 → D4 → D5\n**Phase gate:** All 5 deliverables at L2+ quality. Stakeholder sign-off on scope.\n\n### PREPARE Phase\n**Command:** `\u002Fsap-deliver prepare`\n**Prerequisites:** DISCOVER phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| P1 | Effort Estimate (WBS) | `estimation` | `sap-estimator` |\n| P2 | Solution Architecture | `solution-architecture` | `sap-architect` |\n| P3 | Change Management Plan | `change-management` | — |\n| P4 | Business Case \u002F ROI | `value-advisory` | `sap-value-calculator` |\n| P5 | Project Plan (timeline) | `estimation` | — |\n\n**Dependency chain:** P1 ∥ P2 (parallel) → P3 → P4 → P5\n**Phase gate:** All 5 deliverables at L3+ quality. Budget approved.\n\n### EXPLORE Phase\n**Command:** `\u002Fsap-deliver explore`\n**Prerequisites:** PREPARE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| E1 | Fit\u002FGap Analysis Matrix | `fit-gap-analysis` | Module consultants (parallel) |\n| E2 | Process Design Documents (per module) | `process-design` | `sap-process-modeler` |\n| E3 | Functional Specifications | `deep-interview` + module skills | `sap-doc-generator` |\n| E4 | Data Migration Strategy | `data-migration` | `sap-data-analyst` |\n| E5 | Test Strategy | `testing-strategy` | `sap-test-designer` |\n| E6 | Integration Architecture | `solution-architecture` | `sap-architect` |\n\n**Dependency chain:** E1 → E2 → E3, and E4 ∥ E5 ∥ E6 (parallel)\n**Phase gate:** All gaps resolved or accepted. Functional specs signed off.\n\n### REALIZE Phase\n**Command:** `\u002Fsap-deliver realize`\n**Prerequisites:** EXPLORE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| R1 | Technical Specifications | `program-to-spec` or `code-generation` | `sap-doc-generator` |\n| R2 | Developed Objects (code) | `autopilot` | Full team (parallel) |\n| R3 | Unit Test Results | `self-correcting-loop` | `sap-test-designer` |\n| R4 | Code Review Reports | `code-review` | `sap-reviewer`, `sap-security-auditor` |\n| R5 | SIT Test Scripts & Results | `testing-strategy` | `sap-test-designer` |\n| R6 | Training Materials | module skills | `sap-doc-generator` |\n\n**Dependency chain:** R1 → R2 → R3 → R4 → R5 ∥ R6\n**Phase gate:** All code ATC-clean. SIT passed. Training materials reviewed.\n\n### DEPLOY Phase\n**Command:** `\u002Fsap-deliver deploy`\n**Prerequisites:** REALIZE phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| Y1 | Data Migration Plan & Results | `data-migration` | `sap-data-analyst` |\n| Y2 | Cutover Runbook | `cutover-planning` | — |\n| Y3 | Go-Live Readiness Assessment | `go-live-readiness` | Full team (parallel) |\n| Y4 | UAT Results & Sign-Off | `testing-strategy` | `sap-test-designer` |\n| Y5 | Transport Release Log | `transport-release` | — |\n\n**Dependency chain:** Y1 → Y2 → Y4 → Y3 → Y5\n**Phase gate:** Go\u002FNo-Go decision GREEN. All transports imported.\n\n### RUN Phase\n**Command:** `\u002Fsap-deliver run`\n**Prerequisites:** DEPLOY phase complete\n**Deliverables produced:**\n\n| # | Deliverable | Skill Invoked | Agents Dispatched |\n|---|-------------|---------------|-------------------|\n| N1 | Hypercare Plan | `hypercare` | — |\n| N2 | Daily Status Reports | `hypercare` | — |\n| N3 | Value Realization Report | `value-advisory` | `sap-value-calculator` |\n| N4 | Lessons Learned | `hypercare` | — |\n| N5 | Knowledge Transfer Log | `hypercare` | `sap-doc-generator` |\n\n**Phase gate:** Hypercare exit criteria met. Knowledge transferred.\n\n## Quality Scoring\n\nEvery deliverable is scored on a 5-level maturity model:\n\n| Level | Name | Definition | Evidence |\n|-------|------|-----------|----------|\n| **L1** | Draft | Structure created, sections identified, placeholders present | File exists with correct structure |\n| **L2** | Working | Content filled for all sections, no placeholders remaining | All sections have substantive content |\n| **L3** | Reviewed | Peer reviewed, gaps identified and resolved | Review comments addressed |\n| **L4** | Approved | Client\u002Fstakeholder sign-off ready | Meets all hard gate criteria |\n| **L5** | Baselined | Signed off, version-controlled, change-managed | Sign-off record exists |\n\n**Phase completion thresholds:**\n- DISCOVER: All deliverables at L2+\n- PREPARE: All deliverables at L3+\n- EXPLORE: All deliverables at L3+\n- REALIZE: All deliverables at L4+\n- DEPLOY: All deliverables at L4+\n- RUN: All deliverables at L3+\n\n## Context Injection\n\nThe factory injects project context into every deliverable:\n\n```\nPROJECT CONTEXT (set once, used everywhere)\n═══════════════════════════════════════════\nClient:       [Client name]\nProject:      [Project name]\nSAP Version:  [From .sap-superpowers\u002Fconfig.json]\nABAP Release: [From config]\nIndustry:     [Loads industry\u002F{name}.md]\nCountry:      [Loads country\u002F{name}.md]\nModules:      [In-scope SAP modules]\nTimeline:     [Project start → go-live]\nTeam Size:    [Number of consultants]\n```\n\nIndustry context auto-populates:\n- Module-specific processes relevant to the industry\n- Regulatory requirements for the country\n- Common customizations for the industry\n- Risk patterns typical for the industry\u002Fcountry combination\n\n## Factory Status Report\n\n```\nSAP DELIVERY FACTORY — PROJECT STATUS\n═══════════════════════════════════════\nProject: [Name] | Client: [Name]\nIndustry: [Name] | Country: [Name]\nSAP: [Version] | Release: [ABAP release]\n\nPHASE STATUS\n────────────\n[✅] DISCOVER  — 5\u002F5 deliverables (avg L3.2)\n[✅] PREPARE   — 5\u002F5 deliverables (avg L3.8)\n[?] EXPLORE   — 3\u002F6 deliverables (avg L2.5)  ← CURRENT\n[ ] REALIZE   — 0\u002F6 deliverables\n[ ] DEPLOY    — 0\u002F5 deliverables\n[ ] RUN       — 0\u002F5 deliverables\n\nDELIVERABLE DETAIL (EXPLORE)\n────────────────────────────\n[L3 ✅] E1 Fit\u002FGap Matrix\n[L3 ✅] E2 Process Designs (MM, SD, FI)\n[L2 ?] E3 Functional Specifications — 4\u002F7 modules complete\n[L1 ⏳] E4 Data Migration Strategy — draft started\n[ ] E5 Test Strategy\n[ ] E6 Integration Architecture\n\nNEXT ACTION: Complete E3 (functional specs for PP, PM, QM)\n```\n\n## Verification\n\nThis skill is complete when:\n- [ ] All deliverables for the target phase are produced\n- [ ] Each deliverable meets the phase quality threshold\n- [ ] Cross-references between deliverables are consistent\n- [ ] Factory status report produced\n- [ ] Next phase prerequisites documented\n\n## Cross-References\n\n- Every skill in `skills\u002Fconsulting\u002F` and `skills\u002Fdelivery\u002F` — invoked by the factory\n- Every agent in `agents\u002F` — dispatched by the factory\n- `industry\u002F` files — loaded for context injection\n- `country\u002F` files — loaded for regulatory context\n- `accelerators\u002F` — pre-built solution packages that fast-track specific phases\n",{"name":5,"description":7},"main","cf5d032baea1657808fa74369439ea7e9c7e0a20","skills\u002Fmeta\u002Fdelivery-factory",3,"https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers","https:\u002F\u002Fsap-superpowers.vercel.app\u002F","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24","2026-08-23 17:03:43",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add vigneshbarani24\u002Fsap-superpowers --skill delivery-factory",{"tool":55,"command":56},"bunx","bunx skills add vigneshbarani24\u002Fsap-superpowers --skill delivery-factory",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vigneshbarani24\u002Fsap-superpowers --skill delivery-factory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fmeta\u002Fdelivery-factory\u002FSKILL.md",true,[],[64,90,97,106,115,123],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":36},"01M6EQTMCBV605ETS5WWEQX209","s4hana-migration","Use when advising on S\u002F4HANA migration approach, assessing greenfield vs brownfield vs selective data transition options, analyzing custom code impact, reviewing simplification items, or building a migration business case or timeline.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fs4hana-migration\u002FSKILL.md",[],[71,72,73,74,75,76,77,78,79,80,81,82,22,83,84,85,86,87,88,89],"migration","s4hana migration","data","case","impact","discover","simplification","project","brownfield","options","business case","project manager","business","technical","architect","timeline","analyzing","code","prepare",{"skillNo":91,"name":92,"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":93,"categories":94,"keywords":95,"publishedAt":36},"01M6EQTGJHSYYQDMBJY0APE19X","rise-licensing","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Frise-licensing\u002FSKILL.md",[],[96],"rise licensing",{"skillNo":98,"name":99,"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":100,"categories":101,"keywords":102,"publishedAt":36},"01M6EQTCVAJPYQ7A8SA49A1Y72","joule-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fjoule-strategy\u002FSKILL.md",[],[103,104,105],"joule strategy","joule","strategy",{"skillNo":107,"name":108,"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":109,"categories":110,"keywords":111,"publishedAt":36},"01M6EQTA7RMJ6RNFDTK1E2E9YY","clean-core-strategy","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Fclean-core-strategy\u002FSKILL.md",[],[112,113,114,105],"clean core strategy","clean","core",{"skillNo":116,"name":117,"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":118,"categories":119,"keywords":120,"publishedAt":36},"01M6EQT6QCR8MJ7J62ZP8WZ578","activate-methodology","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002Factivate-methodology\u002FSKILL.md",[],[121,28,122],"methodology","activate methodology",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":36},"01M6EQT3XFHC6Y2F0EWQ62PHSR","strategic","strategic skills category for SAP Superpowers. Contains 5 sub-skills.","https:\u002F\u002Fgithub.com\u002Fvigneshbarani24\u002Fsap-superpowers\u002Fblob\u002Fmain\u002Fskills\u002Fstrategic\u002FSKILL.md",[],[125,130,26],"superpowers"]