agentsclimarketplace

Plan & spec

10,724 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Threat modeling

    Deadlymind/nanolama/skills/threat-modeling Skill

    1★ repo

    Runs design-time STRIDE threat modelling on a feature before the code exists — names the trust boundaries this stack actually has (the tenant boundary, RBAC roles inside a tenant, the auth cookie and CSRF edge, file-upload ingestion, inbound webhooks and third-party payloads, and the AI tool surface where a model-supplied argument is attacker-influenced input), walks spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege against only the boundaries the feature crosses, then emits a short threat-to-mitigation-to-owning-skill table of work items. Use when designing a new endpoint or background job, introducing a new trust boundary or a new class of data, planning anything that touches money, PII or auth, writing an RFC or ADR, or asked "what could go wrong with this design". Not for auditing an existing diff (see security-review) or reacting after a breach or outage (see incident-response).

  • Capacity planning

    yigityildiz0/universal-ai-skill-library/skills/common/capacity-planning Skill

    no license1★ repo

    Build an evidence-based capacity plan for teams, services, operations, budgets, or delivery work. Use for capacity planning, staffing scenarios, workload forecast, throughput planning, utilization, or demand-versus-capacity decisions.

  • Competitive brief

    yigityildiz0/universal-ai-skill-library/skills/common/competitive-brief Skill

    no license1★ repo

    Research and write a decision-focused competitive brief using current, source-backed evidence. Use for competitor analysis, competitive brief, market comparison, feature comparison, positioning comparison, or win/loss preparation.

  • Create implementation plan

    yigityildiz0/universal-ai-skill-library/skills/common/create-implementation-plan Skill

    no license1★ repo

    Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

  • Ddd strategic design

    yigityildiz0/universal-ai-skill-library/skills/common/ddd-strategic-design Skill

    no license1★ repo

    Domain-Driven Design strategic and tactical patterns for complex business domains. Use when modeling domains, defining bounded contexts, or designing.

  • Event planning

    yigityildiz0/universal-ai-skill-library/skills/common/event-planning Skill

    no license1★ repo

    Help plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and.

  • Implementation plan

    yigityildiz0/universal-ai-skill-library/skills/common/implementation-plan Skill

    no license1★ repo

    Produce a decision-complete, repository-grounded implementation plan with scope, architecture, file-level changes, data/API impacts, tests, migration, rollout, rollback, risks, and acceptance criteria. Use before substantial changes or when the user asks for a plan; inspect the actual project and infer safe details instead of running a fixed interview.

  • Notion spec to implementation

    yigityildiz0/universal-ai-skill-library/skills/common/notion-spec-to-implementation Skill

    no license1★ repo

    Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

    The same file is in 4 other repositories

  • Operational risk assessment

    yigityildiz0/universal-ai-skill-library/skills/common/operational-risk-assessment Skill

    no license1★ repo

    Identify, score, prioritize, and monitor operational risks with owners, controls, scenarios, and residual uncertainty. Use for risk assessment, risk register, operational risk, mitigation plan, or contingency planning.

  • Plan before code

    yigityildiz0/universal-ai-skill-library/skills/common/plan-before-code Skill

    no license1★ repo

    Guide exploration and planning phases before implementation using agentic coding best practices. Includes LLM task suitability assessment, token cost.

  • Planning and task breakdown

    yigityildiz0/universal-ai-skill-library/skills/common/planning-and-task-breakdown Skill

    no license1★ repo

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too.

  • Product management

    yigityildiz0/universal-ai-skill-library/skills/common/product-management Skill

    no license1★ repo

    Route product strategy and delivery work to focused workflows for product framing, discovery, competition, metrics, sprint planning, stakeholder communication, and telemetry. Use when a task concerns user problems, scope, prioritization, launch, outcomes, or product decisions.

  • Product tracking plan

    yigityildiz0/universal-ai-skill-library/skills/common/product-tracking-plan Skill

    no license1★ repo

    Design a privacy-aware product telemetry plan with event taxonomy, properties, identity rules, validation, and decision links. Use when asked what to track, to create an analytics plan, event schema, measurement plan, or telemetry specification.

  • Refactor plan

    yigityildiz0/universal-ai-skill-library/skills/common/refactor-plan Skill

    no license1★ repo

    Plan a multi-file refactor with proper sequencing and rollback steps

  • Requirement enhancer

    yigityildiz0/universal-ai-skill-library/skills/common/requirement-enhancer Skill

    no license1★ repo

    Improve the quality, completeness, and testability of software requirements by applying quality attributes analysis, enhancement patterns, acceptance.

  • Research plan implement

    yigityildiz0/universal-ai-skill-library/skills/common/research-plan-implement Skill

    no license1★ repo

    Execute a structured Research-Plan-Implement (RPI) workflow with GO/NO-GO gates and artifact generation at each phase. Use for non-trivial features that.

  • Rollback strategy advisor

    yigityildiz0/universal-ai-skill-library/skills/common/rollback-strategy-advisor Skill

    no license1★ repo

    Plans and implements rollback strategies for production deployments including database migration rollbacks, feature flag rollbacks, and incident response.

  • Spec driven development

    yigityildiz0/universal-ai-skill-library/skills/common/spec-driven-development Skill

    no license1★ repo

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are.

  • Sprint planning

    yigityildiz0/universal-ai-skill-library/skills/common/sprint-planning Skill

    no license1★ repo

    Plan a realistic sprint or short delivery cycle with goal, scope, capacity, dependencies, acceptance criteria, risks, and review signals. Use for sprint planning, iteration planning, backlog selection, delivery planning, or team capacity planning.

  • Stakeholder update

    yigityildiz0/universal-ai-skill-library/skills/common/stakeholder-update Skill

    no license1★ repo

    Write a concise, evidence-based stakeholder update for product, engineering, operations, research, or program work. Use for weekly update, status report, executive summary, project update, risk update, or leadership communication.

  • Strategic comments

    yigityildiz0/universal-ai-skill-library/skills/common/strategic-comments Skill

    no license1★ repo

    Add high-value comments explaining complex logic, business rules, design decisions, and non-obvious implementations. Use when clarifying code intent.

  • Molecular genetics assay planning

    yigityildiz0/scientific-agent-skills/skills/common/molecular-genetics-assay-planning Skill

    no license1★ repo

    Plans and validates research-use PCR, RT-PCR, qPCR, and probe assays with explicit target/isoform/reference-build provenance, primer3 candidate design, pair-aware genome/transcriptome specificity checks, thermodynamic screening, and empirical validation gates. Use for primer or probe design, qPCR assay planning, pseudogene/paralog/off-target checks, SNP-at-primer-site review, hairpin/dimer analysis, or troubleshooting assay specificity and efficiency. Not for autonomous clinical diagnostic claims or unreviewed wet-lab execution.

  • Scientific problem selection

    yigityildiz0/scientific-agent-skills/skills/common/scientific-problem-selection Skill

    no license1★ repo

    This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

    The same file is in 7 other repositories

  • Request refactor plan

    M0rtalPhe0nix/dotfiles/.agents/skills/request-refactor-plan Skill

    1★ repo

    Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

    The same file is in 13 other repositories

  • To spec

    M0rtalPhe0nix/dotfiles/.agents/skills/to-spec Skill

    1★ repo

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    The same file is in 11 other repositories

  • To tickets

    M0rtalPhe0nix/dotfiles/.agents/skills/to-tickets Skill

    1★ repo

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    The same file is in 1 other repository

  • Speckit diagrams

    M0rtalPhe0nix/dotfiles/.claude/skills/speckit-diagrams Skill

    1★ repo

    Turn GitHub Spec Kit feature artifacts into editable Excalidraw diagrams and local previews. Use when the user asks to visualize, diagram, map, explain visually, or create an architecture, workflow, data model, story map, traceability map, or implementation roadmap from Spec Kit files such as spec.md, plan.md, research.md, data-model.md, contracts/, or tasks.md.

  • Ctx spec

    motiful/ctx/skills/ctx-spec Skill

    1★ repo

    Writes specs, ADRs, architecture and design docs that an AI coding agent can build directly from — the right granularity (constraints, not hand-written implementation), testable EARS acceptance criteria, and ADR discipline (record only decided choices, supersede in place). Use when writing or restructuring a spec, a decision record (ADR), an architecture doc, or a design doc in a ctx knowledge base, or when deciding how detailed a spec needs to be.

  • Founder prioritization

    1elasmarjad/yc-founder-skills/plugins/yc-founder-skills/skills/founder-prioritization Skill

    1★ repo

    Choose the startup's highest-leverage constraint and convert it into a weekly outcome, protected founder time, scoped work, ownership, and stop rules. Use for competing priorities, roadmaps, founder calendars, execution failures, delegation, decision latency, too many projects, or deciding what not to do.

  • Owner 5w2h

    XHdW/owner-mode/skills/owner-5w2h Skill

    1★ repo

    Planning preflight: use when the user invokes $owner-5w2h, asks to check the completeness of a requirement, design, implementation approach, research plan, or project plan, or when the current task is explicitly to form or revise such a plan and a concrete missing or contradictory context item has plausible answers that would change its scope, architecture, sequence, authority, or lifecycle cost.

  • Agentic test clean

    jpbaking/agentic-tests/skills/shared/agentic-test-clean Skill

    1★ repo

    Remove every agent-generated test file (*.agentic.spec.*, *.agentic.test.*, *AgenticTest.java, test_agentic_*.py, *_agentic_test.c/.cpp) plus the agentic plan files, after an explicit user confirmation. Use when asked to delete, clean up, or remove the agent tests or start the agentic-test lifecycle over. Never touches main code, user tests, or test config.

  • Relay10 spec

    minwoo19930301/relay10/plugins/relay10/skills/relay10-spec Skill

    1★ repo

    A small, inspectable Codex harness with risk-aware routing, evidence handoffs, and a Reader-10 clarity gate

  • Fips remediation plan

    TGPSKI/go-fips-toolkit/.agents/skills/fips-remediation-plan Skill

    1★ repo

    Generates component-specific FIPS remediation TODO lists from crypto audit results, with effort estimates and suggested PR sequencing. A directed workflow following the Inspect-Decide-Generate pattern, splitting findings into must-fix, primitive swaps, no-change-needed, and upstream dependencies. Use after a FIPS crypto audit when a component team asks what they need to fix, when planning sprint work for a FIPS migration, or when writing remediation PR descriptions.

  • Interview me

    zdnemz/claude-team/.claude/skills/interview-me Skill

    1★ repo

    Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

    The same file is in 8 other repositories

  • Trip brief

    metalaihq/trip-event-curator/skills/trip-brief Skill

    1★ repo

    Compress the session's discovery/tracking/weaving outputs into a 30-second decision brief for the traveler answering exactly three questions — what would I regret missing (top picks with why), what are the booking deadlines (which tickets die first), and what should I do right now (one action) — each verdict wired to signal IDs with capture dates, refusing to brief on inputs that failed their quotas. Use when the user says '핵심만 정리해줘', '뭐가 제일 아까워?', '놓치면 안 되는 것만', '예매 뭐부터 해?', '30초 브리핑', '한 장으로 요약', '너무 많아 — 추려줘', or as the final judgment step after event-finder, entry-tracker, edition-check, or trip-weaver have produced gated outputs. Decision-shaped guidance, never a data dump.

  • Plan alm

    LeonardSEO/power-platform-skills-codex/plugins/power-pages/skills/plan-alm Skill

    1★ repo

    Creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements upfront, then generates a visual HTML plan document for your review and approval. **plan-alm does not deploy anything itself** — it is a planner. After you approve the plan, run the individual ALM skills (setup-solution, setup-pipeline, deploy-pipeline, or export-solution/import-solution); each detects the approved plan and executes the right step in order, keeping the plan updated as it runs. Use when asked to: "plan my alm", "set up alm", "create deployment plan", "plan my deployments", "help me deploy to multiple environments", "set up promotion strategy", "create cicd plan", "plan site promotion", "help me go to production", "set up pipeline for my site".

    The same file is in 1 other repository

  • Specification writing

    jahfaliabdulrahman-dev/hermes-skills/skills/specification-writing Skill

    1★ repo

    Production-grade agent skills for Flutter, DevOps & AI Governance

  • Prd

    wendelcastro/fluxo-engenharia-ia/skills/prd Skill

    no license1★ repo

    Transforma a entrevista em um PRD de uma página — o documento de produto que qualquer pessoa lê, entende e consegue aprovar. Use após a entrevista, antes da especificação técnica, quando o trabalho for um produto ou funcionalidade nova de porte. Gatilhos: "escreve o PRD", "documento de produto", "quero entender o que vamos construir antes da parte técnica".

  • Piensalo strategy

    ralfyishere/piensalo/skills/piensalo-strategy Skill

    1★ repo

    Strategy and decision program: recover the real objective, enumerate constraints including contractual and irreversibility traps, generate genuinely distinct options, scenario-score them, attack the leader, and recommend with explicit kill conditions. Use for 'should we do X', pricing/roadmap/build-vs-buy calls, responses to competitor moves, and any decision under uncertainty with real downside. Trigger phrases: 'recommend', 'should we', 'what's the right move'.

  • Ad creative

    cskwork/supermarketer-skill/vendor/marketingskills/skills/ad-creative Skill

    1★ repo

    When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'static ad concepts,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'fake DM ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'animated explainer ad,' 'motion collage ad,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

    The same file is in 2 other repositories

  • Content strategy

    cskwork/supermarketer-skill/vendor/marketingskills/skills/content-strategy Skill

    1★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

    The same file is in 5 other repositories

  • Lead magnets

    cskwork/supermarketer-skill/vendor/marketingskills/skills/lead-magnets Skill

    1★ repo

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.

    The same file is in 5 other repositories

  • Marketing plan

    cskwork/supermarketer-skill/vendor/marketingskills/skills/marketing-plan Skill

    1★ repo

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

    The same file is in 3 other repositories

  • Site architecture

    cskwork/supermarketer-skill/vendor/marketingskills/skills/site-architecture Skill

    1★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

    The same file is in 5 other repositories

  • Premarket review

    Jinchengawu/stock-monitoring-kit/skills/premarket-review Skill

    1★ repo

    Create an evidence-first daily premarket brief for A-share, Hong Kong, or US markets. Use when the user asks for a pre-open plan, watchlist scan, daily/weekly BBI-KDJ-MACD-volume setup review, market and sector flow assessment, or a catalyst checklist before a trading session.

  • 507 prd

    ssdiwu/507-skills/code/507-prd Skill

    1★ repo

    把当前对话、方案或 PRD 沉淀成产品需求文档(PRD)。承接对齐结果到执行的中间规格化层——把方案落成需求规格(要解决什么问题、给谁、怎么验证)。不拆 issue 工单(归 507-issue)、不做架构体检(归 507-inspect)。Use when user mentions 写 PRD, 拆 PRD, 做个 PRD, 沉淀 PRD, 形成需求文档, 把刚才整理成需求, 需求规格, 落成 PRD, to-prd, product requirements.

  • 507 frame

    ssdiwu/507-skills/write/507-frame Skill

    1★ repo

    面向人的结构化方案 skill(活动、培训、工作坊、合作提案、项目计划)。输入是已由 grill 确认的需求与边界,产物是推动读者决策或行动的正式方案;信息缺口涉及用户取舍时返回 grill,不在 frame 内追问确认。具体软件产品需求规格归 507-prd。Use when user mentions 写方案, 写计划, 活动方案, 培训方案, 工作坊方案, 合作提案, 项目计划, 结构化文档, 正式提案, frame, proposal, workshop plan, partnership proposal, project plan, brief.

  • Seven day plan

    githubume/chengxing-os-skills/plugins/habit-rebuild/skills/seven-day-plan Skill

    1★ repo

    为一个已操作化的成人日常行为设计七天最小实验。用户说“给我七天计划”“做一个一周实验”“怎样开始并坚持”“减少刷手机、拖延或晚睡流程”“想要低负担打卡”时使用;一次只验证一个关键变量,指标不超过三个,并包含漏做后的恢复脚本。

  • Seven day family plan

    githubume/chengxing-os-skills/plugins/parent-learning/skills/seven-day-family-plan Skill

    1★ repo

    为作业启动、家庭提醒或手机边界设计七天家庭学习实验。用户说“给我们一周计划”“家长和孩子分别做什么”“试七天再复盘”“不要只要求孩子改变”时使用;每轮只验证一个关键变量,明确孩子、家长和环境各一个动作,并设置恢复与第3/7天检查。

  • Go

    eduardkumskyi/octo/skills/go Skill

    no license1★ repo

    The front door: describe what you want in a sentence — octo sizes the ceremony automatically. Small fix → implement + verify in minutes; feature → full build; subsystem → spec, plan, then build. Announces the chosen gear; override with -s/-m/-l.

  • Plan

    eduardkumskyi/octo/skills/plan Skill

    no license1★ repo

    Explore the codebase and produce an implementation plan with numbered, independently verifiable tasks. Surfaces every assumption (SAFE/RISKY); RISKY + hard-to-reverse decisions come back as questions before the plan is final.

  • Spec

    eduardkumskyi/octo/skills/spec Skill

    no license1★ repo

    Turn an idea into a reviewed design doc before any planning: a one-question-at-a-time interview via question cards, then a spec covering architecture, data flow, error handling, and testing, self-reviewed for placeholders and contradictions. Feeds /octo:plan.

  • Planning with files

    andr-ca/agentharness/.claude/skills/planning-with-files Skill

    1★ repo

    Use when starting a complex multi-step task, a research project, or any task requiring more than 5 tool calls — creates and maintains task_plan.md, findings.md, and progress.md to preserve state across context resets.

  • Plan lite

    Aquish-Lee/agent-handrails/plugins/agent-handrails/skills/plan-lite Skill

    1★ repo

    Create a compact implementation strategy when a user explicitly requests a plan or a non-trivial task needs ordered, verifiable work slices, risk controls, and a review-boundary seed. Skip obvious single-step edits.

  • Spec lite

    Aquish-Lee/agent-handrails/plugins/agent-handrails/skills/spec-lite Skill

    1★ repo

    Turn converged intent into a lightweight outcome contract when a user explicitly requests a spec or durable acceptance semantics are needed before consequential implementation. Skip routine tasks and unresolved discovery.

  • Plan lite

    Aquish-Lee/agent-handrails/skills/plan-lite Skill

    1★ repo

    Create a compact implementation strategy when a user explicitly requests a plan or a non-trivial task needs ordered, verifiable work slices, risk controls, and a review-boundary seed. Skip obvious single-step edits.

  • Spec lite

    Aquish-Lee/agent-handrails/skills/spec-lite Skill

    1★ repo

    Turn converged intent into a lightweight outcome contract when a user explicitly requests a spec or durable acceptance semantics are needed before consequential implementation. Skip routine tasks and unresolved discovery.

  • Launch a product

    whatsuppiyush/god-of-skills/growth-os/launch-a-product Skill

    1★ repo

    The ordered playbook for launching a product or running a go-to-market push. It sequences the right discipline skills into one workflow: strategy and positioning first, then message and copy, then the launch moment (Product Hunt, press, limited drop), then the acquisition channels that carry it, then the analytics that prove it worked. Use whenever the user is launching a new product, feature, or store; planning a Product Hunt or press launch; running a limited or capped drop; asking "how do we go to market", "how do I launch this", "what's the launch plan", or "we're launching next month, what's the order of operations". Reach for this instead of firing a single skill when the launch touches strategy, brand, copy, channels, and measurement at once.

  • Launch gtm

    whatsuppiyush/god-of-skills/marketing/launch-gtm Skill

    1★ repo

    Plan and run a product launch or go-to-market push: pick your first-users channel, run a Product Hunt launch, earn press, manufacture scarcity for a limited drop, and name/bid so offline attention converts. Use whenever the user is launching a product, planning a Product Hunt launch, asking "how do I get my first users", running a Black Friday / capped drop, chasing tier-1 press or lower CAC, doing a brand-awareness campaign, or naming a product for a billboard/podcast/TV push. Trigger phrases: "launch on Product Hunt", "how do we go to market", "get first 1000 users", "PR strategy", "press outreach", "limited launch", "sell out a cohort", "campaign microsite", "what should we name this".

  • Strategy fundamentals

    whatsuppiyush/god-of-skills/marketing/strategy-fundamentals Skill

    1★ repo

    The upstream growth-strategy layer: decide WHAT to build, WHO for, WHICH channel, and WHY it compounds, before spending a dollar on execution. Use whenever growth has stalled or plateaued, CAC is rising, retention is falling, or someone asks "what should we work on next," "which channel should we use," "how do we find product-market fit," "why isn't growth working," "should I start/quit this," "how do we position this," "what's our unfair advantage," "how do we grow the market," or "write our strategy." Also reach for it whenever a plan jumps straight to tactics (ads, SEO, emails) without a diagnosis, whenever a founder is spreading thin across every channel, or whenever they blame a channel for a problem that is really product, pricing, market, or brand.