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

  • Plan review code quality

    ChristopherAlphonse/calphonse-skills/plan-review-code-quality Skill

    1★ repo

    Reviews code organization, maintainability, local patterns, error handling, and diagram freshness.

  • Plan review intake

    ChristopherAlphonse/calphonse-skills/plan-review-intake Skill

    1★ repo

    Finds review inputs for plan review workflows using only local project files under .planning.

  • Plan review performance

    ChristopherAlphonse/calphonse-skills/plan-review-performance Skill

    1★ repo

    Reviews performance, scaling, caching, database access, and resource usage risks in a plan.

  • Plan review scope

    ChristopherAlphonse/calphonse-skills/plan-review-scope Skill

    1★ repo

    Challenges implementation scope before detailed engineering review.

  • Plan review tests

    ChristopherAlphonse/calphonse-skills/plan-review-tests Skill

    1★ repo

    Produces a test diagram, identifies coverage gaps, and writes a .planning QA handoff artifact.

  • Plan review wrapup

    ChristopherAlphonse/calphonse-skills/plan-review-wrapup Skill

    1★ repo

    Synthesizes plan review sections into a .planning review artifact and readiness summary.

  • Plan

    ChristopherAlphonse/calphonse-skills/plan Skill

    1★ repo

    Strategic planning and architecture assistant focused on thoughtful analysis before implementation. Helps developers understand codebases, clarify requirements, and develop scoped implementation strategies.

  • Prd mode

    ChristopherAlphonse/calphonse-skills/prd-mode Skill

    1★ repo

    Description of the custom chat mode.

  • Process task list

    ChristopherAlphonse/calphonse-skills/process-task-list Skill

    1★ repo

    Guidelines for managing task lists in markdown files to track progress on completing a PRD

  • Market research offers strategy

    taleshagn-horushub/thoth/skills/market-research-offers-strategy Skill

    1★ repo

    Realiza pesquisa aprofundada de mercado (Wide Research) de competidores e cria estratégia completa de ofertas escaláveis (Value Ladder). Use para: analisar concorrentes, identificar falhas no mercado, estruturar pacotes produtizados e criar estratégias de precificação.

  • Product brief

    philpalmieri/engineering-manager-skills/skills/technical/product-brief Skill

    1★ repo

    Generate a product-oriented summary of a project or initiative from GitHub data. Covers the problem, solution, complexity, user value, what's shipped, what's in progress, and what needs product attention. Use when ramping up a PM, presenting to leadership, or creating a shareable project overview.

  • To spec

    endalk200/skills/skills/to-spec Skill

    no license1★ repo

    Collection of agent skills I use in day to day work spanning engineering and none engineering work.

    The same file is in 1 other repository

  • To tickets

    endalk200/skills/skills/to-tickets Skill

    no license1★ repo

    Collection of agent skills I use in day to day work spanning engineering and none engineering work.

    The same file is in 1 other repository

  • Seo aeo content

    krkn-s/ai-workspace/skills/seo-aeo-content Skill

    1★ repo

    SEO and AEO content strategy workflow for creating search-ready and answer-engine-ready content. Use when the agent needs to produce or improve SEO/AEO briefs, page outlines, article structures, landing pages, content audits, editorial plans, keyword-to-question maps, publication checklists, brand SEO recommendations, AI Overview/AEO visibility plans, or content guidance for web publishing. Déclenche aussi sur les requêtes en français, par exemple brief SEO/AEO, plan ou calendrier éditorial, audit d'article ou de contenu, structure de page ou de landing page, optimisation de contenu, ou stratégie de contenu pour le référencement naturel et les moteurs de réponses.

  • Rollback strategy

    almasumdev/awesome-mobile-release-agent-skills/.github/skills/hotfix/rollback-strategy Skill

    no license1★ repo

    Halt rollouts, restore previous binaries, and use kill switches for server-side rollback. Use this when a production release is causing harm.

  • Adlc plan

    davidvictor/adlc-skills/skills/adlc/adlc-plan Skill

    1★ repo

    Create executable ADLC plans with task graphs, acceptance criteria, and commit checkpoints.

  • Adlc roadmap

    davidvictor/adlc-skills/skills/adlc/adlc-roadmap Skill

    1★ repo

    Create or maintain ADLC roadmap artifacts for milestones, sequencing, and long-range direction.

  • Write prd

    niftymonkey/skills/skills/write-prd Skill

    1★ repo

    Create a PRD through user interview, codebase exploration, and module design, saved as a local markdown file with optional GitHub issue submission. Works for new projects, features, or refactors. Use when user wants to write a PRD, create a product requirements document, plan a new feature, or spec out a new project.

  • To issues

    fbarrento/laravel-agent-kit/.agents/skills/to-issues Skill

    no license1★ repo

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

    The same file is in 12 other repositories

  • To prd

    fbarrento/laravel-agent-kit/.agents/skills/to-prd Skill

    no license1★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

    The same file is in 10 other repositories

  • Change spec

    fbarrento/laravel-agent-kit/archive/product-pipeline/change-spec Skill

    no license1★ repo

    Turns an approved PRD into a technical spec — the HOW of one change to a capability. Use after a change has been scoped and its PRD approved, to decompose it into building blocks and route each to its governing rule file. Refuses to run without an approved PRD. Cites rule-file paths; never restates rule content.

  • Product roadmap

    fbarrento/laravel-agent-kit/archive/product-pipeline/product-roadmap Skill

    no license1★ repo

    Produces product/roadmap.md — a deliberate sequence of intended value slices across capabilities, ordered by priority, dependency, and time-to-market. Use when establishing or revising the product's roadmap. Authored top-down from the strategy and capability map, never derived from existing changes. Advisory, not a gate. Refuses to run without an approved strategy and capability map.

  • Product strategy

    fbarrento/laravel-agent-kit/archive/product-pipeline/product-strategy Skill

    no license1★ repo

    Produces product/strategy.md — the WHAT between the vision's why and the roadmap's when. Use when defining or revising the product's strategy — target customers and personas, positioning, measurable goals, monetization, and time-to-market urgency. Authored from human intent, reconciled against the vision. Refuses to run without an approved vision.

  • Spec breakdown

    fbarrento/laravel-agent-kit/archive/product-pipeline/spec-breakdown Skill

    no license1★ repo

    Turns an approved spec into ordered, independently mergeable implementation issues, and drafts the capability README update that keeps the repo the source of truth. Use after a change has been specced and its spec approved. Refuses to run without an approved spec. The last skill in the product pipeline.

  • Plan eng review

    coreline-ai/codex-devflow-plugin/skills/plan-eng-review Skill

    1★ repo

    Engineering-manager style implementation plan review. Use when asked to review architecture, lock in an execution plan, assess data flow, edge cases, test coverage, performance, rollout risk, or perform an engineering review before coding.

  • Spec acceptance harness

    andrey-learning-machines/swe-harness/plugins/swe-harness/skills/spec-acceptance-harness Skill

    1★ repo

    Turn Specification Kit (Spec Kit) feature specifications or product requirements into executable feature acceptance coverage using Gherkin feature files, Playwright browser tests, and a story matrix that maps stories to required backend or service routes. Use when a project needs durable behavior traceability from specification to implementation proof.

  • Unicorn estimation

    andrey-learning-machines/swe-harness/plugins/swe-harness/skills/unicorn-estimation Skill

    1★ repo

    Guides the user through risk-based task estimation using decomposition, three-point estimates, and PERT formula. ALWAYS trigger on "estimate", "how long will this take", "time to complete", "sizing", "scope this", "effort estimate", "how many hours", "story points", "project timeline", "when will this be done", "cost estimate", "level of effort". Use when sizing any work item, feature, or project.

  • Unicorn technical debt

    andrey-learning-machines/swe-harness/plugins/swe-harness/skills/unicorn-technical-debt Skill

    1★ repo

    Guides deliberate management of technical debt: recognition, tracking, prioritization, and paydown. ALWAYS trigger on "technical debt", "code shortcut", "pay down debt", "debt tracking", "just for now", "temporary hack", "hardcoded value", "copy-paste code", "missing tests", "TODO cleanup", "refactor plan", "debt priority", "interest cost", "boy scout rule", "code quality backlog". Use when taking a shortcut, discovering suboptimal code, planning debt paydown, or quantifying ongoing cost of compromises.

  • Implement prd

    ca-lee-b/personal-skills/skills/implement-prd Skill

    1★ repo

    Reads a PRD file and implements it — first producing an execution plan, then writing code. Trigger on "implement the PRD", "build this PRD", "code this up", or any instruction to act on a PRD file. If no file is specified, ask the user before proceeding.

  • Manual sdd

    Soham407/studio-kickstart/architecture/manual-sdd Skill

    1★ repo

    Use when planning or delivering work with a spec-driven development process, including requirements, implementation plans, verification, and review.

  • To issues

    Soham407/studio-kickstart/architecture/to-issues Skill

    1★ repo

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

    The same file is in 12 other repositories

  • To prd

    Soham407/studio-kickstart/architecture/to-prd Skill

    1★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

    The same file is in 10 other repositories

  • Feature spec delivery pipeline

    mo-hawary/hawary-workflow-skills/skills/feature-spec-delivery-pipeline Skill

    1★ repo

    Turn a feature request or bug cluster into a source-backed spec, impact map, acceptance criteria, and delivery plan before coding.

  • Qa bug hunt planner

    mo-hawary/hawary-workflow-skills/skills/qa-bug-hunt-planner Skill

    1★ repo

    Run source-backed QA discovery, recommend audit tracks, build fix-ready bug-hunt plans, and define verification gates.

  • Plan sovereign ai

    hiteshbandhu/skills-i-use/skills/ai-engineer-talks/plan-sovereign-ai Skill

    1★ repo

    Runs checklists for sovereign AI planning — four control pillars, retrofit failure modes, guardrailed agent architecture, and sovereignty acceptance tests. Use when the user must meet GDPR, EU residency, on-prem, air-gap, model swap, or says "sovereign AI", "data sovereignty", "Cloud Act", "Haystack on-prem".

  • Spec grounded design

    hiteshbandhu/skills-i-use/skills/spec-grounded-design Skill

    1★ repo

    Before implementing against any protocol, SDK, or external API, ground the design in reality — pull the actual spec, probe the live endpoint to capture how it really behaves, reconcile spec-vs-reality (reality wins), and extract a design contract of verified facts, edge cases, and invariants to build against. Encodes "read the protocol" + "test live before assuming the spec is correct," because reverse-engineered or stale docs lag the real API. Triggers on "integrate with X", "design against this API", "read the protocol first", "before we build this integration", "is the spec right", "how does this API actually behave", "ground this in the docs", "verify before coding". Use before writing integration code against an external system, not for internal logic.

  • Offline first strategy

    almasumdev/awesome-mobile-agent-skills/.github/skills/offline/offline-first-strategy Skill

    no license1★ repo

    Designing a mobile app as offline-first - caching tiers, authoritative sources, read and write paths, and the boundaries between device and server. Use when a feature needs to work without connectivity or when diagnosing stale/inconsistent data.

  • Crash reporting strategy

    almasumdev/awesome-mobile-agent-skills/.github/skills/operations/crash-reporting-strategy Skill

    no license1★ repo

    Crash reporting for mobile - symbolication, SLOs, tagging, triage workflow, and comparing Crashlytics, Sentry, Bugsnag, Firebase, and native (APM) reporters. Use when setting up or improving crash reporting.

  • Mobile project planning

    almasumdev/awesome-mobile-agent-skills/.github/skills/planning/mobile-project-planning Skill

    no license1★ repo

    Expert guidance on scoping a mobile application, cutting an MVP, prioritizing platforms, and sequencing milestones. Use this when a project is starting or a major feature set is being defined.

  • Mobile testing strategy

    almasumdev/awesome-mobile-agent-skills/.github/skills/quality/mobile-testing-strategy Skill

    no license1★ repo

    Mobile testing strategy - pyramid, device selection, flake reduction, device clouds, and test-category scope. Use when setting up or auditing the testing approach of a mobile project.

  • Speckit analyze

    merllinsbeard/merlin-skills/skills/speckit-analyze Skill

    1★ repo

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

  • Speckit plan

    merllinsbeard/merlin-skills/skills/speckit-plan Skill

    1★ repo

    Execute the implementation planning workflow using the plan template to generate design artifacts.

  • To prd

    merllinsbeard/merlin-skills/skills/to-prd Skill

    1★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

    The same file is in 10 other repositories

  • Customer escalation recovery

    stephenrogan/leadership-skills/skills/customer-escalation-recovery Skill

    1★ repo

    Builds an executive customer escalation recovery brief with timeline, commitments, stakeholders, risk exposure, root-cause hypotheses, response plan, and approval-required concessions. Use for major customer escalations, renewal threats, executive complaints, or service failures.

  • Delegation brief

    stephenrogan/leadership-skills/skills/delegation-brief Skill

    1★ repo

    Converts fuzzy delegation into a crisp ownership brief with outcome, context, constraints, decision rights, checkpoints, risks, and success criteria. Use when handing work to a direct report, project owner, team lead, or cross-functional partner.

  • Executive update brief

    stephenrogan/leadership-skills/skills/executive-update-brief Skill

    1★ repo

    Creates an executive-ready update brief with headline narrative, evidence, risks, decisions needed, owner asks, and anticipated questions. Use for exec staff updates, QBRs, board prep, steering meetings, or when leaders need concise upward communication.

  • Stakeholder prewire

    stephenrogan/leadership-skills/skills/stakeholder-prewire Skill

    1★ repo

    Builds a stakeholder prewire plan with influence map, likely objections, conversation sequence, audience-specific framing, decision asks, and alignment tracker. Use before cross-functional proposals, executive decisions, process changes, or politically sensitive initiatives.

  • Strategy operating system

    stephenrogan/leadership-skills/skills/strategy-operating-system Skill

    1★ repo

    Turns strategy into an operating system with priorities, bets, decision calendar, metrics, operating cadence, owner map, risks, and kill criteria. Use for quarterly planning, annual planning, strategic resets, or converting executive direction into management rhythm.

  • Weekly leadership pack

    stephenrogan/leadership-skills/skills/weekly-leadership-pack Skill

    1★ repo

    Synthesizes the weekly leadership picture across metrics, risks, people, customers, priorities, and decisions into a one-page operating brief. Use before weekly business reviews, leadership team meetings, Monday planning, or Friday retrospectives.

  • Planning and task breakdown

    Xrenya/safe-agent-skills/skills/planning-and-task-breakdown Skill

    1★ repo

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

    The same file is in 9 other repositories

  • Spec driven development

    Xrenya/safe-agent-skills/skills/spec-driven-development Skill

    1★ repo

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

  • Handoff brief

    zaixincheng174-ai/codex-agent-governance-skills/core/skills/handoff-brief Skill

    1★ repo

    Create a concise, redacted handoff brief for continuing work in a future session or another agent. Adapted from handoff; writes to temp or .scratch by default and preserves evidence and verdict boundaries.

  • Persistent planning

    zaixincheng174-ai/codex-agent-governance-skills/core/skills/persistent-planning Skill

    1★ repo

    Advisory persistent planning for complex, multi-step Codex work. Use only when a task needs durable working notes across phases or sessions; subordinate to AGENTS.md, project-lifecycle, repo-preflight, diff-scope-guardian, debug-repro-loop, closeout-review, and explicit user instructions.

  • Spec it

    NjoyimPeguy/augments/plugins/augments/skills/spec-it Skill

    1★ repo

    Use when you have a goal or feature and need detailed requirements before design — what it must do, how each is verified, and the assumptions and risks. Captures the WHAT, not the HOW; grill unknowns with interview-me first. Skip when verifiable requirements are already written down.

  • Writing plans

    NjoyimPeguy/augments/plugins/augments/skills/writing-plans Skill

    1★ repo

    Use when approved requirements or a clearly multi-step task need an executable per-task plan before implementation. High-risk target-work planning requires current approved migration and assurance contracts. A plan limited to explicitly authorized gate-enabling prerequisites may consume the exact proposed owning gate contract, but cannot include target work. Skip single-step or trivial work.

  • Spec it

    NjoyimPeguy/augments/skills/analysis/spec-it Skill

    1★ repo

    Use when you have a goal or feature and need detailed requirements before design — what it must do, how each is verified, and the assumptions and risks. Captures the WHAT, not the HOW; grill unknowns with interview-me first. Skip when verifiable requirements are already written down.

  • Writing plans

    NjoyimPeguy/augments/skills/design/writing-plans Skill

    1★ repo

    Use when approved requirements or a clearly multi-step task need an executable per-task plan before implementation. High-risk target-work planning requires current approved migration and assurance contracts. A plan limited to explicitly authorized gate-enabling prerequisites may consume the exact proposed owning gate contract, but cannot include target work. Skip single-step or trivial work.

  • Product plan

    RubenGlez/harness/skills/product-plan Skill

    1★ repo

    Define the full product vision — audience, positioning, features, roadmap, and UX direction — through a structured interview. Use after ideate, or directly when the idea is already validated and you're ready to spec the product.

  • Design architecture en

    roebi/sw-dev-agent-framework/skills/design-architecture-en Skill

    no license1★ repo

    Produces an architecture design for a software project from a structured requirements list. Outputs architecture.md covering module structure, data flow, technology choices, and testability constraints. Use when requirements are complete and the next step is planning the structure before writing any code. Activate for trigger phrases like: "design the architecture", "architecture phase", "plan the module structure", "create an architecture doc", "design this system", or "how should we structure this project".

  • Query decomposition

    idanmann10/vivarium-world/domains/research/skills/query-decomposition Skill

    no license1★ repo

    Split broad research into independently answerable questions.