[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730EGJY3SSACP1THJRE2V24":3,"skill-same:01M730EGJY3SSACP1THJRE2V24":62},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M730EGJY3SSACP1THJRE2V24","launch-strategy",null,"When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.","ciciliaETH\u002Fclaude-skills","ciciliaETH","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F94572860?v=4","01M72Z3SEH31MEG7M94G85GE0V","cicilia_eth","01M72Z3SF42XENX7AMJVA7SCQX",0,"MIT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Flaunch-strategy\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"launch-strategy\"\ndescription: \"When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Launch Strategy\n\nYou are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n→ See references\u002Flaunch-frameworks-and-checklists.md for details\n\n## Task-Specific Questions\n\n1. What are you launching? (New product, major feature, minor update)\n2. What's your current audience size and engagement?\n3. What owned channels do you have? (Email list size, blog traffic, community)\n4. What's your timeline for launch?\n5. Have you launched before? What worked\u002Fdidn't work?\n6. Are you considering Product Hunt? What's your preparation status?\n\n---\n\n## Proactive Triggers\n\nProactively offer launch planning when:\n\n1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.\n2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.\n3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.\n4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).\n5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |\n| ORB Channel Map | Table | Owned\u002FRented\u002FBorrowed channel strategy with tactics per channel |\n| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |\n| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |\n| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |\n\n---\n\n## Communication\n\nLaunch plans should be concrete, time-bound, and channel-specific — no vague \"post on social media\" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.\n\n---\n\n## Related Skills\n\n- **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.\n- **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.\n- **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.\n- **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.\n- **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.\n- **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.\n","# Launch Strategy\n\nYou are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.\n\n## Before Starting\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\n---\n\n## Core Philosophy\n→ See references\u002Flaunch-frameworks-and-checklists.md for details\n\n## Task-Specific Questions\n\n1. What are you launching? (New product, major feature, minor update)\n2. What's your current audience size and engagement?\n3. What owned channels do you have? (Email list size, blog traffic, community)\n4. What's your timeline for launch?\n5. Have you launched before? What worked\u002Fdidn't work?\n6. Are you considering Product Hunt? What's your preparation status?\n\n---\n\n## Proactive Triggers\n\nProactively offer launch planning when:\n\n1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.\n2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.\n3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.\n4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).\n5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.\n\n---\n\n## Output Artifacts\n\n| Artifact | Format | Description |\n|----------|--------|-------------|\n| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |\n| ORB Channel Map | Table | Owned\u002FRented\u002FBorrowed channel strategy with tactics per channel |\n| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |\n| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |\n| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |\n\n---\n\n## Communication\n\nLaunch plans should be concrete, time-bound, and channel-specific — no vague \"post on social media\" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.\n\n---\n\n## Related Skills\n\n- **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.\n- **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.\n- **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.\n- **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.\n- **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.\n- **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","04d625a73841ac3f69c0d6ab4a7308680faffe02","marketing-skill\u002Fskills\u002Flaunch-strategy","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002FciciliaETH","web3 dev, blockchain enthusiast, token reviewer, all about telegram bot.","2026-05-17 05:17:16",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ciciliaETH\u002Fclaude-skills --skill launch-strategy",{"tool":42,"command":43},"bunx","bunx skills add ciciliaETH\u002Fclaude-skills --skill launch-strategy",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ciciliaETH\u002Fclaude-skills --skill launch-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Flaunch-strategy\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Flaunch-frameworks-and-checklists.md","REFERENCE","参考文档",10860,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Flaunch-strategy\u002Freferences\u002Flaunch-frameworks-and-checklists.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Flaunch_readiness_scorer.py","SCRIPT","脚本",12292,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Flaunch-strategy\u002Fscripts\u002Flaunch_readiness_scorer.py",[63,70,77,84,89,94],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M730RQEKV70CXBH2TQF045GT","ra-qm-skills","12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017\u002F745, FDA 510(k)\u002FPMA, ISO 27001 ISMS, GDPR\u002FDSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fra-qm-skills\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M730QTT31DKCCZC573H22GX6","iso42001-specialist","ISO\u002FIEC 42001:2023 AI Management System (AIMS) specialist for compliance teams running internal audits. Three decisions: (1) Where are the gaps against Clauses 4-10 and what do we close first? (2) What goes in the AI risk register and which Annex A controls treat each risk? (3) What's the 12-month internal audit plan that satisfies Clause 9.2? Use when preparing for certification, scoping internal audit cycles, or onboarding AI systems into an existing ISMS (27001) \u002F QMS (13485) program. NOT an executive AI strategy skill (see chief-ai-officer-advisor). NOT EU AI Act compliance (see compliance-team-eu-ai-act).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M730Q40HCJJ97V6HGDF4FPS0","eu-ai-act-specialist","EU AI Act (Regulation (EU) 2024\u002F1689) operational compliance for compliance teams. Three Article-level decisions: (1) What's the risk tier of this AI system — prohibited (Art. 5), high-risk (Art. 6 + Annex III), limited-risk (Art. 50), or minimal-risk? (2) For high-risk systems, what's the Article 43 conformity assessment route (Module A internal control vs Module H full QMS + notified body) and what goes in the Annex IV technical documentation? (3) Per organizational role (provider \u002F deployer \u002F importer \u002F distributor \u002F authorized representative), what are the active obligations and deadlines? Use during AI system intake review, when planning conformity assessment, or when scoping deployer obligations. Cites Articles + Annexes for every output. NOT executive AI strategy (see chief-ai-officer-advisor). NOT a legal substitute.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":85,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M730PQWQ9N9FWV52Y14A1NJT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-iso42001\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":90,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M730PFX71VE2Q2HFHNYRDKQX","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-eu-ai-act\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M730NW4DAJ4JF9KRXMF35ADB","scrum-master","Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fscrum-master\u002FSKILL.md",[],[]]