[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FQ50DX0QJQFVZT3ZAN7CH":3,"skill-same:01M70FQ50DX0QJQFVZT3ZAN7CH":71},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M70FQ50DX0QJQFVZT3ZAN7CH","competitive-report-structure",null,"Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcompetitive-report-structure\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"competitive report structure","competitive","report","structure","as","matrix","benchmark","recommendations","assemble","benchmarking","leadership","team","analysis","when","writing","map","landscape","decision","pipeline","alignment","2026-11-10 10:12:30",false,"---\nname: competitive-report-structure\ndescription: Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.\n---\n\n# Competitive Report Structure\n\nUse this skill to assemble scored competitor cards into a decision-grade report.\nThe report must answer three questions for the client: **who do we compete with,\nhow do we compete, and where is our defensible white-space?** Every section\nearns its place by moving toward those answers — cut anything that doesn't.\n\n## When to Activate\n\n- All competitor profile cards from benchmark-methodology are complete and ready to assemble.\n- Need to present competitive findings to a founder, leadership team, or board.\n- The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.\n- Preparing a client deliverable that must be auditable and defensible.\n\n## Client positioning brief (establish first)\n\nBefore assembling the report, establish the client's positioning brief. It\nsupplies:\n\n- **Strategic tension** — the paired axes (e.g., memorability × hireability)\n  that define the client's target white-space. All maps and synthesis resolve\n  back to this tension.\n- **Brand balance** — the intended proportional mix of the client's strategic\n  emphases (e.g., 60% strategy\u002Fevidence, 25% distinctiveness, 15% craft).\n  Every recommendation must be checked against this balance; flag any that\n  would shift it.\n- **Differentiator** — the framing principle for the executive summary and\n  white-space section.\n- **Target quadrant** — where the client intends to sit in the tension map;\n  confirming whether that quadrant is genuinely open is the report's central\n  empirical question.\n\n## Framing principle\n\nThe whole report is organized around the client's strategic tension and\nrecommendations resolve back to the client's deliberate brand balance.\nRecommendations that would break that balance must be flagged against it\nexplicitly — \"this move shifts the balance from X\u002FY\u002FZ toward A\u002FB\u002FC; confirm\nintent.\"\n\n## Report sections\n\n### 1. Executive summary\n3–5 takeaways, decision-first. State the most important findings in plain\nlanguage: where the client is strong, where it's exposed, who occupies its\ntarget white-space, and the top 2–3 moves. Written so a founder\u002FPM reads only\nthis and knows what to do. No methodology here.\n\n### 2. Market landscape & category framing\nDefine the category and map it. Use a **multi-axis map** — at minimum a 2×2\n(e.g., *brand-led \u003C-> capability-led* × *boutique \u003C-> enterprise-scale*), and\nideally the **client's tension plot** from `benchmark-methodology` as the\nheadline map. Place every profiled competitor and the client. The map should\nmake the client's intended position visually obvious and show how crowded (or\nempty) it is.\n\n### 3. Competitor tiers\nOrganize the set into **Direct \u002F Adjacent \u002F Aspirational** (from\n`competitive-platform-analysis`). One short paragraph per tier explaining who's\nin it and why it matters to the client. This sets reader expectations before\nthe detail.\n\n### 4. Benchmarking matrix\nThe full **competitors × dimensions** table — the quantitative spine. Rows =\ncompetitors (grouped by tier), columns = the nine benchmark dimensions (note:\ndimension 9 — strategic tension — has two poles (e.g., Memorability and\nHireability for a brand-studio client; substitute the client's own paired axes);\nrepresent them as two separate sub-columns rather than averaging them). Include\nthe client's own honest self-assessment as a row for contrast. Use a **heatmap**\n(color or symbol scale) so strength\u002Fweakness patterns are scannable. Do **not**\nadd a blended total column — report dimensions separately (per the bias\ncontrols). Call out the columns where the client leads and where it trails.\n\n### 5. Deep dives\n3–5 most instructive competitors in narrative form (from their profile cards).\nChoose for instruction, not ranking: the best exemplar of the target tension\n(high on both poles), the cautionary \"one pole only\" case, the \"competent but\nforgettable\" archetype the client defines against, plus any direct threat. Each\ndeep dive: what they do, what the client should learn, what the client should\navoid.\n\n### 6. White-space & threats\nThe strategic heart. Two parts:\n\n- **White-space:** the position the client can own that rivals don't — argued\n  from the maps and matrix, not asserted. Confirm whether the target quadrant\n  (from the positioning brief) is genuinely open.\n- **Threats:** who\u002Fwhat pressures the client — a rival closing the gap,\n  substitutes (no-code\u002FAI tools, in-house teams, generalist freelancers), or\n  category shifts. Be honest about the client's own risks (e.g., a bold identity\n  reading as un-serious to risk-averse buyers).\n\n### 7. Strategic recommendations\nConcrete, prioritized moves: who the client competes with, how it differentiates,\nand where to invest (offer packaging, evidence\u002Fcase studies, thought leadership,\nbrand sharpening). **Tie every recommendation back to the brand balance from the\npositioning brief** and flag any that would shift it. Sequence by impact ×\neffort.\n\n### 8. Sources \u002F methodology appendix\nThe dimensions, weights, rubrics, the scoped set with tiers, source links per\ncompetitor, and verification notes (asserted vs proven). This is what makes the\nreport auditable and defensible — carry the adversarial citation discipline\nthrough.\n\n## How to present data\n\n- **2×2 \u002F positioning maps** — for landscape and the tension plot. Lead with\n  these; they carry the argument faster than prose.\n- **Heatmap matrix** — for the competitors × dimensions comparison (section 4).\n- **Profile cards** — the source unit feeding deep dives (section 5).\n- **Quadrant callouts** — name who sits in each quadrant explicitly, especially\n  the client's target one.\n- Keep tables scannable; push raw evidence and links to the appendix.\n\n## Decision framework (the report must resolve these)\n\n- **Who do we compete with?** — Name the Direct tier specifically; that's the\n  real fight.\n- **How do we compete?** — State the client's differentiator in one sentence,\n  grounded in the matrix (which dimensions the client owns).\n- **Where are our differentiators defensible?** — Identify the\n  dimensions\u002Fquadrant rivals can't easily copy (the moat), vs. the ones that\n  are table-stakes.\n\n## Trigger questions for the team alignment session\n\nEnd with questions that force decisions, not admiration of the analysis:\n\n- Is the target quadrant truly open, or is a rival already moving in?\n- Which Direct competitor is the sharpest threat in the next 12 months, and\n  what's the counter?\n- Does the brand balance still hold given the landscape — should any emphasis\n  shift?\n- Which dimension where the client trails is worth closing, and which to\n  deliberately concede?\n- What's the one move that most widens distinctiveness *without* costing\n  hireability \u002F credibility?\n\n## Anti-Patterns\n\n- **Leading with methodology.** The executive summary opens with the most important finding, not an explanation of how the benchmark was run. Methodology belongs in the appendix.\n- **Presenting scores without the tension plot.** The 2×2 tension map is the headline artefact. A table of numbers without the map buries the strategic insight.\n- **Omitting the decision framework.** The report must resolve the three questions (who to compete with, how, where the moat is). Leaving these unanswered turns the report into a literature review.\n- **Starting before all profile cards are complete.** Benchmark-methodology must finish before assembly begins. Partial data produces gaps that undermine the heatmap and white-space analysis.\n- **Adding a blended total column to the matrix.** Explicitly excluded — it creates a false composite that obscures the asymmetry the client needs to act on.\n\n## Related Skills\n\n- `benchmark-methodology` — the prerequisite; produces the scored competitor profile cards this skill assembles.\n- `competitive-platform-analysis` — provides the tier structure (Direct \u002F Adjacent \u002F Aspirational) used in Section 3.\n- `brand-discovery` — use to establish the client's positioning brief if it hasn't been defined.\n","# Competitive Report Structure\n\nUse this skill to assemble scored competitor cards into a decision-grade report.\nThe report must answer three questions for the client: **who do we compete with,\nhow do we compete, and where is our defensible white-space?** Every section\nearns its place by moving toward those answers — cut anything that doesn't.\n\n## When to Activate\n\n- All competitor profile cards from benchmark-methodology are complete and ready to assemble.\n- Need to present competitive findings to a founder, leadership team, or board.\n- The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.\n- Preparing a client deliverable that must be auditable and defensible.\n\n## Client positioning brief (establish first)\n\nBefore assembling the report, establish the client's positioning brief. It\nsupplies:\n\n- **Strategic tension** — the paired axes (e.g., memorability × hireability)\n  that define the client's target white-space. All maps and synthesis resolve\n  back to this tension.\n- **Brand balance** — the intended proportional mix of the client's strategic\n  emphases (e.g., 60% strategy\u002Fevidence, 25% distinctiveness, 15% craft).\n  Every recommendation must be checked against this balance; flag any that\n  would shift it.\n- **Differentiator** — the framing principle for the executive summary and\n  white-space section.\n- **Target quadrant** — where the client intends to sit in the tension map;\n  confirming whether that quadrant is genuinely open is the report's central\n  empirical question.\n\n## Framing principle\n\nThe whole report is organized around the client's strategic tension and\nrecommendations resolve back to the client's deliberate brand balance.\nRecommendations that would break that balance must be flagged against it\nexplicitly — \"this move shifts the balance from X\u002FY\u002FZ toward A\u002FB\u002FC; confirm\nintent.\"\n\n## Report sections\n\n### 1. Executive summary\n3–5 takeaways, decision-first. State the most important findings in plain\nlanguage: where the client is strong, where it's exposed, who occupies its\ntarget white-space, and the top 2–3 moves. Written so a founder\u002FPM reads only\nthis and knows what to do. No methodology here.\n\n### 2. Market landscape & category framing\nDefine the category and map it. Use a **multi-axis map** — at minimum a 2×2\n(e.g., *brand-led \u003C-> capability-led* × *boutique \u003C-> enterprise-scale*), and\nideally the **client's tension plot** from `benchmark-methodology` as the\nheadline map. Place every profiled competitor and the client. The map should\nmake the client's intended position visually obvious and show how crowded (or\nempty) it is.\n\n### 3. Competitor tiers\nOrganize the set into **Direct \u002F Adjacent \u002F Aspirational** (from\n`competitive-platform-analysis`). One short paragraph per tier explaining who's\nin it and why it matters to the client. This sets reader expectations before\nthe detail.\n\n### 4. Benchmarking matrix\nThe full **competitors × dimensions** table — the quantitative spine. Rows =\ncompetitors (grouped by tier), columns = the nine benchmark dimensions (note:\ndimension 9 — strategic tension — has two poles (e.g., Memorability and\nHireability for a brand-studio client; substitute the client's own paired axes);\nrepresent them as two separate sub-columns rather than averaging them). Include\nthe client's own honest self-assessment as a row for contrast. Use a **heatmap**\n(color or symbol scale) so strength\u002Fweakness patterns are scannable. Do **not**\nadd a blended total column — report dimensions separately (per the bias\ncontrols). Call out the columns where the client leads and where it trails.\n\n### 5. Deep dives\n3–5 most instructive competitors in narrative form (from their profile cards).\nChoose for instruction, not ranking: the best exemplar of the target tension\n(high on both poles), the cautionary \"one pole only\" case, the \"competent but\nforgettable\" archetype the client defines against, plus any direct threat. Each\ndeep dive: what they do, what the client should learn, what the client should\navoid.\n\n### 6. White-space & threats\nThe strategic heart. Two parts:\n\n- **White-space:** the position the client can own that rivals don't — argued\n  from the maps and matrix, not asserted. Confirm whether the target quadrant\n  (from the positioning brief) is genuinely open.\n- **Threats:** who\u002Fwhat pressures the client — a rival closing the gap,\n  substitutes (no-code\u002FAI tools, in-house teams, generalist freelancers), or\n  category shifts. Be honest about the client's own risks (e.g., a bold identity\n  reading as un-serious to risk-averse buyers).\n\n### 7. Strategic recommendations\nConcrete, prioritized moves: who the client competes with, how it differentiates,\nand where to invest (offer packaging, evidence\u002Fcase studies, thought leadership,\nbrand sharpening). **Tie every recommendation back to the brand balance from the\npositioning brief** and flag any that would shift it. Sequence by impact ×\neffort.\n\n### 8. Sources \u002F methodology appendix\nThe dimensions, weights, rubrics, the scoped set with tiers, source links per\ncompetitor, and verification notes (asserted vs proven). This is what makes the\nreport auditable and defensible — carry the adversarial citation discipline\nthrough.\n\n## How to present data\n\n- **2×2 \u002F positioning maps** — for landscape and the tension plot. Lead with\n  these; they carry the argument faster than prose.\n- **Heatmap matrix** — for the competitors × dimensions comparison (section 4).\n- **Profile cards** — the source unit feeding deep dives (section 5).\n- **Quadrant callouts** — name who sits in each quadrant explicitly, especially\n  the client's target one.\n- Keep tables scannable; push raw evidence and links to the appendix.\n\n## Decision framework (the report must resolve these)\n\n- **Who do we compete with?** — Name the Direct tier specifically; that's the\n  real fight.\n- **How do we compete?** — State the client's differentiator in one sentence,\n  grounded in the matrix (which dimensions the client owns).\n- **Where are our differentiators defensible?** — Identify the\n  dimensions\u002Fquadrant rivals can't easily copy (the moat), vs. the ones that\n  are table-stakes.\n\n## Trigger questions for the team alignment session\n\nEnd with questions that force decisions, not admiration of the analysis:\n\n- Is the target quadrant truly open, or is a rival already moving in?\n- Which Direct competitor is the sharpest threat in the next 12 months, and\n  what's the counter?\n- Does the brand balance still hold given the landscape — should any emphasis\n  shift?\n- Which dimension where the client trails is worth closing, and which to\n  deliberately concede?\n- What's the one move that most widens distinctiveness *without* costing\n  hireability \u002F credibility?\n\n## Anti-Patterns\n\n- **Leading with methodology.** The executive summary opens with the most important finding, not an explanation of how the benchmark was run. Methodology belongs in the appendix.\n- **Presenting scores without the tension plot.** The 2×2 tension map is the headline artefact. A table of numbers without the map buries the strategic insight.\n- **Omitting the decision framework.** The report must resolve the three questions (who to compete with, how, where the moat is). Leaving these unanswered turns the report into a literature review.\n- **Starting before all profile cards are complete.** Benchmark-methodology must finish before assembly begins. Partial data produces gaps that undermine the heatmap and white-space analysis.\n- **Adding a blended total column to the matrix.** Explicitly excluded — it creates a false composite that obscures the asymmetry the client needs to act on.\n\n## Related Skills\n\n- `benchmark-methodology` — the prerequisite; produces the scored competitor profile cards this skill assembles.\n- `competitive-platform-analysis` — provides the tier structure (Direct \u002F Adjacent \u002F Aspirational) used in Section 3.\n- `brand-discovery` — use to establish the client's positioning brief if it hasn't been defined.\n",{"name":5,"description":7},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcompetitive-report-structure",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill competitive-report-structure",{"tool":63,"command":64},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill competitive-report-structure",{"tool":66,"command":67},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill competitive-report-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcompetitive-report-structure\u002FSKILL.md",true,[],[72,80,88,95,102,109],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":87},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":87},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"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":87},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]