[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N7ZAY0RW2D4SWP8ED3HC0":3,"skill-same:01M71N7ZAY0RW2D4SWP8ED3HC0":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":50,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M71N7ZAY0RW2D4SWP8ED3HC0","launch-strategist",null,"Org role guidance for a launch strategist: sequence product launches from internal validation to full public release across owned, rented and borrowed channels. For the full imported launch playbook, use launch-strategy.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Flaunch-strategist\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"launch","strategist","launch strategist","public","marketing","guidance","sequence","validation","playbook","release","https","product","github","monomind","across","channels","use","strategy","imported","for","2026-11-10 10:56:23",false,"---\nname: launch-strategist\ndescription: \"Org role guidance for a launch strategist: sequence product launches from internal validation to full public release across owned, rented and borrowed channels. For the full imported launch playbook, use launch-strategy.\"\ntags: [\"product\",\"launch\",\"marketing\"]\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Launch Strategist — Best Practices\n\n## Focus\nPlans and sequences product launches and feature announcements — from internal validation through full public release — to build momentum and convert attention into users.\n\n## Best practices\n- Use the ORB channel model: build Owned channels (email, blog, community) first since they compound; use Rented channels (social, marketplaces) to drive traffic to owned ones; use Borrowed channels (guest content, podcasts, influencers) to shortcut attention, then convert that attention into an owned relationship immediately.\n- Sequence launches in phases — internal (10-20 friendly users) → alpha (first external exposure + waitlist) → beta (broader access + teaser marketing) → early access (throttled or full expansion) → full launch (open self-serve, maximum visibility) — don't skip straight to public launch.\n- Coordinate multiple touchpoints on launch day: customer email, in-app notification, website banner, blog post, social posts, and relevant launch platforms (Product Hunt, Hacker News).\n- For Product Hunt: submit Tuesday-Thursday, brief your community in advance so upvotes aren't a surprise, write a founder-story first comment, and respond to every comment in the first 4 hours.\n- Write feature-announcement subject lines and taglines around the benefit\u002Ftransformation, not the feature name.\n- Keep iterating after launch: collect qualitative feedback week 1, ship fixes by week 4, synthesize quantitative retention data by month 2, and run a second announcement wave with social proof by month 3.\n\n## Common pitfalls\n- Treating launch as a single event instead of a phased sequence — going straight to full public launch without internal\u002Falpha\u002Fbeta validation.\n- Over-investing in rented channels (social posts) without a plan to convert that traffic into an owned asset (email list, community).\n- Submitting to Product Hunt without a plan to be active and responsive all day.\n- No post-launch plan — momentum dies because there's no week 1\u002Fmonth 1\u002Fmonth 2 follow-through.\n- Announcing features with feature-name subject lines instead of benefit framing, so existing users skip the email.\n\n## Tools & techniques\n- Five-phase launch framework (internal → alpha → beta → early access → full launch) with a stated goal per phase.\n- ORB channel mapping exercise before planning any specific launch tactic.\n- Launch-day touchpoint checklist to ensure owned, rented, and borrowed channels all fire together.\n- Success-metric benchmarks to judge a launch: waitlist size (500-2000 pre-launch), launch-day signup multiplier (3-5x baseline), D7 retention (40%+) for the launch cohort.\n","# Launch Strategist — Best Practices\n\n## Focus\nPlans and sequences product launches and feature announcements — from internal validation through full public release — to build momentum and convert attention into users.\n\n## Best practices\n- Use the ORB channel model: build Owned channels (email, blog, community) first since they compound; use Rented channels (social, marketplaces) to drive traffic to owned ones; use Borrowed channels (guest content, podcasts, influencers) to shortcut attention, then convert that attention into an owned relationship immediately.\n- Sequence launches in phases — internal (10-20 friendly users) → alpha (first external exposure + waitlist) → beta (broader access + teaser marketing) → early access (throttled or full expansion) → full launch (open self-serve, maximum visibility) — don't skip straight to public launch.\n- Coordinate multiple touchpoints on launch day: customer email, in-app notification, website banner, blog post, social posts, and relevant launch platforms (Product Hunt, Hacker News).\n- For Product Hunt: submit Tuesday-Thursday, brief your community in advance so upvotes aren't a surprise, write a founder-story first comment, and respond to every comment in the first 4 hours.\n- Write feature-announcement subject lines and taglines around the benefit\u002Ftransformation, not the feature name.\n- Keep iterating after launch: collect qualitative feedback week 1, ship fixes by week 4, synthesize quantitative retention data by month 2, and run a second announcement wave with social proof by month 3.\n\n## Common pitfalls\n- Treating launch as a single event instead of a phased sequence — going straight to full public launch without internal\u002Falpha\u002Fbeta validation.\n- Over-investing in rented channels (social posts) without a plan to convert that traffic into an owned asset (email list, community).\n- Submitting to Product Hunt without a plan to be active and responsive all day.\n- No post-launch plan — momentum dies because there's no week 1\u002Fmonth 1\u002Fmonth 2 follow-through.\n- Announcing features with feature-name subject lines instead of benefit framing, so existing users skip the email.\n\n## Tools & techniques\n- Five-phase launch framework (internal → alpha → beta → early access → full launch) with a stated goal per phase.\n- ORB channel mapping exercise before planning any specific launch tactic.\n- Launch-day touchpoint checklist to ensure owned, rented, and borrowed channels all fire together.\n- Success-metric benchmarks to judge a launch: waitlist size (500-2000 pre-launch), launch-day signup multiplier (3-5x baseline), D7 retention (40%+) for the launch cohort.\n",{"name":5,"tags":48,"tools":49,"source":50,"license":14,"description":7},[34,23,27],[],"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Flaunch-strategist",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add monoes\u002Fmonomind --skill launch-strategist",{"tool":65,"command":66},"bunx","bunx skills add monoes\u002Fmonomind --skill launch-strategist",{"tool":68,"command":69},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill launch-strategist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Flaunch-strategist\u002FSKILL.md",true,[],[74,101,135,159,181,208],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":100},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[81,82,83,84,85,86,87,88,89,90,91,92,36,93,94,95,96,97,98,99],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":105,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":117,"publishedAt":100},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[109,114],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":115,"categoryName":116,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[118,119,120,85,121,122,123,124,90,125,126,127,34,128,129,130,131,132,133,134],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":100},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[142],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[128,144,145,146,147,88,148,123,149,150,151,34,152,153,154,155,156,157,39,158],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":100},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师",[90,128,170,171,42,172,88,39,123,173,174,175,176,151,35,177,33,178,179,180],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":193,"publishedAt":100},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[187,190],{"categoryNo":188,"categoryName":189,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":191,"categoryName":192,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发",[194,195,196,197,42,198,199,200,201,89,202,203,204,90,36,35,205,206,207,33],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":215,"publishedAt":100},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[214],{"categoryNo":191,"categoryName":192,"taxonomyType":112,"taxonomyTypeDesc":113},[196,216,217,218,219,220,221,42,222,223,125,224,225,226,36,35,227,228,33,229],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]