agentsclimarketplace

Plan & spec

10,746 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

  • Interview me

    mouadja02/skills/skills/coding/interview-me Skill

    no license9★ 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.

  • Planning and task breakdown

    mouadja02/skills/skills/coding/planning-and-task-breakdown Skill

    no license9★ repo

    Breaks work into ordered tasks

  • Spec driven development

    mouadja02/skills/skills/coding/spec-driven-development Skill

    no license9★ repo

    Creates specs before coding

  • Creating oracle to postgres master migration plan

    mouadja02/skills/skills/databases/creating-oracle-to-postgres-master-migration-plan Skill

    no license9★ repo

    Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan

  • Planning oracle to postgres migration integration testing

    mouadja02/skills/skills/databases/planning-oracle-to-postgres-migration-integration-testing Skill

    no license9★ repo

    Oracle → PostgreSQL integration test plan for .NET data access artifacts

  • Devops rollout plan

    mouadja02/skills/skills/devops/devops-rollout-plan Skill

    no license9★ repo

    Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes

    The same file is in 1 other repository

  • Gtm enterprise account planning

    mouadja02/skills/skills/go-to-market/gtm-enterprise-account-planning Skill

    no license9★ repo

    Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.

  • Gtm positioning strategy

    mouadja02/skills/skills/go-to-market/gtm-positioning-strategy Skill

    no license9★ repo

    Find and own a defensible market position

  • Vllm serving planner

    mouadja02/skills/skills/llm-tooling/vllm-serving-planner Skill

    no license9★ repo

    Use when planning, reviewing, or tuning vLLM or OpenAI-compatible LLM serving for throughput, latency, KV-cache pressure, batching, quantization, prefix caching, or multimodal serving.

  • Cs pricing strategy

    mouadja02/skills/skills/marketing-and-growth/cs-pricing-strategy Skill

    no license9★ repo

    Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy

  • Launch strategy

    mouadja02/skills/skills/marketing-and-growth/launch-strategy Skill

    no license9★ repo

    When the user wants to plan a product launch, feature announcement, or release strategy

  • Marketing strategy pmm

    mouadja02/skills/skills/marketing-and-growth/marketing-strategy-pmm Skill

    no license9★ repo

    Product marketing — positioning, GTM strategy, competitive intelligence, and product launches

  • Agile product owner

    mouadja02/skills/skills/product-management/agile-product-owner Skill

    no license9★ repo

    Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking

  • Breakdown epic pm

    mouadja02/skills/skills/product-management/breakdown-epic-pm Skill

    no license9★ repo

    Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification

  • Breakdown feature prd

    mouadja02/skills/skills/product-management/breakdown-feature-prd Skill

    no license9★ repo

    Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

    The same file is in 1 other repository

  • Breakdown plan

    mouadja02/skills/skills/product-management/breakdown-plan Skill

    no license9★ repo

    Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking

  • Create github action workflow specification

    mouadja02/skills/skills/product-management/create-github-action-workflow-specification Skill

    no license9★ repo

    Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance

  • Create github issue feature from specification

    mouadja02/skills/skills/product-management/create-github-issue-feature-from-specification Skill

    no license9★ repo

    Create GitHub Issue for feature request from specification file using feature_request.yml template.

    The same file is in 1 other repository

  • Create github issues feature from implementation plan

    mouadja02/skills/skills/product-management/create-github-issues-feature-from-implementation-plan Skill

    no license9★ repo

    Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

    The same file is in 1 other repository

  • Create github issues for unmet specification requirements

    mouadja02/skills/skills/product-management/create-github-issues-for-unmet-specification-requirements Skill

    no license9★ repo

    Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.

    The same file is in 1 other repository

  • Create github pull request from specification

    mouadja02/skills/skills/product-management/create-github-pull-request-from-specification Skill

    no license9★ repo

    Create GitHub Pull Request for feature request from specification file using pull_request_template.md template.

  • Create implementation plan

    mouadja02/skills/skills/product-management/create-implementation-plan Skill

    no license9★ repo

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

  • Create specification

    mouadja02/skills/skills/product-management/create-specification Skill

    no license9★ repo

    Create a new specification file for the solution, optimized for Generative AI consumption.

    The same file is in 1 other repository

  • Prd

    mouadja02/skills/skills/product-management/prd Skill

    no license9★ repo

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis

  • Product strategist

    mouadja02/skills/skills/product-management/product-strategist Skill

    no license9★ repo

    Strategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals

  • Roadmap communicator

    mouadja02/skills/skills/product-management/roadmap-communicator Skill

    no license9★ repo

    Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers

  • Update implementation plan

    mouadja02/skills/skills/product-management/update-implementation-plan Skill

    no license9★ repo

    Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure

  • Update specification

    mouadja02/skills/skills/product-management/update-specification Skill

    no license9★ repo

    Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code

  • Ai901 study planner

    timothywarner-org/ai901-cert-buddy-claude/.claude/skills/ai901-study-planner Skill

    9★ repo

    Generates a personalized AI-901 study plan based on the learner's self-assessed confidence across the two AI-901 domains and their sub-areas, prioritizing weak areas with estimated hours, Microsoft Learn module links, and the matching Microsoft Press video lesson. Use when the learner asks for a study plan, is unsure what to study, or wants exam prep guidance for Microsoft Azure AI Fundamentals.

  • Ai901 study planner

    timothywarner-org/ai901-cert-buddy-claude/plugin/ai901-cert-buddy/skills/ai901-study-planner Skill

    9★ repo

    Generates a personalized AI-901 study plan based on the learner's self-assessed confidence across the two AI-901 domains and their sub-areas, prioritizing weak areas with estimated hours, Microsoft Learn module links, and the matching Microsoft Press video lesson. Use when the learner asks for a study plan, is unsure what to study, or wants exam prep guidance for Microsoft Azure AI Fundamentals.

  • Ablation planner

    pinkpixel-dev/skills-collection-1/SKILLS/ablation-planner Skill

    9★ repo

    Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission. Codex designs ablations from a reviewer's perspective, CC reviews feasibility and implements.

    The same file is in 2 other repositories

  • Auri core

    pinkpixel-dev/skills-collection-1/SKILLS/auri-core Skill

    9★ repo

    Auri: assistente de voz inteligente (Alexa + Claude claude-opus-4-20250805). Visao do produto, persona Vitoria Neural, stack AWS, modelo Free/Pro/Business/Enterprise, roadmap 4 fases, GTM, north star WAC e analise competitiva.

    The same file is in 1 other repository

  • Cc skill strategic compact

    pinkpixel-dev/skills-collection-1/SKILLS/cc-skill-strategic-compact Skill

    9★ repo

    Development skill from everything-claude-code

  • Concise planning

    pinkpixel-dev/skills-collection-1/SKILLS/concise-planning Skill

    9★ repo

    Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

    The same file is in 3 other repositories

  • Conductor new track

    pinkpixel-dev/skills-collection-1/SKILLS/conductor-new-track Skill

    9★ repo

    Create a new track with specification and phased implementation plan

    The same file is in 9 other repositories

  • Content strategy

    pinkpixel-dev/skills-collection-1/SKILLS/content-strategy Skill

    9★ repo

    Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program.

    The same file is in 1 other repository

  • Ddd strategic design

    pinkpixel-dev/skills-collection-1/SKILLS/ddd-strategic-design Skill

    9★ repo

    Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language for complex business domains.

    The same file is in 10 other repositories

  • Executing red team engagement planning

    pinkpixel-dev/skills-collection-1/SKILLS/executing-red-team-engagement-planning Skill

    9★ repo

    Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.

  • Experiment plan

    pinkpixel-dev/skills-collection-1/SKILLS/experiment-plan Skill

    9★ repo

    Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `research-refine`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.

    The same file is in 1 other repository

  • Grant proposal

    pinkpixel-dev/skills-collection-1/SKILLS/grant-proposal Skill

    9★ repo

    Draft a structured grant proposal from research ideas and literature. Supports KAKENHI (Japan), NSF (US), NSFC (China, including 面上/青年/优青/杰青/海外优青/重点), ERC (EU), DFG (Germany), SNSF (Switzerland), ARC (Australia), NWO (Netherlands), and generic formats. Use when user says "write grant", "grant proposal", "申請書", "write KAKENHI", "科研費", "基金申请", "写基金", "NSF proposal", or wants to turn research ideas into a funding application.

  • Think boundary critique

    product-on-purpose/thinking-framework-skills/skills/think-boundary-critique Skill

    9★ repo

    Audits the boundary judgments that silently define a problem frame. For each of four sources, who benefits, who decides, whose knowledge counts, who has standing, it contrasts the descriptive is boundary against the normative ought boundary, names the gaps, and lists the affected-but-excluded parties who have no voice in the frame, producing a boundary-judgment audit rather than a stakeholder round-up. Use when a plan, metric, or proposal already encodes who matters and who does not and the risk is solving a tidy problem for the people inside the line while pushing harm onto people outside it, when an improvement claim rests on an unexamined judgment about whose improvement, or on contested, value-laden, multi-party situations.

  • Think fermi estimation

    product-on-purpose/thinking-framework-skills/skills/think-fermi-estimation Skill

    9★ repo

    Produces a Fermi decomposition worksheet that estimates an unknown numeric quantity by factoring it into a chain of order-of-magnitude sub-estimates, guessing each to within a band, then multiplying back to a point estimate plus a compounded low/high range, with an independence check and a dominant-uncertainty flag. Use when you need a number and no lookup-able data or genuine reference class exists, so the magnitude has to be built from factors (for example sizing a market, a load, a cost, or a conversion you cannot look up). Not for forecasting from real base rates (use reference-class-forecasting) or decomposing a question for coverage with no number (use issue-tree).

  • Think problem restatement

    product-on-purpose/thinking-framework-skills/skills/think-problem-restatement Skill

    9★ repo

    Generates several genuinely different framings of an ambiguous problem by varying altitude, stakeholder, and goal-versus-implementation, then selects the most useful one to solve and produces a reframed problem statement with How Might We angles. Use when a problem is vague, arrived as a symptom or a pre-baked solution, or before committing significant work to solving the wrong thing.

  • Think red team light

    product-on-purpose/thinking-framework-skills/skills/think-red-team-light Skill

    9★ repo

    Produces an adversarial critique by constructing the strongest case against a proposal or thesis (the best objections an intelligent adversary would raise), then judging which objections actually land and what would rebut them. Use when a plan has too-easy consensus and needs pressure-testing, or to steelman the opposition before committing.

  • Think scenario planning

    product-on-purpose/thinking-framework-skills/skills/think-scenario-planning Skill

    9★ repo

    Produces a scenario set, 2-4 contrasting and internally consistent short narratives of alternative external futures named by two critical-uncertainty axes, plus a robustness read of the strategy across the worlds (which moves survive every world, which early signals show which world is arriving, which options to keep open). Use when the planning horizon is long and the decisive forces are outside control and not reliably predictable, and a single implicit forecast is driving the strategy. Not forecasting and not a single preferred path.

  • Think what would have to be true

    product-on-purpose/thinking-framework-skills/skills/think-what-would-have-to-be-true Skill

    9★ repo

    Converts a strategy, option, or contested claim into the specific conditions that would have to be true for it to be the best choice, rates each condition's confidence, and identifies which load-bearing assumptions to test first, producing an assumption ledger. Use when evaluating a strategic bet, or when a disagreement has become a clash of opinions rather than evidence.

  • Implementation notes

    GreatMark/fable-field-guide-skills/skills/implementation-notes Skill

    9★ repo

    Keep a running implementation-notes.md logging decisions, plan deviations, and surprises during implementation. Use PROACTIVELY the moment you start implementing an agreed plan, spec, or decision — the trigger is you beginning the work, not the user's wording: terse approvals ("开搞", "go ahead", "LGTM"), incremental starts ("先做第一步"), resuming across sessions, or starting from a reference-hunt taking list. If you notice mid-implementation it is missing, create it and backfill. Also use when the user says "keep implementation notes", "记录实现笔记". Not for post-hoc summaries of already-finished work.

  • Implementation plan

    GreatMark/fable-field-guide-skills/skills/implementation-plan Skill

    9★ repo

    Write an implementation plan that leads with the decisions the user is most likely to change and buries mechanical work at the bottom. Use when the user says "implementation plan", "实现计划", "开发计划", "落地方案", "先出方案再动手", "先别写代码,想清楚给我看看", asks for an RFC/技术方案 or a pre-work buy-in proposal (立项提案), or wants a reviewable plan after brainstorming. Also read whenever a built-in plan mode is active (Cursor, Claude Code, Codex) — before writing any plan, whether you switched into it or the session started there. Not for trivial changes or resolving open questions (run interview-me first); if a reviewed plan already exists, start with implementation-notes instead.

  • Pitch explainer

    GreatMark/fable-field-guide-skills/skills/pitch-explainer Skill

    9★ repo

    Package the spec, prototype, and implementation notes of finished or nearly-finished work into one self-contained document that gets reviewers to buy in fast. Use when the user says "pitch doc", "提案文档", "打包给评审", "给这轮工作写个提案", "把成果打包成汇报材料", "跟团队讲清楚这次改动", asks for a one-pager or explainer aimed at reviewers or approvers, or needs sign-off from people out of the loop. Not for verifying the user's own understanding (use change-quiz), proposals to green-light work not yet started (use implementation-plan), routine status reports (日报/周报), or neutral knowledge docs — wikis, READMEs, onboarding guides.

  • Spec builder

    wcgomes/agents-workspace/templates/skills/spec-builder Skill

    no license9★ repo

    Create, evolve, and archive spec-driven workflow artifacts (proposals, outcome specs, task plans). Use when work needs a durable outcome contract before execution — new deliverables or outcome changes, API/contract changes, migrations, security/privacy-sensitive work, or any long-running task where the outcome must be agreed upfront. Do NOT use for trivial fixes, exploratory spikes, or tasks where the handoff's done criteria suffice. Produces specs/ artifacts that orchestrate consumes via Spec ref.

  • Pilot proposal writer setup

    TeoSlayer/pilot-skills/skills/pilot-proposal-writer-setup Skill

    9★ repo

    Deploy a multi-agent proposal writing system with 3 agents. Use this skill when: 1. User wants to set up a proposal writing or RFP response pipeline 2. User is configuring an agent as part of a proposal drafting workflow 3. User asks about research briefs, proposal sections, or compliance review across agents Do NOT use this skill when: - User wants to share a single document (use pilot-share instead) - User wants a one-off review (use pilot-review instead)

  • Tech leadership

    oghie/skillsets/skills/tech-leadership Skill

    9★ repo

    Use when advising, planning, reviewing, reporting, operating, or improving CTO and technology leadership work across strategy, cybersecurity management, SME/COE, functional and technical requirements, framework selection, people, organization, delivery, risk, KPI, roadmap, budgeting, governance, audit, R&D, stakeholder communication, culture, politics, and sector-specific leadership.

  • Agent risk review

    emaraschio/cursor-commands/.cursor/skill-contracts/agent-risk-review Skill

    9★ repo

    Produces a one-page agent permission brief (allowed, approval-required, forbidden, limits, logging, rollback, first-week test plan) before granting an AI agent access to a system, tool, or account. Use for agent risk review, permission design, MCP/tool access planning, or "what should the agent be allowed to do?"

  • Pathfinder

    emaraschio/cursor-commands/.cursor/skill-contracts/pathfinder Skill

    9★ repo

    Map the fog of war before building. Given a project goal and known context, separate decisions already fixed from open decision frontiers and fog-of-war unknowns, tag each unknown with a next move (research, prototype, ask an expert, user test, or delegate), and lay out parallel work tracks plus the next three actions. Plan-only, no execution in the same turn. Use for pathfinder, decision mapping, fog of war, or planning a greenfield or messy project before the next step feels obvious but undercooked.

  • Requirement to implementation

    emaraschio/cursor-commands/.cursor/skill-contracts/requirement-to-implementation Skill

    9★ repo

    Structured workflow for taking a requirement (feature, bug, refactor, chore, or performance task) from any source (Notion, GitHub, conversation) through planning, approval, implementation, verification, and documentation. Use when the user provides a requirement, task, ticket, or asks to implement something.

  • Agent risk review

    emaraschio/cursor-commands/plugin/.cursor/skill-contracts/agent-risk-review Skill

    9★ repo

    Produces a one-page agent permission brief (allowed, approval-required, forbidden, limits, logging, rollback, first-week test plan) before granting an AI agent access to a system, tool, or account. Use for agent risk review, permission design, MCP/tool access planning, or "what should the agent be allowed to do?"

  • Pathfinder

    emaraschio/cursor-commands/plugin/.cursor/skill-contracts/pathfinder Skill

    9★ repo

    Map the fog of war before building. Given a project goal and known context, separate decisions already fixed from open decision frontiers and fog-of-war unknowns, tag each unknown with a next move (research, prototype, ask an expert, user test, or delegate), and lay out parallel work tracks plus the next three actions. Plan-only, no execution in the same turn. Use for pathfinder, decision mapping, fog of war, or planning a greenfield or messy project before the next step feels obvious but undercooked.

  • Requirement to implementation

    emaraschio/cursor-commands/plugin/.cursor/skill-contracts/requirement-to-implementation Skill

    9★ repo

    Structured workflow for taking a requirement (feature, bug, refactor, chore, or performance task) from any source (Notion, GitHub, conversation) through planning, approval, implementation, verification, and documentation. Use when the user provides a requirement, task, ticket, or asks to implement something.

  • Brain plan

    SanderMoon/local-brain/pkg/skillscatalog/skills/brain-plan Skill

    9★ repo

    Plan a project by breaking goals into concrete tasks with priorities and deadlines. Use when the user says "let's plan", "break this down", "I need to figure out how to", "help me plan", or when starting a new project.

  • Plan create

    JordanGunn/nunchuck/skills/plan/plan-create Skill

    9★ repo

    Compile `.plan/active.yaml` into a schema-validated active plan directory under `.plan/active/`.