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

  • Review panel

    grimaldost/craft-collection/plugins/session-workflow/skills/review-panel Skill

    2★ repo

    Use when the user has iterated on a design, plan, spec, architecture, code, or prose over several rounds and can no longer judge it cleanly, before a high-stakes or hard-to-reverse decision, or when they ask for "fresh eyes", "a second opinion", "red team this", "poke holes in this", "sanity-check this independently", "am I anchored" / "too close to this", "critique this from different angles", or run "/review-panel". Prefer this over reviewing the artifact yourself — its value is convening fresh reviewer subagents that are blind to this conversation and to each other, which a review you run while anchored on the same context cannot replicate. Requires spawning fresh-context reviewers (subagents where the harness has them; sequential clean contexts otherwise); always show the plan and rough cost and ask before firing. Not for a quick factual check, a single obvious answer, or a first-pass review of something just created.

  • Toolkit awareness

    grimaldost/craft-collection/plugins/session-workflow/skills/toolkit-awareness Skill

    2★ repo

    Know what skills, agents, commands, and hooks are installed in the current Claude Code environment, and reference them well in prompts and specs. Use when answering "what tools/agents/commands/hooks do I have" (including narrower inventory questions like which hooks are configured), determining which installed skill owns or is responsible for a given concern — a scoring rubric, a schema, project conventions — so you point at the owner instead of duplicating it, planning work that will run in Claude Code, or writing a task spec or definition-of-done that should reference slash commands or quality gates. Produces a live inventory via a scan script rather than relying on a hand-maintained list.

  • Loop ops

    VioletScar-Hui/Build_Great_Loop/loop-ops Skill

    2★ repo

    Operate an existing or intent-settled long-running, recurring, or unattended agent loop SAFELY — the scheduling, cost, safety, and rollout layer around a loop. Use this WHENEVER the user wants to RUN/SCHEDULE/OPERATE an agent loop over time rather than author its prompt: "run this agent every day / on every PR / nightly / on a cron", "set up an autonomous agent that keeps running", "babysit my PRs", "auto-triage issues", "sweep CI failures", "draft release notes automatically", "how do I run my loop unattended without it doing damage", or any question about an agent loop's cadence, autonomy level, token/cost budget, safety gates, denylist, human escalation, multi-loop coordination, kill switch, or operational readiness. If the per-run goal, success, safety, or budget is unsettled, loop-spec owns the request first. For a compound build-and-schedule request, loop-ops is lead and calls loop-engineering once for the per-run prompt. Produces an operating plan (pattern + cadence + autonomy level + budget + safety gates + schedule command + STATE/run-log scaffolding). Pairs with loop-engineering, which authors the per-run prompt this operates.

  • Loop retro

    VioletScar-Hui/Build_Great_Loop/loop-retro Skill

    2★ repo

    Post-run retrospective for an agent loop — close the improvement flywheel. Reads the ACTUAL run artifacts (structured event log / progress view / state files / PLAN history / loop-docs) and produces: an evidence-cited diagnosis, concrete harness revision proposals, gotcha eval cases from real failures, and SPEC/STANDARDS revision proposals for human ratification. Trigger AFTER a loop has run: "loop 跑完了帮我复盘", "看看运行记录哪里出问题", "这个循环为什么 thrash / 超预算了", "分析一下 run log", "post-mortem my loop", "did my loop actually do a good job". Not for auditing a loop prompt BEFORE it runs (loop-review), operating/scheduling a loop (loop-ops), or building one (loop-spec / loop-engineering).

  • Loop spec

    VioletScar-Hui/Build_Great_Loop/loop-spec Skill

    2★ repo

    Clarify and scope a NEW agent loop before its harness is authored. Use when the user wants to create an autonomous/repeating agent, asks to turn a vague idea into a loop, or has not yet settled success criteria, boundaries, risk, or budget. First test whether a loop is justified; route one-shot or deterministic tasks to a simpler workflow. Use proportionate intake: confirm only load-bearing decisions, offer visible reversible defaults for minor details, and write durable SPEC/STANDARDS/GOALS artifacts only when the loop's scale or lifespan benefits from them. Hands settled intent to loop-engineering. Not for reviewing an existing harness (loop-review), measuring it (loop-eval), running it on a schedule (loop-ops), or post-run analysis (loop-retro).

  • Documentation maintenance

    affectionatec/agentic-engineering/skills/documentation-maintenance Skill

    2★ repo

    Use when something said or decided in conversation makes a chain document (PRD, SPEC, ADR, IMPL PLAN, AGENTS.md) stale, contradicted, or incomplete, or when the user proposes a new feature or scope change mid-project. Triggers on "I want to add a feature", "let's also support X", "change the architecture", "switch from X to Y", "we decided to...", "the spec is out of date", "keep the docs in sync", "the code now does X but the doc says Y", or noticing any decision in the conversation that the docs don't yet reflect. The agent flags drift proactively and MUST get the user's permission before editing any fundamental document.

  • Implementation plan

    affectionatec/agentic-engineering/skills/implementation-plan Skill

    2★ repo

    Use when specs are approved and work needs to be broken into independently executable tasks, when sequencing dependencies across modules, when sizing milestones, or when a project is about to start coding but lacks a milestone breakdown. Triggers on "let's plan the implementation", "break this into tasks", "sprint plan", "what should we build first", "milestones", "task ordering", "estimate the work", or transitioning from spec to code.

  • Project kickoff prd

    affectionatec/agentic-engineering/skills/project-kickoff-prd Skill

    2★ repo

    Use when starting a new project or feature from scratch, when a rough idea needs to be turned into a structured product spec, or when scope, target users, or success metrics are undefined. Triggers on "let's build X", "new project", "kick off", "write a PRD", "product brief", "what should we build", vague feature requests, or when no PRD exists yet for the work about to start.

  • Technical specification

    affectionatec/agentic-engineering/skills/technical-specification Skill

    2★ repo

    Use when the PRD is finalized and precise implementation contracts are needed, when defining API shapes, data models, state machines, error taxonomies, or acceptance criteria, or when ambiguous "handle this gracefully" requirements need to be hardened into testable specs. Triggers on "write the spec", "define the API", "what's the data model", "state diagram", "error contract", "acceptance criteria", or transitioning from PRD to implementation.

  • Spec first

    Alex7develop/my-agent-skills/skills/spec-first Skill

    2★ repo

    Написать короткую спецификацию (цель, границы, критерии готовности) перед тем как писать код для новой фичи, значимого изменения или нового проекта. Используй этот навык, когда пользователь просит реализовать фичу, начать новый проект, добавить функциональность, или когда задача сформулирована широко и её легко понять по-разному ("сделай авторизацию", "добавь экспорт в PDF", "перепиши модуль X"). Не используй для тривиальных однострочных правок или явно узких багфиксов.

  • Codebase plan refactor

    risadams/ink-and-agency/skills/codebase-build/codebase-plan-refactor Skill

    no license2★ repo

    Create a detailed refactor plan with tiny commits via user interview, then file it as an issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

  • Plan to spec

    risadams/ink-and-agency/skills/meta-orchestration/plan-to-spec Skill

    no license2★ repo

    Synthesize the current conversation into a spec (PRD) and stage it as a local file. Use when a design discussion, grilling session, or work-plan is settled and you want it written up as a spec — no interview, just synthesis. Publishing to Confluence is opt-in, only on request.

  • Plan to tickets

    risadams/ink-and-agency/skills/meta-orchestration/plan-to-tickets Skill

    no license2★ repo

    Break a spec, plan, or the current conversation into a local, numbered, spec-kit-style task list of tracer-bullet vertical slices with explicit dependencies. Use when a spec or plan is ready to become actionable tasks. Pushing to Jira is opt-in, only on request.

  • Work plan

    risadams/ink-and-agency/skills/meta-orchestration/work-plan Skill

    no license2★ repo

    Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

  • Sprint plan

    risadams/ink-and-agency/skills/scrum-sprint/sprint-plan Skill

    no license2★ repo

    Convert the start-of-sprint canvas into a planning markdown report. Use when the user says "sprint plan", "sprint planning report", "convert sprint plan to markdown", or invokes /sprint-plan. Produces a sprint-goal summary, committed scope (carry-over vs new commit), capacity vs commitment with WIP-saturation risk, observations, and risks; auto-runs a clarity-council pass and writes a date-stamped report with a `-latest` pointer.

  • Reverse brief

    batteryshark/skill-tap/skills/productivity/reverse-brief Skill

    2★ repo

    Reconstruct a concise implementation brief from an existing codebase or artifact when original requirements are missing, stale, or incomplete.

  • Gtm brief

    Abhillashjadhav/PM-agent-OS/.claude/skills/gtm-brief Skill

    no license2★ repo

    Launch-stage skill: turns a feature plus its evidence into a GTM one-pager where every audience claim is tied to a stated source or labeled assumption. Use when a launch needs its go-to-market summarized on one page — 'draft the GTM one-pager', 'GTM brief for the launch', 'who are we selling this to and how', 'GTM summary for sales kickoff' — or when /pm routes such a request here. Do NOT use for full GTM strategy authoring, launch checklists (launch-checklist), announcements (announcement-drafter), or GTM definitions.

  • North star designer

    Abhillashjadhav/PM-agent-OS/.claude/skills/north-star-designer Skill

    no license2★ repo

    Strategy-stage skill: designs a north star metric and its input-metric tree for a product — the NSM must be leading, not lagging, and the output states the causality check it passed. Use when the user wants to choose or fix their top metric — 'design a north star metric', 'what should our NSM be', 'is MRR a good north star', 'build the metric tree' — or when /pm routes such a request here. Do NOT use for definitions of metric concepts, for analytics instrumentation setup, for diagnosing why a metric moved (research-brief), or for setting OKR targets on existing metrics.

  • Prd first

    Abhillashjadhav/PM-agent-OS/.claude/skills/prd-first Skill

    no license2★ repo

    Forces a written PRD before any code generation. Use this skill when the user says "build", "create app", "make me a", "vibe code", "let's build", "I want an app that", "spin up a", "prototype a", "ship a", or any phrasing that signals they want code generated from a high-level idea. Also use when the user references an existing project but the conversation has no PRD context (no /prds/ file referenced, no clear success metric). The skill blocks code generation until a 5-field PRD exists as a markdown file in the repo. Do NOT use when the user is asking factual questions, debugging existing code, editing a specific file they've named, or working in a repo where a PRD for this feature already exists at /prds/. Skip when user explicitly says "skip the PRD" or "just code it" — but flag the risk once before proceeding.

  • Prd to eval

    Abhillashjadhav/PM-agent-OS/.claude/skills/prd-to-eval Skill

    no license2★ repo

    Build-stage skill: turns a PRD or feature spec into a verification layer — binary quality gates for disqualifiers plus an anchored 1-5 rubric for tradeable qualities, with the two never mixed. Use when the user needs to define and test 'good' for a feature — 'turn this PRD into an eval', 'define good for our AI summarizer', 'build quality gates and a judge rubric', 'how do we test whether this works' — or when /pm routes a spec-bearing eval-design request here. Do NOT use to generate artifacts against frozen criteria (builder-validator), to execute an eval over outputs, for gate-vs-rubric knowledge questions, or for build/kill decisions (ai-feature-go-no-go).

  • Pricing tradeoff

    Abhillashjadhav/PM-agent-OS/.claude/skills/pricing-tradeoff Skill

    no license2★ repo

    Strategy-stage skill: turns a pricing question into structured options — every option carries a stated margin mechanism, never a naked price point. Use when the user is weighing pricing structures — 'per seat or usage-based', 'freemium vs free trial', 'structure the pricing options', 'bundle or unbundle the add-on', 'how should we price X' — or when /pm routes such a request here. Do NOT use to conjure a single price with no cost/margin context, to size markets (opportunity-sizer), to audit a roadmap's economics (roadmap-reality-check), or for definitions of pricing terms.

  • Research brief

    Abhillashjadhav/PM-agent-OS/.claude/skills/research-brief Skill

    no license2★ repo

    Discovery-stage skill: turns an open product question into a structured research plan where every method is mapped to the decision it informs. Use when the user needs to plan research before acting — 'write a research plan for X', 'how should we figure out why Y happened', 'what research do we need before betting on Z', 'draft the research brief' — or when /pm routes such a request here. Do NOT use to synthesize research already run (interview-synthesizer / feedback-pattern-miner), to execute surveys or studies, for qual-vs-quant knowledge questions, or for web/market deep-research tasks.

  • Roadmap reality check

    Abhillashjadhav/PM-agent-OS/.claude/skills/roadmap-reality-check Skill

    no license2★ repo

    Strategy-stage skill: audits a roadmap against unit economics — every item tagged supported or unsupported with the economic mechanism stated. Use when the user provides a roadmap plus business numbers and asks what's economically justified — 'reality-check this roadmap', 'which items pay for themselves', 'what survives contact with the P&L', 'does this lineup make economic sense' — or when /pm routes such a request here. Do NOT use to author a roadmap, to prioritize purely by customer impact without economics, to size markets (opportunity-sizer's job), or for definitions of unit-economics terms.

  • Stakeholder update

    Abhillashjadhav/PM-agent-OS/.claude/skills/stakeholder-update Skill

    no license2★ repo

    Launch-stage skill: turns raw project state into audience-calibrated status updates whose numbers reconcile exactly to the input — emphasis varies by audience, facts never do. Use when project state needs communicating — 'write the launch status update for the exec team', 'weekly stakeholder update from these notes', 'update sales on where the launch stands' — or when /pm routes such a request here. Do NOT use for public launch announcements (announcement-drafter), for logging decisions to memory (pm-context-system), for one-off meeting summaries, or for cadence-process questions.

  • Strategy review

    Abhillashjadhav/PM-agent-OS/.claude/skills/strategy-review Skill

    no license2★ repo

    Strategy-stage skill: pressure-tests a strategy document — every weakness it raises must cite the specific line it attacks. Use when the user provides their own strategy doc, positioning memo, or plan and asks for it to be stress-tested — 'pressure-test this strategy', 'tear it apart before the board does', 'red-team this memo', 'what's weak in this one-pager' — or when /pm routes such a request here. Do NOT use to author a strategy from scratch (there must be a doc to attack), to review PRs (/pr-review), to analyze a competitor's strategy (competitor-teardown), or for knowledge questions about strategy frameworks.

  • Eval rubric generator

    Abhillashjadhav/PM-agent-OS/eval-rubric-generator Skill

    no license2★ repo

    Use this skill when a product spec, feature requirement, PRD, or user story needs to be converted into a concrete evaluation rubric. Triggers on phrases like "write an eval for this", "create a rubric", "how do I test this AI feature", "define good output", "what should I measure", or when a user pastes a spec and asks what success looks like. Produces a binary pass/fail checklist — not vague metrics, not suggestions — a rubric you can run against model outputs today. This is the skill AI PMs need before anything ships to production. Do NOT use to execute an evaluation or invent requirements absent from the supplied specification.

  • Diagram gen spec

    jamestexas/agents/skills/diagram-gen-spec Skill

    2★ repo

    Curated library of Claude Code subagents and skills (23 agents, 20 skills) with an idempotent installer that symlinks into ~/.claude. Frontmatter-driven; spec-compliant with Anthropic and Gemini schemas.

  • Product

    tikhomirovv/agents-knowledge/skills/product Skill

    no license2★ repo

    Acts as a product manager for founders and small teams. Use when the user needs to choose a niche/idea, define ICP and problem, validate demand, design an MVP, write a PRD, plan a roadmap, set value-based pricing assumptions, or filter ideas with a lightweight GTM manifesto before building. Applies whenever the user mentions product management, MVP, PRD, roadmap, PMF, niche selection, or product strategy.

  • Pricing strategy targets

    factory-x-contributions/business-models/.agents/skills/pricing-strategy-targets Skill

    2★ repo

    Defines the pricing strategy, price positioning, architecture, discount rules, KPI guardrails, and go-to-market test plan. Includes a closing checklist to verify all viability elements are complete and consistent.

  • Stakeholder matrix

    factory-x-contributions/business-models/.agents/skills/stakeholder-matrix Skill

    2★ repo

    Identifies and maps all relevant stakeholders per prioritized market segment into a 2x2 influence-involvement matrix. Defines engagement strategies per quadrant and prioritizes key stakeholders.

  • Ontology planning team

    Mokee04/ontology_research/ontology-planning-team Skill

    no license2★ repo

    Plan a domain ontology effort by clarifying scope, composing the working team, defining competency questions, and setting risk and approval gates before research begins.

  • Ontology technical plan writer

    Mokee04/ontology_research/ontology-technical-plan-writer Skill

    no license2★ repo

    Draft or refine a technical planning document template for an ontology project. Use when the user wants a technical proposal, planning brief, or reusable template that connects scope, competency questions, standards reuse, modeling approach, validation, governance, and execution phases without drifting into a business-only pitch.

  • Business product leadership

    kinhluan/skills/.agent-skills/business-product-leadership Skill

    2★ repo

    Strategic frameworks for Product/Business Owners. Use this skill for Product Market Research, defining Jobs-To-Be-Done (JTBD), understanding Diffusion of Innovations, planning MVPs, separating deployment (Ship) from business launch (Release), product metrics, A/B testing, pricing, and go-to-market strategy.

  • Milestone tracker

    kinhluan/skills/.agent-skills/milestone-tracker Skill

    2★ repo

    Track PhD/Master's milestones, deadlines, committee meetings, and research timeline. Use when planning PhD schedule, checking progress, preparing for committee meetings, managing submission deadlines, or when behind on timeline.

  • Phd proposal

    kinhluan/skills/.agent-skills/phd-proposal Skill

    2★ repo

    Write, structure, or review a PhD/Master's research proposal. Use when drafting a research proposal, preparing for committee review, writing a thesis outline, or aligning methodology with academic requirements.

  • Proposal defense

    kinhluan/skills/.agent-skills/proposal-defense Skill

    2★ repo

    Prepare for PhD/Master's proposal defense — slide structure, committee Q&A simulation, proposal presentation, and defense logistics. Use when preparing to defend your research proposal before the committee.

  • Publication strategy

    kinhluan/skills/.agent-skills/publication-strategy Skill

    2★ repo

    Choose publication venue, prepare submission, write rebuttals, and manage revision cycles. Use when deciding where to submit a paper, preparing camera-ready, writing a rebuttal to reviewers, or planning a revision.

  • Why strategic rationale

    kinhluan/skills/.agent-skills/why-strategic-rationale Skill

    2★ repo

    Establish the strategic rationale for a product or feature before building. Use this skill when evaluating a new product idea, justifying an initiative to stakeholders, validating whether a feature is worth building, or preparing a pitch document. Combines Value Proposition Canvas (structured analysis) with Amazon's Working Backwards PR/FAQ (narrative synthesis) in a 2-phase workflow.

  • Problem clarifier

    Recusive/Skills/problem-clarifier Skill

    2★ repo

    Clarify problems, bugs, and feature requests through a reflect-back interview before planning. Use this skill whenever the user describes an issue, bug, broken behavior, or a feature they want — BEFORE entering plan mode. Triggers on phrases like "this isn't working", "I'm seeing a bug", "something is wrong with", "I want to change how X works", "X is broken", "the problem is", "I'm having an issue with", "can you fix", or any description of unexpected behavior.

  • Testing strategy

    troyjthomas/ios-agent-skills/skills/testing-strategy Skill

    2★ repo

    Comprehensive testing approach for iOS apps built with Claude Code. Covers what Claude Code can test automatically (unit tests, build verification), what requires manual testing (interactive behavior, visual feel), and how to set up CI/CD with GitHub Actions. Use this skill during and after the build phase, and especially before shipping. Becomes critical for post-v1 updates where regressions hide.

  • Ou features audit

    secondorderai/ouroboros/.agents/skills/ou-features-audit Skill

    2★ repo

    Audit implemented Ouroboros features against requirements, PRDs, tickets, GitHub issues, or acceptance criteria to find missing, partial, incorrect, or unverifiable work. Use when the user asks to audit a feature, verify implementation completeness, compare code to requirements, check acceptance criteria, run a gap analysis, determine what is left to build, check whether a ticket is done, audit against a PRD/spec, or asks whether recent work in the Ouroboros codebase matches its requirements. Do NOT use for creating PRDs, generating tickets, implementing tickets, broad full-codebase review, or general bug triage.

  • Ouroboros test plan author

    secondorderai/ouroboros/.agents/skills/ouroboros-test-plan-author Skill

    2★ repo

    Create intent-based Ouroboros desktop E2E Markdown test plans from a high-level goal, feature, module, bug, PRD, ticket, or UI area. Use when asked to generate, draft, author, improve, or expand files under test-plan/ for Agent Browser desktop testing.

  • Prd to tickets

    secondorderai/ouroboros/.agents/skills/prd-to-tickets Skill

    2★ repo

    Use this skill whenever the user wants to generate implementation tickets from an existing PRD, break a PRD into engineering tickets, create ticket files from a product spec, or turn a requirements document into actionable work items. Triggers include: 'create tickets from PRD', 'break this into tickets', 'generate tickets', 'write tickets for this PRD', 'turn this PRD into tickets', 'make implementation tickets', 'ticket this up', or any request to take an existing PRD or product spec and produce individual implementation tickets. The PRD can be a local file (markdown). Also use when the user has just finished writing a PRD and wants to generate tickets from it. Use this skill even if the user just says 'create the tickets' or 'ticket this' when a PRD file is referenced. Do NOT use for writing PRDs from scratch.

  • Meta thinking

    secondorderai/ouroboros/.claude/skills/meta-thinking Skill

    2★ repo

    Use this skill when the user needs structured planning, complex analysis, difficult tradeoff decisions, or troubleshooting under uncertainty and the agent should apply a compact meta-thinking loop with task classification, a meta-mode gate, plan extraction, critique, and concise trust signals. Prefer it when surfacing confidence, limitations, and context gaps will materially improve the answer. Do not use it for simple factual or one-step requests where extra framing would add friction without improving the result.

  • Meta thinking

    secondorderai/ouroboros/packages/desktop/resources/skills/builtin/meta-thinking Skill

    2★ repo

    Use this skill when the user needs structured planning, complex analysis, difficult tradeoff decisions, or troubleshooting under uncertainty and the agent should apply a compact meta-thinking loop with task classification, a meta-mode gate, plan extraction, critique, and concise trust signals. Prefer it when surfacing confidence, limitations, and context gaps will materially improve the answer. Do not use it for simple factual or one-step requests where extra framing would add friction without improving the result.

  • Change validation planner

    ckorhonen/swe-skills/skills/change-validation-planner Skill

    2★ repo

    Plans the narrowest trustworthy validation path for a scoped code change or diff. Use when a user asks what to run before merging, how to validate a specific change, whether the current checks are enough, or wants a bounded command order from narrow to broad. Do NOT use for writing tests, fixing the code change itself, broad QA sweeps, or generic debugging that needs root cause analysis.

  • Nova implement plan

    lliangcol/llm-plugins-fusion/nova-plugin/skills/nova-implement-plan Skill

    2★ repo

    Implement the resolved execution profile. The default approved-plan profile requires PLAN_INPUT_PATH and PLAN_APPROVED=true.

  • Nova produce plan

    lliangcol/llm-plugins-fusion/nova-plugin/skills/nova-produce-plan Skill

    2★ repo

    Write a formal plan document to file using general or java-backend profile; design checkpoint only.

  • Sharpen intent

    harshitsinghbhandari/domain-expansion/skills/sharpen-intent Skill

    no license2★ repo

    Use ONLY when the user explicitly asks to sharpen, pressure-test, interrogate, or stress-test an idea, decision, or plan they are holding. Triggers on "sharpen this", "interrogate my idea", "pressure-test this decision", "grill me on X", "help me get this crisp before I act". Grills the human 2-3 questions at a time until their intent is stated cleanly enough that a stranger could act on it with zero ambiguity, then writes a sharpened-intent artifact. Manual-only: do NOT self-activate on "I want to build X" (that is spec-and-ship). Skip when intent is already clear, or the idea is small enough to just do.

  • Spec and ship

    harshitsinghbhandari/domain-expansion/skills/spec-and-ship Skill

    no license2★ repo

    Use when building, adding, or significantly changing any non-trivial feature, system, refactor, integration, or migration that will be built out through Agent Orchestrator (AO) workers. Also triggers on "interview me", "ask me questions first", "help me spec this out", "I want to build X", "let's plan Y before we code", or handing over a spec doc / PRD / design brief to start work. Skip for bug fixes, one-liners, and cosmetic tweaks.

  • Component design spec

    The-AI-Directory-Company/agents-and-skills/skills/component-design-spec Skill

    2★ repo

    Write component design specifications — defining props, states, interactions, accessibility requirements, and visual variants for design system components.

  • Data migration plan

    The-AI-Directory-Company/agents-and-skills/skills/data-migration-plan Skill

    2★ repo

    Plan and execute data migrations with phased rollout — dual-write, backfill, cutover, and verification stages with rollback triggers and data integrity checks at every step.

  • Database migration plan

    The-AI-Directory-Company/agents-and-skills/skills/database-migration-plan Skill

    2★ repo

    Plan database schema migrations (DDL changes) with backward-compatible strategies, migration scripts, rollback procedures, and zero-downtime deployment patterns. Covers column additions, type changes, index management, and table restructuring.

  • Disaster recovery plan

    The-AI-Directory-Company/agents-and-skills/skills/disaster-recovery-plan Skill

    2★ repo

    Write disaster recovery plans with RPO/RTO targets, failover procedures, communication protocols, and testing schedules — ensuring business continuity when systems fail.

  • Go to market plan

    The-AI-Directory-Company/agents-and-skills/skills/go-to-market-plan Skill

    2★ repo

    Write go-to-market plans with positioning, target segments, channel strategy, pricing context, launch timeline, and success metrics — connecting product value to market execution.

  • Integration specification

    The-AI-Directory-Company/agents-and-skills/skills/integration-specification Skill

    2★ repo

    Write integration specifications — defining data flows, API contracts, authentication, error handling, retry logic, and monitoring requirements for system-to-system connections.

  • Okr writing

    The-AI-Directory-Company/agents-and-skills/skills/okr-writing Skill

    2★ repo

    Write OKRs (Objectives and Key Results) with measurable outcomes, scoring rubrics, and alignment checks across team and company levels.

  • Onboarding plan

    The-AI-Directory-Company/agents-and-skills/skills/onboarding-plan Skill

    2★ repo

    Design structured onboarding plans — for new hires, new customers, or new users — with milestone-based progression, success criteria, and feedback loops.

  • Prd writing

    The-AI-Directory-Company/agents-and-skills/skills/prd-writing Skill

    2★ repo

    Write clear, comprehensive Product Requirements Documents with problem statements, success metrics, scope boundaries, and actionable requirements.

  • Product launch brief

    The-AI-Directory-Company/agents-and-skills/skills/product-launch-brief Skill

    2★ repo

    Write product launch briefs that align all teams — with positioning, target audience, key messages, launch timeline, channel plan, success metrics, and cross-functional responsibilities.