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

  • Lesson plan differentiator

    JJuice22/classroom-ready-ai-skills/skills/lesson-plan-differentiator Skill

    1★ repo

    Adds research-based differentiation layers to any existing lesson plan, activity, or assignment using Universal Design for Learning (UDL) principles, MTSS tiered support structures, and evidence-based accommodation strategies. Trigger this skill whenever the user mentions differentiating a lesson, adding accommodations or modifications, making a lesson accessible for all learners, adapting a lesson for IEP students or ELL students or advanced learners, adding scaffolds or extensions, making a lesson UDL-compliant, or asking how to meet the needs of diverse learners. Also trigger when the user pastes a lesson plan and says "help me differentiate this", "make this work for all my kids", "add supports for my struggling students", or "what can I do for my students with IEPs?" Works with pasted lesson plans, uploaded .docx files, or verbal descriptions of a lesson.

  • Substitute lesson plan builder

    JJuice22/classroom-ready-ai-skills/skills/substitute-lesson-plan-builder Skill

    1★ repo

    Generates complete, self-contained substitute lesson plans from any existing lesson, unit, or subject description — with enough detail that a non-specialist substitute teacher can deliver quality instruction without additional support. Trigger this skill whenever the user needs a sub plan, is preparing for an absence, needs emergency lesson plans, wants to leave instructions for a substitute teacher, needs a lesson that can run itself, or asks "what can I leave for a sub?" Also trigger when the user says "I need a sub plan for tomorrow", "I'm going to be absent", "help me write sub plans", or "I need something a sub can do with my class." Works with existing lesson content, a topic description, or just a grade level and subject — even with minimal input, this skill produces a complete, functional plan.

  • Android monetization

    Mcgrass-ops/android-studio-pipeline/skills/android-monetization Skill

    1★ repo

    Monetization strategy for an Android app. Use AFTER android-product-planning and BEFORE android-compose-design. Takes the planning spec's monetization field and deepens it into a concrete model (free+ads, one-time purchase, freemium subscription, IAP, or B2B/strategic-free), pricing with regional/PPP notes, paywall placement and copy, free-tier scoping, the funnel and activation events to instrument, billing SDK choice (Play Billing, RevenueCat), Play Store subscription compliance, and an experimentation plan. Enforces a replan loop back to planning if the model changes the product. Trigger on "how should this app make money", "add a paywall", "pricing", "monetization", "subscription", or automatically once a planning spec exists.

  • Android product planning

    Mcgrass-ops/android-studio-pipeline/skills/android-product-planning Skill

    1★ repo

    Product planning, retention, and Android-platform discovery. Use BEFORE the android-compose-design skill - whenever the user wants to build a new app, add a major feature, or scope a product from a one-sentence prompt. Asks 5-11 questions covering loop, Jobs-to-be-Done, win/lose state, retention targets, primary screen, monetization, activation event, and (conditional) hook and pre-mortem. Detects product, retention, and platform contradictions (viral-vs-accountability, weak Investment phase, monetization mismatched with retention curve, notification timing, missing offline fallback). Surfaces the 11 Android-platform decisions (notifications, permissions, deep links, widgets, offline, form factors, AI cost, Vitals, Material 3 Expressive, Data Safety, ASO) that anchor what the design skill builds. Produces a one-page spec the design skill consumes. Use proactively - most one-sentence prompts hide product incoherence the user hasn't noticed yet.

  • Research proposal

    bydeng01/phd-application-skill/skills/research-proposal Skill

    1★ repo

    Draft a PhD research proposal or research plan aligned to a specific lab's current and future agenda. Use this whenever the user needs a research proposal, project proposal, research statement, or research plan for a PhD application or a particular professor — e.g. "write a research proposal for the Smith lab", "I need a 2-page research plan for my Cambridge application", "draft a PhD proposal on diffusion models for this professor", or "help me turn my interests into a proposal that fits her work". Builds a concrete, feasible project at the intersection of the lab's open problems and the applicant's strengths, grounded in real prior work, as a draft the applicant authors and refines. Trigger whenever the intent is to produce a research proposal tied to a PhD opportunity.

  • Motion spec

    SkillMedev/designer-to-dev-handoff/skills/motion-spec Skill

    1★ repo

    Specifies animation and motion precisely - duration, easing curve, trigger, and intent - for accurate engineer implementation. Use when handing off transitions, micro-interactions, or loading states.

    The same file is in 1 other repository

  • Prototype spec

    SkillMedev/designer-to-dev-handoff/skills/prototype-spec Skill

    1★ 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

  • Responsive spec

    SkillMedev/designer-to-dev-handoff/skills/responsive-spec Skill

    1★ repo

    Specifies responsive behavior across breakpoints - layout reflow, content priority, touch targets, and fluid-versus-stepped scaling rules - precisely enough for engineers to implement directly. Use when someone asks "how should this work on mobile", "spec the breakpoints", "write the responsive rules for this page", or is adapting a single-viewport design for multi-device use. Do NOT use for static measurements inside one frame - use redline-annotation instead; for the overall handoff package with flows and edge cases, use design-handoff-doc.

    The same file is in 1 other repository

  • Deal analysis

    yeshelloAB/investment-analysis-skills/skills/deal-analysis Skill

    1★ repo

    Analyses M&A transactions: deal structure, valuation (comps, premium, implied multiples), strategic rationale, synergy assessment, and risk (regulatory, integration, financing). Supports investor and full practitioner (advisory) modes. Use for: analysing a deal, assessing whether an acquisition is fairly priced, evaluating a takeover bid, reviewing synergy claims, determining accretion/dilution, or advising a deal team. Triggers on: "M&A", "acquisition", "merger", "deal", "takeover", "bid", "deal analysis", "is this priced fairly?", "what are the synergies?", "will this be accretive?", "what's the premium?", "comps", "EV/EBITDA", "deal multiples", "we're advising on this", "recommend to the board", "walk-away price", "fairness opinion", "bid strategy", or any corporate transaction request. Use this skill for deal situations : do not default to stock-investment-analysis when a transaction is the subject.

  • Strategic moat agent

    yeshelloAB/investment-analysis-skills/skills/strategic-moat-agent Skill

    1★ repo

    Use this skill for competitive moat and strategic durability analysis of any listed company or sector. Covers moat type and width, Porter's Five Forces, pricing power, barriers to entry, market position, TAM trajectory, disruption risk, and credible competitive threats. Returns a structured assessment ready for standalone use or multi-agent workflows. Trigger on questions about: competitive advantage, how defensible a business is, whether a company can hold its market position, barriers to entry in an industry, pricing power evidence, who the real competitors are, business model durability, disruption risk, industry dynamics, or strategic positioning. Do NOT use for: valuation or DCF analysis (use stock-investment-analysis), management or CEO quality (use management-quality-agent), ESG or ethics (use values-esg-agent), or full multi-lens stock assessments (use stock-orchestrator).

  • Plan your exit

    kwakseongjae/some-engineer-mind/plan-your-exit Skill

    1★ repo

    Treats failure as a precondition for risky work. Before deploys, data deletions, migrations, force pushes, dependency upgrades, or other hard-to-undo actions, this skill builds the retreat path first — dry-run, backup, staged rollout, explicit rollback procedure written down — so the user can enter the action with composure. 실패할 가능성이 있는 작업에 들어가기 전에 되돌아올 길을 먼저 마련하는 엔지니어링 철학 스킬.

  • Spec diff

    Xindaan/claude-skills/skills/spec-diff Skill

    1★ repo

    Erstellt einen vollständigen, bijektiven Vergleichsreport zwischen zwei Versionen einer technischen Spezifikation (PDF, DOCX, Markdown, HTML, XML/XSD oder Textdateien). Verwende diesen Skill immer wenn der User zwei Versionen eines Dokuments oder einer Spezifikation vergleichen will — egal ob "Vergleich", "Diff", "Delta", "was hat sich geändert", "Änderungsanalyse", "compare versions", "changelog erstellen", "Unterschiede finden", "v6 vs v7", "alt gegen neu", oder ähnliche Formulierungen. Auch geeignet wenn der User ein Änderungsdokument, eine Migrationsübersicht, ein Delta-Dokument oder eine Impact-Analyse zwischen Dokumentversionen erstellen will. Funktioniert mit einzelnen Dateien ebenso wie mit ganzen Dokumentfamilien (z.B. mehrteilige TRs, Normen, Standards mit Schema-Paketen).

  • Strategy

    bromso/metapowers/plugins/branding/skills/strategy Skill

    1★ repo

    Define brand positioning, values, personality, and competitive differentiation

  • Strategy

    bromso/metapowers/plugins/coaching/skills/strategy Skill

    1★ repo

    Review strategy through the lens of a business strategist

  • Compliance roadmap

    bromso/metapowers/plugins/compliance/skills/compliance-roadmap Skill

    1★ repo

    Build a phased compliance roadmap with milestones, dependencies, and resource needs

  • Evidence plan

    bromso/metapowers/plugins/compliance/skills/evidence-plan Skill

    1★ repo

    Design evidence collection strategy per control

  • Implementation plan

    bromso/metapowers/plugins/compliance/skills/implementation-plan Skill

    1★ repo

    Create phased implementation plan for control deployment

  • Plan

    bromso/metapowers/plugins/development/skills/plan Skill

    1★ repo

    Break a feature into a detailed implementation plan with bite-sized tasks

  • Plan

    bromso/metapowers/plugins/finance/skills/plan Skill

    1★ repo

    Define strategic financial objectives, KPIs, and planning assumptions

  • Incident response plan

    bromso/metapowers/plugins/legal/skills/incident-response-plan Skill

    1★ repo

    Create data breach and security incident response plan

  • Stakeholder needs

    bromso/metapowers/plugins/legal/skills/stakeholder-needs Skill

    1★ repo

    Identify legal needs per business unit, product, and stakeholder group

  • Training plan

    bromso/metapowers/plugins/legal/skills/training-plan Skill

    1★ repo

    Design legal compliance training program for the team

  • Content strategy

    bromso/metapowers/plugins/marketing/skills/content-strategy Skill

    1★ repo

    Plan content pillars, editorial calendar, and distribution strategy

  • Free tool strategy

    bromso/metapowers/plugins/marketing/skills/free-tool-strategy Skill

    1★ repo

    Plan free tools and calculators for acquisition

  • Launch strategy

    bromso/metapowers/plugins/marketing/skills/launch-strategy Skill

    1★ repo

    Plan and execute product or feature launches

  • Pricing strategy

    bromso/metapowers/plugins/marketing/skills/pricing-strategy Skill

    1★ repo

    Evaluate pricing models, tiers, and packaging strategy

  • Capacity planning

    bromso/metapowers/plugins/project-management/skills/capacity-planning Skill

    1★ repo

    Plan team capacity across sprints accounting for holidays and availability

  • Estimation

    bromso/metapowers/plugins/project-management/skills/estimation Skill

    1★ repo

    Estimate work using story points, T-shirt sizing, or planning poker

  • Roadmap

    bromso/metapowers/plugins/project-management/skills/roadmap Skill

    1★ repo

    Build a release roadmap with milestones, themes, and timeline

  • Sprint planning

    bromso/metapowers/plugins/project-management/skills/sprint-planning Skill

    1★ repo

    Plan the sprint — select stories, define sprint goal, assign capacity

  • Stakeholder map

    bromso/metapowers/plugins/project-management/skills/stakeholder-map Skill

    1★ repo

    Identify and map stakeholders by influence, interest, and communication needs

  • Stakeholder update

    bromso/metapowers/plugins/project-management/skills/stakeholder-update Skill

    1★ repo

    Generate stakeholder status update with progress, risks, and asks

  • User stories

    bromso/metapowers/plugins/project-management/skills/user-stories Skill

    1★ repo

    Write user stories with acceptance criteria following INVEST principles

  • Containment strategy

    bromso/metapowers/plugins/security/skills/containment-strategy Skill

    1★ repo

    Define containment, eradication, and isolation procedures

  • Encryption strategy

    bromso/metapowers/plugins/security/skills/encryption-strategy Skill

    1★ repo

    Plan encryption at rest, in transit, and key management

  • Monitoring strategy

    bromso/metapowers/plugins/security/skills/monitoring-strategy Skill

    1★ repo

    Design security monitoring, alerting, and observability

  • Pentest plan

    bromso/metapowers/plugins/security/skills/pentest-plan Skill

    1★ repo

    Plan penetration testing scope, methodology, and rules of engagement

  • Recovery plan

    bromso/metapowers/plugins/security/skills/recovery-plan Skill

    1★ repo

    Design disaster recovery and system restoration procedures

  • Gen brief

    tchr-dev/autonovel/.claude/skills/revision/gen-brief Skill

    1★ repo

    Auto-generate a chapter revision brief from structured feedback (eval JSON + reader panel JSON + adversarial cuts JSON + Opus review items). Output is a markdown brief suitable as input to gen-revision. Picks the right brief shape (compression / expansion / dramatisation / character-deepening / consistency).

  • Grizzly plan

    HarishDvs/Grizzly/skills/grizzly-plan Skill

    1★ repo

    Plan chapters, arcs, or sequences. Use when the user wants to plan what happens next, structure an arc, outline a chapter, decide POV, or think through story structure. Integrates the technique deck for structural moves.

  • Fast prototype

    tibichi/fast-preset/skills/fast-prototype Skill

    1★ repo

    Build or iterate an Astro/Tailwind/DaisyUI coded prototype where JSON files in src/data are the editable data layer. Reads BRIEF.md to drive scope; _assumed records are tracked but render exactly like verified records (no visible tells). Use when the user wants a working prototype rather than a plan or spec.

  • Startup go to market

    RashiD2801/Skills/startup-go-to-market Skill

    no license1★ repo

    Go-to-market strategy and step-by-step startup roadmap — India-first launch, MVP scope definition, pricing strategy, distribution channels, expansion sequencing (India → Asia/Middle East → Europe → US), and phased milestones. Usable standalone or as Phase 3 of the startup-analyzer pipeline.

  • Content brief

    busyeugene/content-marketing-skills/content-brief Skill

    1★ repo

    Use when the user wants a content brief, SEO outline, SERP analysis, or blog post plan for a target keyword. Produces a full brief (outline, entities, PAA, competitor summary, unique angle) ready for a writer or the blog-post skill.

  • Launch plan

    ramanbamba/10x-pm/skills/launch-plan Skill

    1★ repo

    Build a go-to-market launch plan with tiering, owner matrix, timeline, and go/no-go checklist. Use when the user says "plan this launch", "GTM plan", "launch checklist", "release plan for [feature]", or is preparing to ship something to customers.

  • Prd

    ramanbamba/10x-pm/skills/prd Skill

    1★ repo

    Draft a product requirements document (PRD) from a rough idea, feature request, or problem statement. Use when the user says "write a PRD", "spec this out", "draft requirements", "product spec", or shares a feature idea they want documented for engineering and design.

  • Roadmap

    ramanbamba/10x-pm/skills/roadmap Skill

    1★ repo

    Build a Now/Next/Later product roadmap organized by themes with confidence levels and kill criteria. Use when the user says "build a roadmap", "roadmap for next quarter/half/year", "now next later", or needs to turn a strategy and backlog into a communicable plan.

  • Stakeholder comms

    ramanbamba/10x-pm/skills/stakeholder-comms Skill

    1★ repo

    Draft the hard workplace messages product managers must send — saying no to a feature request, announcing a delay or de-scope, escalating a blocker, pushing back on an executive, or delivering unwelcome findings. Use when the user says "help me tell X that", "how do I say no to", "announce this delay", "escalate this", or "push back on".

  • Story splitter

    ramanbamba/10x-pm/skills/story-splitter Skill

    1★ repo

    Split an epic, feature, or PRD into user stories with acceptance criteria, sized for iterative delivery. Use when the user says "split this epic", "break this down into stories", "write user stories", "acceptance criteria for", or shares a spec that needs to become a sprint-ready backlog.

  • Ceo brief

    cerebrocybersolutions/libro/skills/ceo-brief Skill

    1★ repo

    CEO-level cross-department briefing for {{operator_name}} at {{company_name}}. Reads all department Brain sessions and decisions, synthesizes into a structured brief covering what moved, what's stuck, pending decisions, and upcoming deadlines. Use this skill whenever {{operator_name}} says: "brief me", "what's the state of the company", "morning brief", "company status", "what happened", "catch me up", "how are we doing", "daily brief", "what do I need to know", or at the end of any sessionend to close the loop. Also triggers on: "what's moving", "macro view", "give me a company update". This is the Chief of Staff brain — always run it when the operator needs a company-wide picture, even if they don't say "brief" explicitly. NOTE: backlog-lane intents (aging / pending / unresolved decisions) route to cross-dept-decisions, not here. See {brain_root}/AGENTS.md §Known DRY pairs.

  • Orchestrator mode

    cerebrocybersolutions/libro/skills/orchestrator-mode Skill

    1★ repo

    [LEGACY 2026-07-26 — retired upstream, shipped for reference only. Do NOT invoke against a live API key: the cloud path bills a real request against a beta unexercised since April 2026, on superseded model pins. The durable tier heuristic is preserved in the banner below.] Sequential chain routing — decomposes a compound task into subtasks, routes each subtask to its optimal tier (via advisor-mode underneath), runs a quality-gate check after each step, and escalates to a higher tier on gate failure. Complements council-mode (parallel comparison). Orchestrator is the "route around failure" thesis applied sequentially: keep each subtask on the cheapest tier that passes, escalate only when the gate fails. Trigger on: "orchestrator mode", "chain this", "break this into subtasks", "route each step", "escalation pipeline", "run this as a chain", "decompose and route", "quality- gated routing", "sequential tier routing", "run the orchestrator".

  • Plan before execution

    lubochka/xiigen-general-skills/agent-skills/plan-before-execution Skill

    1★ repo

    Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.

  • Plan before execution

    lubochka/xiigen-general-skills/claude/skills/plan-before-execution Skill

    1★ repo

    Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.

  • Plan before execution

    lubochka/xiigen-general-skills/codex/skills/plan-before-execution Skill

    1★ repo

    Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.

  • Plan before execution

    lubochka/xiigen-general-skills/skills/universal/plan-before-execution Skill

    1★ repo

    Open-source AI agent skills for safer Claude, Codex and Cursor coding workflows

  • Plan before execution

    lubochka/xiigen-general-skills/vscode-extension/resources/agent-skills/plan-before-execution Skill

    1★ repo

    Create a bounded plan before non-trivial work. Use for multi-file, high-risk, ambiguous, or delegated work.

  • Lesson plan builder

    SkillMedev/educators-toolkit/skills/lesson-plan-builder Skill

    1★ repo

    Builds a complete single-lesson plan - measurable objective, timed four-part arc (hook, direct instruction, guided practice, closure), a formative check with a proceed/re-teach rule, and differentiation notes - clear enough that a substitute could run it. Use when someone asks "write a lesson plan for...", "plan a 50-minute class on photosynthesis", "how should I structure tomorrow's lesson", or "turn this standard into a lesson". Do NOT use for sequencing a multi-week unit or full course - use curriculum-mapper instead; for deep per-learner adaptation of an existing lesson, use differentiated-instruction; for writing the quiz itself, use quiz-generator.

    The same file is in 2 other repositories

  • Doc writing

    jajupmochi/agent-harness/skills/doc-writing Skill

    1★ repo

    Use when writing or updating any document a human will read — a design or architecture spec, a feature manual and its in-app guide, an audit / bugfix / test report, a README, release notes, a plan, or a session handoff. Encodes the document requirements mined from two real project sessions (define every term in place, prove every claim and say how a tester re-proves it, full clickable links, mermaid diagrams, nothing stale, remaining tasks highlighted, no secrets) and ships `scripts/doccheck.py` to lint the finished file against the ones a machine can check.

  • Prompt library

    jajupmochi/agent-harness/skills/prompt-library Skill

    1★ repo

    Use to save and reuse good prompts across projects and agents, and to MINE past prompts out of local Claude Code / Codex / Copilot / opencode history. Many prompts recur (a detailed feature spec, a "design the whole thing" brief, a manual/onboarding prompt) and are worth reusing verbatim or as a reference. This curates them as browsable, greppable Markdown — each with the original, an optimized rewrite, and when to use / when NOT to use it — behind a PRIVACY GATE that refuses to store anything still containing paths/emails/tokens/usernames/codenames, so the library stays publishable.

  • Prd to ia

    royvergara/design-team-os/skills/prd-to-ia Skill

    1★ repo

    Use when turning a PRD or requirements document into a first pass information architecture. Triggers on a pasted or linked PRD plus a request for an IA, sitemap, screen list, or structure. Always returns what was excluded and why, not just the IA.

  • Prototype to spec

    royvergara/design-team-os/skills/prototype-to-spec Skill

    1★ repo

    Use when turning a chosen prototype into a buildable spec for engineering handoff. Triggers on a prototype link, file, or description plus a request for a spec or handoff. No validation signal, no spec — the only exception is an explicit owned bet (named owner, declared absence of evidence, reason, review date), which produces a spec with a Bet Record instead of a Validation Record.