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

  • NioPD PM roadmap

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PM-roadmap Skill

    1★ repo

    Creates project roadmap with Gantt chart. Use for project planning.

  • NioPD PO north star

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PO-north-star Skill

    1★ repo

    Defines and tracks the North Star Metric that drives product success. Use for strategic focus, team alignment, or metric rationalization.

  • NioPD PO stakeholder update

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PO-stakeholder-update Skill

    1★ repo

    Creates stakeholder update report. Use for executive communication.

  • NioPD ST okr

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-ST-okr Skill

    1★ repo

    Applies OKR (Objectives and Key Results) framework to define and track strategic goals. Use for quarterly planning, goal alignment, performance management, or team focus.

  • NioPD ST rice

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-ST-rice Skill

    1★ repo

    Applies RICE prioritization framework to score and rank features or initiatives. Use for feature prioritization, roadmap planning, resource allocation decisions, or stakeholder alignment on priorities.

  • NioPD UR kano

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-UR-kano Skill

    1★ repo

    Applies Kano Model to categorize features based on customer satisfaction impact. Use for feature prioritization, customer satisfaction optimization, or product differentiation strategy.

  • Evidence

    JarrydAdaens/agentic_rails_tooling/archived/skills/evidence Skill

    1★ repo

    Use this skill when the user explicitly asks for evidence capture, provenance, validation evidence, source-grounded proof, or an evidence.md file during an agentic task. It maintains an opt-in evidence record — by default the `## Evidence / References` section inside the active plan.md, or a standalone evidence.md when explicitly requested or genuinely required for audit — that indexes changed files, commits, checks, planning inputs, and unverified claims.

  • Rails retrospective

    JarrydAdaens/agentic_rails_tooling/archived/skills/rails-retrospective Skill

    1★ repo

    Use this skill after implementation work, planning work, Agentic Rails implementation-plan execution, bulk planning, orchestration runs, or completed stories when the user asks for a retrospective, lessons learned, post-work review, process review, plan-adherence review, or durable retrospective.md grounded in plans, logs, git history, changed files, and optional provenance artifacts.

  • Rails grade cer

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-grade-cer Skill

    1★ repo

    Use this skill to grade an Agentic Rails plan on three orthogonal axes — complexity, effort, and risk (CER) — and emit a score card. Use whenever the user wants a plan sized, graded, or assessed before dispatch; wants to know how hard, how long, or how dangerous a plan is; wants to spot a story that should be reclassified as an epic; or wants CER scores to feed a downstream routing or planning system. Runs all three axes by default, or any subset the user names (e.g. "just the risk", "effort and complexity"). Grades only — it does not route, plan, fragment, select models, or suggest fixes.

  • Rails memory learnings

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-memory-learnings Skill

    1★ repo

    Use this skill at the end of a work session - after implementation, planning, Agentic Rails implementation-plan execution, bulk planning, orchestration, or a completed story - when the user asks to capture learnings, memorize the session, write a session learning, or deposit a memory artifact. It reflects on the session and writes exactly one durable learning file into the Rails memory repository's learnings/new/ folder, recording the outcome, what went well, what struggled, and full provenance: the models, harness, thinking effort, reasoning vs non-reasoning, fast mode, and token cost behind the work.

  • Rails milestone planning

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-milestone-planning Skill

    1★ repo

    Use this skill to turn the story backlog (an unscheduled story inventory, informally "Milestone -1") and the Design doc's Milestones Index into a scored, dependency-ordered story list inside a Milestone document, and to keep the backlog itself alive over time. Use it to pull backlog stories into a fresh milestone's story list, or to refine an existing milestone whose story list has grown past a sensible scope and needs stories shunted into Deferred / Follow-up Work. Calls the rails-grade-cer skill for scoring rather than reimplementing it, and promotes epic-sized backlog items into their own Milestone documents when CER exposes them. Not model-invocable — the user calls this by name when they are ready to plan or refine a milestone's story list; it does not trigger itself on ambient planning conversation.

  • Rails new proposal

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-new-proposal Skill

    1★ repo

    Use this skill when the user wants to capture a proven, project-local innovation - a guard rail, hook set, agent, rule pack, script, or workflow - as a self-contained proposal for the Agentic Rails tooling repository. Triggers: "make this a proposal", "propose this for rails", "bundle this up for tooling", "this guard rail should be generalized". It copies the working slice verbatim (hooks extracted into a fresh .claude/settings.json, agents, scripts, dependency manifests, docs) into proposals/<slug>/ in the tooling repo, writes a README recording the use case, the evidence it works, and a suggested destination, and can zip the proposal for sharing with another developer. It is drop-off only: it never integrates anything into source/, never generalizes code, and never touches other proposals.

  • Rails plan spam workflow

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-plan-spam-workflow Skill

    1★ repo

    Use this orchestration skill when turning stories, feature descriptions, backlog items, or design notes into many implementation-plan documents. The Boss builds a durable planning queue, dispatches one subagent per story or feature cluster, writes plans, updates progress, and repeats until complete.

  • Rails planning phaser

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-planning-phaser Skill

    1★ repo

    Use this skill to fracture a plan into sequential, executable phases. It grades the plan with CER, and if any axis breaches threshold it splits the plan at natural seams into small phases that each fit under the local model's threshold, re-grades every phase, and rewrites the original plan into a manifest that registers and tracks them. Use whenever a plan is too large, complex, or risky to run as one unit; when work needs to be sized for a local model; or when preparing a plan for orchestrated sub-agent execution. Assigns each phase a model tier and escalates to the human if the work needs more than seven phases (it's really multiple stories) or can't be reduced below threshold.

  • Rails planning

    JarrydAdaens/agentic_rails_tooling/source/skills/rails-planning Skill

    1★ repo

    Use this skill when creating, revising, locating, or enforcing implementation plans inside an Agentic Rails project. Use for implementation plans, work plans, execution plans, feature plans, bug plans, repository planning before coding, IDE planning drift, or any planning output that should survive across IDEs, machines, branches, sessions, reviews, retrospectives, execution logs, evidence, complaints, or handovers. The skill ensures plans are written into the target repository under context/implementation-plans/<milestone-slug>/ <story-slug>/, producing one primary artifact — plan.md — with CER, questions, evidence, complaints, execution log, and completion review folded into it by default. Can also produce opt-in sidecars (evidence.md, complaining.md, thinking.md) beside plan.md when a story genuinely needs durable, separately tracked provenance.

  • Generation

    jovd83/playwright-skill/coverage_plan/generation Skill

    1★ repo

    Coverage-planning skill for Playwright work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Playwright coverage plan with scenarios, execution types, priorities, and traceability.

  • Review

    jovd83/playwright-skill/coverage_plan/review Skill

    1★ repo

    Coverage-plan review skill for Playwright work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.

  • Stakeholder

    jovd83/playwright-skill/reporting/stakeholder Skill

    1★ repo

    Stakeholder-reporting skill for Playwright execution results. Use when Codex needs to turn raw Playwright runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.

  • Repurpose

    rmzlb/baaton-skills/marketing/repurpose Skill

    1★ repo

    Transform one piece of content into multiple platform-optimized formats. 1-to-N content multiplication: LinkedIn post to X thread, email, carousel, video script, and more. Includes platform adaptation rules, not just reformatting. Use when: repurposing a post for other platforms, maximizing content ROI, creating a content series from one idea, or building a multi-channel campaign. Trigger words: repurpose, transform, adapt, cross-post, multi-platform, content multiplication, 1-to-N, carousel, thread from post, atomize. NOT for: writing original content (use write), quality scoring (use audit), or strategic planning (use strategy).

  • Strategy

    rmzlb/baaton-skills/marketing/strategy Skill

    1★ repo

    Marketing strategy foundations: ICP definition, buyer personas, positioning, messaging frameworks, competitive analysis, and go-to-market planning. Use when: starting a new product/feature, defining target audience, building messaging, analyzing competitors, planning a launch, or creating a GTM strategy. Trigger words: ICP, persona, positioning, messaging, competitive analysis, go-to-market, GTM, value proposition, target audience, market research. NOT for: writing content (use write), auditing drafts (use audit), or running the full content pipeline (use create).

  • Agentprivacy quantum sentinel

    mitchuski/agentprivacy-skills/agentprivacy-skills-v5/persona/agentprivacy-quantum-sentinel Skill

    1★ repo

    Specialist persona for quantum threat model and post-quantum sovereignty. Activates for quantum vulnerability assessment, 2D vs 6D defence, dormant asset analysis, temporal thesis, or post-quantum migration planning. V6 register note (2026-06-10): conjecture and version citations resolve to agentprivacy-docs/research/CONJECTURE_REGISTER_V6.md (head C89); model head: privacy_value_v6_formal_specification.md.

  • Agentprivacy ranger

    mitchuski/agentprivacy-skills/agentprivacy-skills-v5/persona/agentprivacy-ranger Skill

    1★ repo

    Dark Forest Navigator for 0xagentprivacy. Activates for dark forest strategy, privacy-preserving path optimisation, minimum-exposure routing, cross-chain navigation under adversarial conditions, or any task requiring strategic movement through environments where visibility means vulnerability.

  • Agentprivacy dark forest

    mitchuski/agentprivacy-skills/agentprivacy-skills-v5/role/agentprivacy-dark-forest Skill

    1★ repo

    Dark forest strategy and adversarial environment navigation for 0xagentprivacy. Activates when discussing R(d) strategic disclosure, information asymmetry, predator-prey dynamics in data markets, position-revealing risks, or how to navigate environments where visibility means vulnerability.

  • Legacy refactor plan

    ForeverSc/ai-handrail/skills/legacy-refactor-plan Skill

    1★ repo

    Use when planning actual code changes to a legacy project after guardrails are in place. Triggers when user says "refactor this module", "modernize this code", "plan the migration", "break this into tasks", or after legacy-safety-rails has established protection.

  • Spec generate

    robotka1321/great-product-skills/skills/spec-generate Skill

    no license1★ repo

    Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step workflow. Output in English Markdown format.

  • Project doc generator

    bingooyong/agent-skills/skills/project-doc-generator Skill

    no license1★ repo

    Generate and maintain project documentation systems from structured inputs. Use when (1) creating documentation from spec/requirements/design/tasks, (2) planning doc dependency order and generation sequence, (3) incremental doc updates with consistency checks, (4) generating docs with correct depth for target audience. Focuses on dependency-aware, incremental, audience-appropriate documentation.

  • Refactoring planner

    bingooyong/agent-skills/skills/refactoring-planner Skill

    no license1★ repo

    Analyze code smells, generate refactoring plans with impact assessment and risk evaluation. Use when (1) identifying code smells and technical debt hotspots, (2) planning safe refactoring sequences with dependency awareness, (3) estimating refactoring scope and risk, (4) creating step-by-step refactoring checklists. Outputs prioritized refactoring plans with rollback strategies.

  • Test strategy designer

    bingooyong/agent-skills/skills/test-strategy-designer Skill

    no license1★ repo

    Analyze code changes and design targeted test strategies covering impact scope, test types, and priority. Use when (1) determining what tests are needed after code changes, (2) designing test plans for new features or bug fixes, (3) estimating test effort and coverage gaps, (4) selecting appropriate test types. Outputs actionable test strategies with priority and scope.

  • Content strategy

    yunseo-kim/agent-toolbox/catalog/skills/content-strategy Skill

    no license1★ repo

    Plan content strategy, decide what to create, and build topic clusters with pillar pages and distribution plans

  • Free tool strategy

    yunseo-kim/agent-toolbox/catalog/skills/free-tool-strategy Skill

    no license1★ repo

    Plan, evaluate, or build free tools for marketing purposes including lead generation, SEO value, and brand awareness

  • Launch strategy

    yunseo-kim/agent-toolbox/catalog/skills/launch-strategy Skill

    no license1★ repo

    Plan product launches, feature announcements, and release strategies with timelines, channels, and momentum tactics

  • Pricing strategy

    yunseo-kim/agent-toolbox/catalog/skills/pricing-strategy Skill

    no license1★ repo

    Make pricing decisions, design packaging and tiers, and develop monetization strategy with research methods

  • Project planner

    yunseo-kim/agent-toolbox/catalog/skills/project-planner Skill

    no license1★ repo

    Breaks down complex projects into actionable tasks with timelines, dependencies, milestones, and resource allocation

  • Sprint planner

    yunseo-kim/agent-toolbox/catalog/skills/sprint-planner Skill

    no license1★ repo

    Agile sprint planning with story estimation, capacity planning, velocity tracking, and sprint goal setting

  • Strategy advisor

    yunseo-kim/agent-toolbox/catalog/skills/strategy-advisor Skill

    no license1★ repo

    High-level strategic thinking and business decision guidance for planning, competitive analysis, and direction-setting

  • Requirement parser

    allenli178/yuyan-skills/tech-evaluator/skills/requirement-parser Skill

    1★ repo

    需求拆解Skill,将用户的模糊技术选型需求转化为结构化的评估维度,包括必选项和权重项。

  • Spec driven dev

    medy-gribkov/arcana/skills/spec-driven-dev Skill

    1★ repo

    Specification-driven development with structured requirements, planning workflows, task breakdown, and quality gates. Covers product briefs, PRDs, technical specs, and implementation plans.

  • Testing strategy

    medy-gribkov/arcana/skills/testing-strategy Skill

    1★ repo

    Comprehensive testing expertise across unit, integration, and e2e tests. Covers pytest, Vitest, Jest, Go testing, Playwright, Cypress. Test pyramids, TDD workflow, mocking patterns, coverage targets, property-based testing, snapshot testing, parameterized tests, fixtures, CI integration. Use when writing tests, designing test architecture, improving coverage, or setting up testing infrastructure.

  • Viewing openspec item details

    yu-iskw/openspec-skills/skills/viewing-openspec-item-details Skill

    no license1★ repo

    Displays detailed information about a specific OpenSpec change or specification. Use when you need to read the content of a proposal or spec.

  • Plan and execute

    primeline-ai/primeline-skills/skills/plan-and-execute Skill

    1★ repo

    Use when you have a multi-step task, before touching code. Creates bite-sized implementation plans with TDD emphasis, then executes them in batches with review checkpoints. Prevents the "just start coding" trap.

  • Snap issues

    sadiksaifi/skills/snap-issues Skill

    no license1★ repo

    Turn current context, source references, and repo understanding into independently grabbable GitHub issues. Use when the user wants to break down a PRD, plan, spec, idea discussion, or implementation conversation into vertical issues agents can pick up.

  • Snap prd

    sadiksaifi/skills/snap-prd Skill

    no license1★ repo

    Turn current context, source references, and repo understanding into a complete product-grade PRD published as a GitHub issue. Use when the user wants to spec a feature, formalize requirements, or create an implementation-ready product document.

  • Snap visual

    sadiksaifi/skills/snap-visual Skill

    no license1★ repo

    Create a single-page HTML visual brief to explain a concept, plan, architecture, comparison, or proposal — then open it in the browser. Use whenever the user asks to "explain this visually", "show me an HTML page", "make a visual", "diagram this", "visualize X", or wants something rendered as a page instead of prose. Also reach for this proactively when a dense explanation (an architecture, a migration plan, a set of tradeoffs, a design proposal) would clearly land better as a visual document than a wall of text.

  • Create plan

    corticalstack/flow/.claude/skills/create-plan Skill

    1★ repo

    Research the codebase and author a phased implementation plan under flow/plans/ from an issue / work item or task. Explicit workflow command; run only when invoked via /create-plan or explicitly asked, never autonomously.

  • Implement plan

    corticalstack/flow/.claude/skills/implement-plan Skill

    1★ repo

    Execute an implementation plan from flow/plans/ phase by phase, pausing for verification between phases. Explicit workflow command; run only when invoked via /implement-plan or explicitly asked, never autonomously.

  • Iterate plan

    corticalstack/flow/.claude/skills/iterate-plan Skill

    1★ repo

    Revise an existing implementation plan in flow/plans/ based on feedback, researching when needed. Explicit-only; run only when invoked via /iterate-plan or explicitly asked.

  • Validate plan

    corticalstack/flow/.claude/skills/validate-plan Skill

    1★ repo

    Validate an implementation against its plan, run verification commands, and report issues before commit. Explicit workflow command; run only when invoked via /validate-plan or explicitly asked.

  • Fr goal

    derio-net/super-fr/.hermes/skills/fr/fr-goal Skill

    1★ repo

    Run a feature goal end-to-end autonomously: brainstorm, one batched Q&A, then spec → review → fr-plan → review → TDD implementation → review → single PR, fixing every finding, no intermediate approval gates. ALWAYS use when the operator invokes /fr-goal or /goal, says "build this autonomously", "ask your questions once then build it", "take this to a PR", hands a feature to run unattended, says "auto mode" or spec-to-PR.

  • Fr plan

    derio-net/super-fr/.hermes/skills/fr/fr-plan Skill

    1★ repo

    Write phase-structured plans with operator collaboration. Use when: "write a plan", "fr plan", "create a plan". Invoked by brainstorming handoff.

  • Fr progress

    derio-net/super-fr/.hermes/skills/fr/fr-progress Skill

    1★ repo

    Plan / spec progress reporting, and the repo-state preflight for any repo with docs/superpowers/ or fr config. Use when: "what's in progress", "status board", "audit drift", "spec rollup", "is this plan up to date", "is this repo fr-managed", "legacy v1 plans", "before archiving or moving files under docs/superpowers/".

  • Fr goal

    derio-net/super-fr/.opencode/skills/fr-goal Skill

    1★ repo

    Run a feature goal end-to-end autonomously: brainstorm, one batched Q&A, then spec → review → fr-plan → review → TDD implementation → review → single PR, fixing every finding, no intermediate approval gates. ALWAYS use when the operator invokes /fr-goal or /goal, says "build this autonomously", "ask your questions once then build it", "take this to a PR", hands a feature to run unattended, says "auto mode" or spec-to-PR.

  • Fr plan

    derio-net/super-fr/.opencode/skills/fr-plan Skill

    1★ repo

    Write phase-structured plans with operator collaboration. Use when: "write a plan", "fr plan", "create a plan". Invoked by brainstorming handoff.

  • Fr progress

    derio-net/super-fr/.opencode/skills/fr-progress Skill

    1★ repo

    Plan / spec progress reporting, and the repo-state preflight for any repo with docs/superpowers/ or fr config. Use when: "what's in progress", "status board", "audit drift", "spec rollup", "is this plan up to date", "is this repo fr-managed", "legacy v1 plans", "before archiving or moving files under docs/superpowers/".

  • Fr goal

    derio-net/super-fr/plugins/super-fr/skills/fr-goal Skill

    1★ repo

    Run a feature goal end-to-end autonomously: brainstorm, one batched Q&A, then spec → review → fr-plan → review → TDD implementation → review → single PR, fixing every finding, no intermediate approval gates. ALWAYS use when the operator invokes /fr-goal or /goal, says "build this autonomously", "ask your questions once then build it", "take this to a PR", hands a feature to run unattended, says "auto mode" or spec-to-PR.

  • Fr plan

    derio-net/super-fr/plugins/super-fr/skills/fr-plan Skill

    1★ repo

    Write phase-structured plans with operator collaboration. Use when: "write a plan", "fr plan", "create a plan". Invoked by brainstorming handoff.

  • Fr progress

    derio-net/super-fr/plugins/super-fr/skills/fr-progress Skill

    1★ repo

    Plan / spec progress reporting, and the repo-state preflight for any repo with docs/superpowers/ or fr config. Use when: "what's in progress", "status board", "audit drift", "spec rollup", "is this plan up to date", "is this repo fr-managed", "legacy v1 plans", "before archiving or moving files under docs/superpowers/".

  • Creating eval plan

    jek-bao-choo/productivity-plugins/sales-process/skills/creating-eval-plan Skill

    1★ repo

    Generate modular Evaluation Plan CSV files for Datadog Home Run POC/Trial management. Combines solution-area modules (Infrastructure, APM, Logs, Cloud SIEM, LLM Observability, NDM, RUM, Synthetics, CCM, Security, DBM, Incident Management, BitsAI, Service Management) into a 4-column CSV (Depth, Title, Description, Success Criteria) ready for upload to Home Run. Use when the user asks to create an evaluation plan, eval plan, POC plan, trial plan, Home Run template, or mentions "evaluation plan", "eval plan", "POC plan", "Home Run CSV", or "trial template".

  • Pm embedded prd

    suibianqugenichenghaole/pm-workflow-system/skills/public/pm-embedded-prd Skill

    1★ repo

    Generate embedded PRD deliverables that combine structured requirement documentation with linked demo preview, rule/state/config mappings, and bidirectional navigation between document blocks and demo areas. Use when requirement rules and demo outputs are relatively stable enough to assemble into a reviewable or deliverable "left document / right demo" experience, and when a product manager needs PRD + demo linkage rather than separate artifacts.

  • Pm prd writer

    suibianqugenichenghaole/pm-workflow-system/skills/public/pm-prd-writer Skill

    1★ repo

    Write page-oriented, development-readable Chinese PRD / requirement documents from already discussed product requirements. Use when the user asks to write or rewrite a 需求文档 / PRD, make requirements developer-readable, follow a fixed demand-document format, or organize page structure, interactions, field rules, key logic, and out-of-scope scope without scattering information.

  • Pm requirement intake

    suibianqugenichenghaole/pm-workflow-system/skills/public/pm-requirement-intake Skill

    1★ repo

    Structure product-requirement intake, classify requirement types, actively confirm missing dimensions, and judge whether a request is ready for structure draft, prototype draft, or formal PRD. Use when discussing a new requirement, refining an existing requirement, checking whether requirement information is complete enough to proceed, or helping a product manager narrow options and identify risks before prototype or PRD work.