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

  • Social strategy

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/social-strategy Skill

    0★ repo

    When to activate: social media strategy, Twitter X LinkedIn Instagram TikTok content, posting cadence, community building, social listening, organic social

  • Strategy frameworks

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/strategy-frameworks Skill

    0★ repo

    When to activate: corporate strategy, Porter's 5 Forces, Blue Ocean, BCG Matrix, Ansoff Matrix, Balanced Scorecard, SWOT, strategic planning, scenario planning, strategic narrative

  • Talent strategy

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/talent-strategy Skill

    0★ repo

    When to activate: talent strategy, talent philosophy, employer brand, executive hiring, retention strategy, compensation philosophy, culture performance, EVP, workforce planning

  • User stories

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/user-stories Skill

    0★ repo

    When to activate: user stories, as a user I want, acceptance criteria, story splitting, story mapping, epic, backlog, agile

  • Vision frameworks

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/vision-frameworks Skill

    0★ repo

    When to activate: vision, mission, values, long-range planning, strategic narrative, company direction, north star vision, galvanizing teams, cascading strategy

  • Stakeholder readout

    vermapragya/analytics-skill/skills/stakeholder-readout Skill

    0★ repo

    Structures a stakeholder-ready analysis writeup with TL;DR, evidence, decision, and next steps. Use when the user asks for a readout, analysis writeup, insight doc, exec summary, "share this with the team", "make this stakeholder-friendly", or "summarize the findings."

  • Product designer

    Punpun1643/claude-skills/product-designer Skill

    no license0★ repo

    Produce and refine product-design briefs — the document that turns a rough product idea into a buildable MVP spec: vision, personas, jobs-to-be-done, goals/non-goals, numbered functional requirements, key screens, data model, user stories with acceptance criteria, user journeys, success metrics, risks, and milestones, all grounded in human-centered-design principles. Use this skill WHENEVER the user wants to write, expand, critique, or restructure a product brief, MVP plan, PRD, feature spec, or set of user stories — including phrasings like "write a product spec for X", "turn this idea into an MVP plan", "draft the requirements", "write user stories with acceptance criteria", "design this feature", "what should the MVP scope be", "critique this product plan", or "make a PRD". Also use it proactively when a user describes a product idea and asks how to scope or structure it. The skill enforces HCD principles (visible constraints, reversibility, informative feedback, traceability) and that every requirement is testable and tied to a real user need.

  • Content plan

    lumizone/social-content-os-claude-skill/skills/content-plan Skill

    0★ repo

    Build a social media content plan / calendar from a niche or business. Use when the user asks to plan content, build a content calendar, decide what to post, map a month of posts, or says "content plan", "plan tresci", "zaplanuj miesiac postow", "what should I post this week/month", "content calendar", "posting schedule". Builds a Topic Tree (Niche of One + 3 interests + subtopics), then a 2–4 week calendar where every post is tagged with format, Awareness Funnel stage, funnel layer (ToF/MoF/BoF), hook angle, and CTA, following SGTMS cadence. Outputs a markdown plan plus a table and an importable CSV.

  • Social content os

    lumizone/social-content-os-claude-skill/skills/social-content-os Skill

    0★ repo

    Router and onboarding for the Social Content OS pack — a system for planning and producing high-performing social media content (Instagram, LinkedIn, TikTok, X) based on the Interest Graph / Graffiti playbook (ABC hooks, SGTMS, Awareness Funnel, Best of Nine, carousels, ManyChat monetization). Use when the user wants help with social media content but hasn't picked a specific task, or says "social content os", "pomoz mi z social media", "od czego zaczac z contentem", "help me with my social media", "what should I post". Explains the system, loads the brand profile, and routes to the right sub-skill: content-plan, hook-lab, carousel-builder, caption-writer, or repurpose.

  • Go to market planner

    SkillMedev/solo-founder-stack/skills/go-to-market-planner Skill

    0★ repo

    Build a sequenced go-to-market plan - beachhead ICP, positioning, one or two channels, and dated milestones - instead of a scattershot launch. Use when someone asks "how do I take this to market", "what's my GTM strategy", "which channel should I start with", "who should I sell to first", or is planning a new product or a new market entry. Do NOT use for the dated launch-week timeline and asset checklist - use launch-plan-sequencer instead; for Product Hunt copy and day-of tactics use product-hunt-launch; for deep persona research use icp-persona-builder.

    The same file is in 2 other repositories

  • Pricing strategy

    SkillMedev/solo-founder-stack/skills/pricing-strategy Skill

    0★ repo

    Set or revise pricing for any product by triangulating value, competition, and cost floor into a recommended structure, price points, and a test plan. Use when someone asks "what should I charge", "how do I price my product", "are we priced too low", "should we go usage-based or flat", or is preparing a repricing or a new-product launch. Do NOT use for designing SaaS tier ladders, value metrics, and expansion packaging in detail - use saas-pricing instead; for gym front-end offers and guarantees use gym-pricing-and-guarantees; for checking whether the resulting price produces healthy CAC payback use unit-economics.

    The same file is in 2 other repositories

  • React brief recipes

    jaballer/react-claude-skills/react-brief-recipes Skill

    0★ repo

    30-second component-tree decision recipes for common interview prompts. When the brief drops, look it up here and get tree + state-ownership + must/should/won't + one "wow" detail. Covers pricing card, hero + signup, multi-step onboarding, FAQ, modal, tabs, combobox, comparison table, newsletter, sticky nav, sidebar nav, code block, dashboard card, testimonial carousel, feature grid. Load this skill FIRST when starting any interview build. Triggers on "interview build", "what should I build", "component tree", "where to start", "brief recipe", "pricing card", "hero", "build a form", "build a modal", "build tabs", "build accordion", "build navigation", "build dashboard".

  • Loop

    Lemonaderrrrr/flow-kit/skills/loop Skill

    0★ repo

    A closed-loop delivery engine that wraps any output-oriented task — define spec, get your approval, then autonomously produce + adversarially self-check and iterate (max 3 rounds), show you only when aligned, and re-loop on your feedback until you're satisfied. Orchestrates the other SOPs (build/write/research/plan/analyze) and the two thinking modes. Default Engineer mode. Offer it proactively when a task is a substantial, multi-step deliverable; the user may also invoke it directly. Saves to outputs/loop/.

  • Plan

    Lemonaderrrrr/flow-kit/skills/plan Skill

    0★ repo

    Turn a goal into an executable plan with milestones, dependencies, schedule, and checkpoints. Default Engineer mode. Uses whatever context the user provides as a baseline, fine-tunes from current info, and asks for missing key inputs instead of assuming. Saves to outputs/plans/. Use when the user says "help me plan X", "make a timeline", "schedule this", or invokes the skill.

  • Team

    Lemonaderrrrr/flow-kit/skills/team Skill

    0★ repo

    Run a project as a parallel dev team — Planner decomposes into a task board, dispatches Frontend/Backend engineers concurrently by directory ownership, and gates every ticket through a Reviewer (hard gate + rework loop) before Done. Use when the user says "build this as a team", "parallelize this project", "/flow:team", or hands over a spec/PRD to implement.

  • Brainstorming

    roedyrustam/claudevibeskills/src/brainstorming Skill

    no license0★ repo

    Advanced brainstorming protocol with 2026 Modern Web Guidance. Use this skill whenever the user wants to ideate, plan, architect, or design a new feature, product, or system — especially for web applications. Trigger on phrases like "brainstorm", "let's plan", "how should I approach", "help me design", "what's the best way to build", "I want to create", "give me ideas for", "design document", "technical spec", or "architecture for". Also trigger when the user is starting a new project and needs a structured Design Document (DD) output. Covers RSC, PPR, Server Actions, AI integration, Passkeys, and structured output templates.

  • Prd architect

    roedyrustam/claudevibeskills/src/prd-architect Skill

    no license0★ repo

    Initial guardrail skill that enforces creating a comprehensive Product Requirements Document (PRD) before generating code. Use whenever the user starts a new project or feature and jumps straight to "build me X" without defined requirements. Trigger on phrases like "build me an app that...", "create a system for...", "I want to build...", or any greenfield request lacking clear scope. Also trigger when the user explicitly asks for a PRD or requirements document.

  • House shaper

    argent-gnome/sdlc-skills/skills/house-shaper Skill

    0★ repo

    The house SDLC shaping session — turn a fuzzy idea, backlog item, audible, or decision into ready-to-build planned work (spec + plan + plan-check + reconciled docs) OR a recorded decision (ADR + roadmap). Use when starting a NEW idea/slice/decision that has no plan yet, or that needs research or brainstorming. Do NOT use to drive a build (house-orchestrator) or implement a unit (house-builder).

  • Okr builder

    SkillMedev/remote-team-toolkit/skills/okr-builder Skill

    0★ repo

    Drafts a quarter's OKRs - an inspiring qualitative objective with 3-5 measurable key results, each with a baseline, target, and owner - plus the weekly confidence check-in and end-of-quarter grading cadence. Use when someone asks "help me write OKRs", "are these key results any good", "turn our goals into OKRs for next quarter", or "how do we score our OKRs". Do NOT use for building the full-year company plan that OKRs slot into - use annual-plan instead - or for personal goal-tracking with a check-in partner - use goals-accountability instead.

    The same file is in 2 other repositories

  • Stakeholder update

    SkillMedev/remote-team-toolkit/skills/stakeholder-update Skill

    0★ repo

    Writes project stakeholder updates readable in under 60 seconds - honest RAG status, decisions made, explicit asks with owners and dates, next milestones - tiered to the audience. Use when someone asks "write my weekly project update", "how do I tell stakeholders we're at risk", "draft a status email for leadership", or "my updates get ignored, fix the format". Do NOT use for aggregating many teams' statuses into one engineering-wide report - use eng-status-rollup instead. For monthly investor letters with metrics and asks to VCs, use investor-update-writer; for customer-facing incident status, use status-page-update.

    The same file is in 1 other repository

  • Legal negotiate

    Frog1205/OPC-Skills/skills/legal-negotiate Skill

    0★ repo

    Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

  • Issue plan commit

    usrrname/agent-skills/skills/issue-plan-commit Skill

    no license0★ repo

    Reads from an existing issue, interprets expected outcomes, plans before making changes

  • Kiss plan

    Pr1m4lc0d3/KiSYSTEM/skills/kiss-plan Skill

    no license0★ repo

    Use before writing code for any multi-step task, feature, or new project — orient inside the existing structure first, then turn the request into a short design doc with explicit modules, interfaces, and a verify-stepped build sequence. Use when a task is ambiguous, spans more than one file, or has more than one reasonable interpretation.

  • Mutual action plan

    SkillMedev/outbound-sales-engine/skills/mutual-action-plan Skill

    0★ repo

    Builds a mutual action plan (MAP) with shared milestones, named owners, and buffer-padded dates that drives a qualified deal from verbal intent to signature and go-live. Use when someone asks "build a mutual action plan for this deal", "how do I keep this deal from stalling", "the buyer said yes but nothing is moving", or once a prospect is qualified and has expressed intent to move forward. Do NOT use for preparing the qualification call itself - use discovery-call-prep instead. Do NOT use for scripting the negotiation and close conversation - use closer-sales-script instead.

    The same file is in 1 other repository

  • Sales proposal writer

    SkillMedev/outbound-sales-engine/skills/sales-proposal-writer Skill

    0★ repo

    Writes a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a proposal", "how should I present pricing in this proposal", or when a deal needs a document to move from discovery to close. Do NOT use for a one-page internal decision brief - use one-pager-designer instead; for investor decks use pitch-deck-builder; for setting the underlying price model use pricing-strategy.

    The same file is in 3 other repositories

  • Sql query optimizer

    SkillMedev/data-engineering-pipeline/skills/sql-query-optimizer Skill

    0★ repo

    Diagnoses slow SQL from the execution plan, names the cost driver, and delivers the rewritten query plus index DDL with the expected plan change and write-side cost stated. The general entry point for slow-query work that routes deep cases to specialist skills. Use when someone asks "why is this query slow", "can you optimize this SQL", "what index do I need", "this endpoint got slow and it's the database", or pastes an EXPLAIN output. Do NOT use for deep index strategy across a whole schema - use index-advisor instead; for pure query-shape rewrites when indexes are already right - use query-rewriter instead; for ORM-driven repeated-query patterns - use n-plus-one-hunter instead; for line-by-line EXPLAIN interpretation training - use explain-plan-reader instead; for table partitioning decisions - use partition-planner instead.

    The same file is in 1 other repository

  • Icon system

    SkillMedev/design-system-builder/skills/icon-system Skill

    0★ repo

    Designs or audits an icon set so every glyph shares one grid, stroke weight, corner language, naming convention, and export pipeline, and delivers the written icon spec engineering builds against. Use when someone asks "our icons look inconsistent", "set up an icon grid", "how should we name icons", "audit this icon set", "prep our SVGs for handoff", or is commissioning new icons and needs the rules first. Do NOT use for a single logo mark - use logo-brief-writer instead; for delivering full design specs beyond icons, use design-handoff-doc.

    The same file is in 2 other repositories

  • Prototype spec

    SkillMedev/design-system-builder/skills/prototype-spec Skill

    0★ repo

    Turns a static design into a numbered, testable, dev-ready specification covering every state, interaction, breakpoint, motion detail, and edge case the mockup cannot show. Use when someone asks "write the spec for this screen", "engineering keeps asking what happens when", "document the interactions before handoff", "what states does this component need", or a build came back wrong because behavior was never written down. Do NOT use for the motion token details themselves - use motion-spec instead; for verifying a finished build against the spec, use design-qa-checklist.

    The same file is in 2 other repositories

  • Financial planner

    SkillMedev/founder-fundraising-os/skills/financial-planner Skill

    0★ repo

    Builds a complete personal financial plan - a prioritized order of operations across budgeting, emergency savings, debt payoff, and goals - from the user's actual numbers, then routes each piece to the right specialist skill. Use when someone asks "help me get my finances in order", "where should my money go first", "should I pay off debt or save", "am I doing okay financially", or "build me a financial plan". Do NOT use for constructing the monthly budget itself - use budget-builder instead; for sequencing multiple debts - use debt-payoff-planner; for sizing the cash cushion - use emergency-fund-planner; for investing fundamentals - use investment-basics; for retirement readiness math - use retirement-projection; for lowering a tax bill - use tax-optimization; for evaluating one large purchase - use big-purchase-decision.

    The same file is in 2 other repositories

  • Content refresh auditor

    SkillMedev/seo-organic-growth/skills/content-refresh-auditor Skill

    0★ repo

    Produces a prioritized refresh plan for a decaying published page - a refresh/consolidate/retire verdict plus ordered update actions to recover or grow rankings. Use when an existing URL is losing traffic or rankings, during a periodic content-decay sweep, or when asked to "update", "refresh", or "revive" an old article. Do NOT use when planning coverage for a draft that is not yet published or ranking - use SERP Gap Analyzer instead.

    The same file is in 1 other repository

  • Delivery engine

    cody-hutson/pmo-platform/operations/skills/delivery-engine Skill

    no license0★ repo

    Operational backbone for backlog health through release readiness. Modes: Backlog scan · Ticket insight · DoR gate · Sprint planning · Execution control · DoD gate · RAID updates. Use for sprint planning, backlog review, quality gates, or velocity tracking across Agile and Waterfall governance. Triggers: "run DoR on this", "run DoD on this", "check this backlog", "plan the sprint", "velocity check", "is this release ready", "update the RAID log."

  • Pmo program manager

    cody-hutson/pmo-platform/operations/skills/pmo-program-manager Skill

    no license0★ repo

    Program Manager Specialist — drives a program's multiple coordinated workstreams to outcomes, deciding which cross-project signal moves the delivery plan and binding the program's risk posture to its delivery decisions. Operates at the program tier above any single project's delivery and below portfolio strategy, across agile and waterfall governance. Composes ppm-agent (strategic synthesis + intake-governance) + delivery-engine (backlog→release-readiness mechanics) — invokes them, never re-implements them. Modes: Cross-Project Risk & Dependency Synthesis · Program Delivery Posture · Program Release-Readiness · Program Intake & Capacity Trade-off · Program RAID & Decision Stewardship. Use when one program's multi-workstream delivery needs a risk read, a posture call, a go/no-go, an intake trade-off, or RAID stewardship. Triggers: "program-level risk to delivery", "is this program ready to release", "across these workstreams", "program go/no-go", "cross-project dependency", "how's the program tracking".

  • Pmo project manager

    cody-hutson/pmo-platform/operations/skills/pmo-project-manager Skill

    no license0★ repo

    Project Manager Specialist — owns a single named project's delivery end-to-end at the single-project tier (not a program or portfolio): renders the project's go/no-go, owns its RAID, stewards its milestone. Composes delivery-engine only — invokes it across modes A/C/D/E/F/G, never re-implements it; the value-add is single-project delivery accountability plus cross-mode coherence within delivery-engine (a DoR gap conditioning the sprint plan, a DoD failure originating a RAID entry). Modes: Project Backlog & Readiness Health · Project Sprint Planning & Execution · Project Release-Readiness (DoD) · Project RAID & Decision Stewardship. Use when one named project needs its delivery owned. Triggers: "is this project ready to release", "run DoR/DoD on this project", "plan this project's sprint", "check this project's backlog", "update this project's RAID", "this project's go/no-go". Routes program / multi-workstream requests to pmo-program-manager; routes ceremony-facilitation requests to pmo-scrum-master.

  • Implementation planner

    cody-hutson/pmo-platform/release/skills/implementation-planner Skill

    no license0★ repo

    Converts build-reviewer findings registers into sequenced, minimal-change remediation implementation plans for any governed document pack — Copilot Builder Agent, PMO platform, or generic. Domain-specific planning context loaded from pluggable domain packs under `references/domain-packs/`. Applies the Minimal-Change Remediation Bias and classifies every confirmed finding to one of 8 remediation types (RT-1 text correction through RT-8 accepted residual). Produces implementation records (RI-NNN) as Edit-ready specs and Bash scripts directly consumable by Claude Code's native tools per the reference workflow in `release/references/how-to/implementation-execution-pattern.md`. Use when the user has a build-reviewer findings register ready for planning, needs remediation sequencing, or wants to plan the fixes before execution.

  • Pmo software engineer

    cody-hutson/pmo-platform/release/skills/pmo-software-engineer Skill

    no license0★ repo

    Software Engineer Specialist — executes end-to-end Stage-6 Engineering; turns an approved implementation plan into executed change, verification, and a PR. Composes implementation-planner (RT-classification + Edit-ready spec generation from a findings register) — invokes it, never re-implements it. Mode: Development. Input is scoped to an executable plan / findings register; a bare ticket with no plan routes to planning first. Use when an approved plan or findings register is ready to build. Triggers: "implement this plan", "execute the remediation plan", "engineer this change", "run the Stage-6 build", "turn this plan into a PR".

  • Release planner

    cody-hutson/pmo-platform/release/skills/release-planner Skill

    no license0★ repo

    Plans the PMO platform release lifecycle. Modes: Backlog analysis · Release planning · Dry run. Analyzes the improvement backlog, maps dependencies, suggests release bundles, generates release plans, and produces dry-run diffs. Read-only — never modifies governance files. Triggers: "review the backlog", "plan the release", "bundle the release", "dry run", "show me the diffs", "what's in v[X.Y]."

  • Roadmap curator

    cody-hutson/pmo-platform/release/skills/roadmap-curator Skill

    no license0★ repo

    Keeps the living initiative roadmap current as work arrives — the ongoing roadmap-grooming function. Classifies new or changed issues into the ratified initiative → capability-slice → horizon, syncs the operator's board fields + roadmap §3, and surfaces two-surface drift. Surface-agnostic: references the board via registered depersonalization tokens only, never a literal board id. Modes: Incremental Maintenance · Re-baseline · Drift Audit. Triggers: "groom the roadmap", "classify this issue into the roadmap", "place this on the roadmap", "re-baseline the initiative set", "audit roadmap drift", "is the roadmap in sync", "keep the roadmap current."

  • Backend module builder

    vipincode/exr-agent-skills/.claude/skills/backend-module-builder Skill

    no license0★ repo

    Build a backend feature/module from an approved FEATURE_PLAN, enforcing reuse so no duplicate utils, middleware, types, or helpers get created. Use this whenever the user wants to implement, build, or generate a planned feature — "build the auth module", "implement FEATURE_PLAN_products.md", "now build it", "code up the orders feature". It reads ARCHITECTURE.md + MODULE_REGISTRY.md + the feature plan, searches for existing reusable code BEFORE creating anything, builds the module in the project's paradigm, then updates the registry. It does NOT plan features (that is backend-feature-planner) and does NOT write tests (that is backend-test-writer). Works in any project in the Express/TS convention family with the contract files.

  • Backend onboard

    vipincode/exr-agent-skills/.claude/skills/backend-onboard Skill

    no license0★ repo

    Make any project ready for the backend toolkit (backend-feature-planner, backend-module-builder, backend-test-writer) by establishing its contract files. Use this as the entry point whenever the user points the toolkit at a directory — "set up my existing API for this", "onboard this repo", "I want to use these skills on my current project", "get this project ready", or starting work in a folder that has no ARCHITECTURE.md / MODULE_REGISTRY.md yet. For an EXISTING codebase it scans the repo and generates a DESCRIPTIVE ARCHITECTURE.md plus a MODULE_REGISTRY.md seeded with all existing reusable code, so feature work reuses what's there instead of duplicating it (DRY). For an EMPTY directory it hands off to express-ts-bootstrap. It is non-destructive — it never refactors existing code, only writes the contract files. After onboarding, plan/build/test happen through the dedicated skills.

  • Skill snapshot v1

    vipincode/exr-agent-skills/.claude/skills/frontend-feature-planner-workspace/skill-snapshot-v1 Skill

    no license0★ repo

    Plan how an already-designed Next.js/React frontend feature will BIND to a backend API — before any binding code is written. Use this whenever the user has a built (or in-progress) design and wants to wire it to an endpoint: "plan the products API binding", "wire up the orders screen to the API", "bind this design to the auth endpoints", "how do I connect this page to the backend", "make this design functional with the API", or simply names an API/endpoint to hook a frontend feature to. Its signature move: it reads the REAL backend (monorepo source first, then the backend's contract files, then an OpenAPI/Swagger spec, then a user-pasted sample) to learn the actual endpoints, request/response envelope, auth, and validation — so the plan binds to ground truth instead of a guessed contract. It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md, maps which existing design components consume which fields, and writes an editable _docs/FEATURE_PLAN_<name>.md (types, Zod schemas, BFF routes, axios api fns, TanStack Query hooks, data-binding map). It does NOT write binding code (that is frontend-module-builder), does NOT build the design/components (that is figma-to-component / html-to-component), does NOT write tests (frontend-test-writer), and is NOT for backend/server planning (that is backend-feature-planner). Frontend / Next.js / React / API-binding scope only.

  • Frontend feature planner

    vipincode/exr-agent-skills/.claude/skills/frontend-feature-planner Skill

    no license0★ repo

    Agent Skills for building production-grade Express + TypeScript + Mongoose backends with Claude Code

  • Frontend module builder

    vipincode/exr-agent-skills/.claude/skills/frontend-module-builder Skill

    no license0★ repo

    Build the API binding for an already-designed Next.js/React feature from an approved FEATURE_PLAN — wiring the existing design to a real backend endpoint and making it functional, while enforcing reuse so no duplicate components, hooks, schemas, or utils get created. Use this whenever the user wants to implement/build/execute a planned frontend binding — "build the products binding", "implement FEATURE_PLAN_products.md", "now make this design functional", "wire up the orders screen", "bind it to the API". It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md + the feature plan, searches for existing reusable code BEFORE creating anything, writes the feature-module binding layer (types/schema/api/hooks) and edits the built design to consume it (dropping hardcoded samples), unwraps the response envelope + validates with Zod, uses TanStack Query for server state, then updates the registry. It does NOT plan the binding (that is frontend-feature-planner), does NOT build/redesign components from Figma or HTML (that is figma-to-component / html-to-component), and does NOT write tests (that is frontend-test-writer). It is NOT for backend/server code (that is backend-module-builder). Frontend / Next.js / React / API-binding scope only.

  • Frontend onboard

    vipincode/exr-agent-skills/.claude/skills/frontend-onboard Skill

    no license0★ repo

    Make any existing frontend ready for the frontend toolkit (frontend-feature-planner, frontend-module-builder, frontend-test-writer, frontend-code-review) by establishing its contract files. Use this as the entry point whenever the user points the frontend toolkit at a directory — "set up my existing Next.js app for these skills", "onboard this React frontend", "I want to use these skills on my current UI", "get this client ready", or starting work in a frontend folder that has no ARCHITECTURE.md / MODULE_REGISTRY.md yet. For an EXISTING frontend it scans the repo and generates a DESCRIPTIVE ARCHITECTURE.md plus a MODULE_REGISTRY.md seeded with all existing reusable components, hooks, schemas, lib utils, and feature modules, so feature work reuses what's there instead of duplicating it (DRY). For an EMPTY directory it hands off to nextjs-bootstrap. It is non-destructive — it never refactors existing code, only writes the contract files. After onboarding, plan/build/test/review happen through the dedicated frontend skills. This is the FRONTEND twin of backend-onboard — do NOT use it on an Express/Mongoose API (that is backend-onboard).

  • Prd creator

    vipincode/exr-agent-skills/.claude/skills/prd-creator Skill

    no license0★ repo

    Turn an app idea into a production-grade PRD, then shard it into per-module briefs that feed module-planner. Use this whenever the user wants to plan a whole app or product — "I want to build a blog / e-commerce app / SaaS", "create a PRD", "help me plan this app", "scope my product idea", "divide the PRD into modules", "shard the PRD" — or describes a product vision spanning multiple features, even if they never say "PRD". It takes the user's points, suggests improvements and standard production features they missed (auth, payments, admin, SEO — the user keeps or rejects each), writes _docs/prd/PRD.md, and on approval shards it into _docs/features/<module>/<module>-module.md briefs tagged backend/frontend/fullstack. Also use it to MODIFY an existing PRD (change scope, add features, re-shard). It does NOT do technical feature planning (that is module-planner), does NOT write code, and does NOT scaffold projects — product scope only, upstream of the whole toolkit.

  • Task decomposition

    scoobydrew83/skills/plugins/coordinated-skills/skills/task-decomposition Skill

    0★ repo

    DEPRECATED — this skill was merged into `overwhelm-breakdown` on 2026-06-16 because the two were competing for the same triggers. Do NOT trigger this skill. If you see this description matching a user request, use `overwhelm-breakdown` instead — it now covers "I'm overwhelmed, where do I start?" alongside "break this big thing down for me", with the worked reporting-system example, the size-by-time-AND-energy guidance, and the "use real tools only" caution that used to live here. This tombstone exists only because the source file could not be deleted in the build environment; treat it as a no-op redirect.

  • Client onboarding os

    search-atlas-group/amm-founding-circle/skills/client-onboarding-os Skill

    0★ repo

    Orchestrate the first 90 days of a new SEO/AEO client engagement — from pre-kickoff access gathering through Day 90 quarterly re-planning. Produces a week-by-week schedule that runs foundational skills (Brand Kit, SERP Intent Decoder) in Weeks 1-2, diagnostic audits (LLM Citation Audit, Entity & Topical Authority Mapper, GBP Competitor Audit or Internal Linking Auditor or Competitor Content Gap depending on business type and engagement scope) in Weeks 3-5, consolidation into the first 90-day plan via AEO/LLM Content Planner in Week 6, and structured execution with Day-30/60/90 checkpoints through the remainder. Routes every actual audit or fix to the specific skill that does the work — this skill is pure sequencing. Use whenever an agency, consultant, or in-house lead is taking on a brand-new client or starting a greenfield AEO/SEO engagement, or whenever someone asks "where do I start with a new client," "what's the onboarding process," "how do I kick off this engagement," "first 90 days for new client," "SEO onboarding checklist," or "AEO consulting onboarding." Chains with every other skill in the pack via sequential invocation; output serves as the engagement's master schedule. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.

  • Content brief generator

    search-atlas-group/amm-founding-circle/skills/content-brief-generator Skill

    0★ repo

    Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.

  • Dispatch and brief

    search-atlas-group/amm-founding-circle/skills/dispatch-and-brief Skill

    0★ repo

    Split one big job across several agents running at once — and write each one a tight, self-contained brief so it works its slice instead of burning its effort rediscovering the whole job. This is context engineering made practical: the agent only knows what you tell it, so a good brief is the difference between "five agents at once" being leverage and being five shallow drafts. Teaches split → brief → gate, and how to keep your main conversation lean by delegating the messy work. Use when a job is too big for one pass (a multi-section audit, a batch of pages, a repo-wide cleanup), when parallel agents keep coming back with thin or overlapping work, when your main chat gets clogged with raw output, or when you're on Level 4 and want the split/brief step done right.

  • Keyword deep dive

    search-atlas-group/amm-founding-circle/skills/keyword-deep-dive Skill

    0★ repo

    Use when planning to rank for a specific keyword. The agent Googles it, reads the top 10, classifies intent, reads the top 3 competitor pages, and produces a 90-day ranking plan with intent, SERP analysis, and content recommendations. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.

  • Thread to spec

    search-atlas-group/amm-founding-circle/skills/thread-to-spec Skill

    0★ repo

    Convert a pasted product, marketing, or engineering discussion into a scoped implementation spec with acceptance checks and explicit out-of-scope boundaries.

  • Partition planner

    SkillMedev/database-performance/skills/partition-planner Skill

    0★ repo

    Produces a partitioning or sharding plan for an oversized table - range/list/hash strategy, partition-key choice, composite-key and pruning constraints, and a verdict on whether to partition at all. Use when one table has grown past tens of millions of rows or hundreds of GB, vacuum/autovacuum on it runs for hours, retention deletes are giant DELETEs, or you are deciding between range/list/hash partitioning or sharding a hot table. Do NOT use when the goal is choosing indexes for specific slow queries - use index-advisor instead.

    The same file is in 1 other repository

  • Goldengoal

    lroolle/skills/skills/goldengoal Skill

    0★ repo

    Goal engineering for agentic loops -- a goal is a contract, not a wish. Composes fuzzy intent into a goal brief plus a /goal condition, or sharpens an existing draft against five contract gates (outcome, evidence, boundary, stop rules, pause conditions). Calibrates to task weight: trivial skips, simple gets three lines, complex gets pre-mortem. Fires on three branches: defining a task or setting up /goal or /loop ("I want to build", "help me start", "define the task"); checking whether a goal, spec, or requirement is clear enough ("sharpen this", "is this goal clear"); and recovering after a loop drifted or built the wrong thing. Mid-execution corrections with clear direction don't need a contract -- just make the correction.

  • Karvey grill

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-grill Skill

    0★ repo

    Pre-spec interrogation. Interviews the engineer relentlessly about their problem before writing any spec. Use at the start of every new feature or initiative — before karvey-init. Triggers include "grill me", "entrevístame", "interview me", "quiero especificar algo", "I want to spec something", "tengo una idea", "I have an idea", "necesito una feature", "I need a feature", "spec-driven", "SDD", "kiro", "gstack", "Garry Tan", "office hours", "producto 10 estrellas", "10-star product", "reframe", "PRD", "método de desarrollo", "development method".

  • Karvey init

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-init Skill

    0★ repo

    Initialize a new Karvey spec. Creates the directory structure, spec.json, and registers the Epic in ClickUp (or PLAN.md if not using ClickUp). Use after karvey-grill or when starting a new feature. Triggers include "karvey init", "iniciar spec", "init spec", "nueva feature", "new feature", "nuevo cambio", "new change", "spec-driven", "SDD", "kiro", "cc-sdd", "gstack", "Garry Tan", "PRD", "iniciar proyecto spec-driven", "start spec-driven project", "nuevo método", "new method", "scaffolding".

  • Karvey qa

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-qa Skill

    0★ repo

    QA code review in 8 dimensions (Security with OWASP Top 10 + STRIDE, Errors, Consistency, Impact, Env vars, Versioning, Second opinion cross-model, Visual audit vs design-spec). Creates REVISION_PR document, ClickUp tasks or PLAN.md entries. Notifies Google Chat. Triggers include "karvey qa", "code review", "revisión de código", "QA".

  • Karvey requirements

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-requirements Skill

    0★ repo

    Generate EARS-format requirements and spec-delta for a Karvey spec. Creates Features in ClickUp or updates PLAN.md. Use after karvey-init. Triggers include "karvey requirements", "generar requisitos", "generate requirements", "especificar requisitos", "specify requirements".

  • Karvey

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey Skill

    0★ repo

    Orchestrator of the Karvey Method — the complete spec-driven development (SDD) pipeline, stack-agnostic. Shows the pipeline state, guides which skill to run at each phase, and is the method's entry point. A synthesis of first-hand experience + Kiro + gstack. Triggers include "karvey", "método karvey", "karvey method", "pipeline karvey", "qué sigue en karvey", "what's next in karvey", "iniciar proyecto", "start project", "spec-driven", "spec driven development", "SDD", "specification-driven", "kiro", "cc-sdd", "openspec", "gstack", "g-stack", "Garry Tan", "spec kit", "PRD", "requirements engineering", "living specs", "método de desarrollo", "development method", "development pipeline", "SDLC", "desarrollo con IA", "AI-assisted development", "agentic development", "equipo virtual de ingeniería", "virtual engineering team", "vibe coding".

  • Product roadmap

    SkillMedev/product-manager-stack/skills/product-roadmap Skill

    0★ repo

    Turns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter. Use when someone asks "build our product roadmap", "turn these priorities into a roadmap", "execs want committed ship dates for next year", or needs to communicate direction without over-promising. Do NOT use for company-wide annual operating plans - use annual-plan instead; for defining the goals a roadmap serves, use okr-builder; for scheduling work inside a sprint, use sprint-planning.

    The same file is in 1 other repository

  • Sprint planning

    SkillMedev/product-manager-stack/skills/sprint-planning Skill

    0★ repo

    Facilitates sprint planning end to end - backlog refinement checks against a Definition of Ready, a one-sentence sprint goal, capacity math from velocity and PTO, story selection and team commitment, task breakdown, and flagged risks with owners. Use when a team asks "plan our next sprint", "how much should we commit to", "write a sprint goal", or keeps blowing sprint forecasts. Do NOT use for running the retrospective after the sprint ends - use sprint-retro-facilitator instead.

    The same file is in 1 other repository

  • Technical spec

    SkillMedev/product-manager-stack/skills/technical-spec Skill

    0★ repo

    Writes engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.

    The same file is in 1 other repository