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

  • Feature scoping

    stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/feature-scoping Skill

    1★ repo

    [discovery-phase pack · scoping] Translates the chosen solution direction and top risks into a tight, build-able scope with explicit in/out boundaries per area. Designed to be reusable as a chunk of a proposal or SoW. Produces scope-doc.md. Reads discovery-context.md, opportunity-tree.md, and risk-assumption-map.md.

  • Proposal

    stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/proposal Skill

    1★ repo

    [discovery-phase pack · deliverables] Generates a client-facing proposal document consolidating problem understanding, recommended approach, scope, assumptions, dependencies, team, timeline, and headline pricing guidance. Designed for pre-sale or paid-discovery conclusion. Produces proposal.md. Reads discovery-context.md and most upstream artifacts.

  • Prototype plan

    stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/prototype-plan Skill

    1★ repo

    [discovery-phase pack · validation] Plans a runnable prototype that retires the top assumptions in a realistic environment. Differs from MVP by being internally-scoped (limited audience, throwaway by default). Includes demo script. Produces poc-plan.md and a runnable skeleton scaffold. Reads discovery-context.md.

  • Research planning

    stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/research-planning Skill

    1★ repo

    [discovery-phase pack · discovery] Designs the evidence-gathering plan based on what access is actually available. Branches into direct interviews, SME workshops, secondary research, support-data analysis, or a mix. Produces research-plan.md and (if applicable) interview-guide.md. Reads discovery-context.md.

  • Stakeholder mapping

    stanislavnianko/product-discovery-claude-skills/plugins/discovery-phase/skills/stakeholder-mapping Skill

    1★ repo

    [discovery-phase pack · discovery] Maps client-side AND agency-side stakeholders with their stakes, success metrics, concerns, decision rights, and conflicts. Two-tier map. Surfaces deal-breakers in week 1, not week 4. Produces stakeholder-map.md. Reads discovery-context.md.

  • Curriculum mapper

    SkillMedev/course-creator-launch-system/skills/curriculum-mapper Skill

    1★ repo

    Maps a course's scope and sequence across a term or year - units, weeks, standards coverage with introduced/developed/mastered notation, and Bloom's-level progression - and flags gaps and redundancy. Use when someone asks "map my curriculum for the year", "build a scope and sequence for this course", "audit my course for standards gaps", or is deciding unit order for a semester. Do NOT use for planning a single lesson - use lesson-plan-builder instead; for adapting one lesson to mixed readiness levels in one classroom, use differentiated-instruction.

    The same file is in 2 other repositories

  • Lesson plan builder

    SkillMedev/course-creator-launch-system/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

  • Strangler fig planner

    SkillMedev/legacy-modernization/skills/strangler-fig-planner Skill

    1★ repo

    Produces an incremental migration plan that runs a legacy and a new system side by side behind a routing seam, slicing and sequencing whole capabilities so the old system stays live until its last route is cut. Use when planning to replace or rebuild a large, business-critical system that must keep serving traffic throughout. Do NOT use when extracting a single service from a still-living monolith - use monolith-decomposer instead; for generic non-migration implementation planning, use the plan skill instead.

    The same file is in 1 other repository

  • Spec to code compliance

    simanam/theaiteam/team/skills/engineering/_trailofbits/spec-to-code-compliance/skills/spec-to-code-compliance Skill

    no license1★ repo

    Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.

    The same file is in 4 other repositories

  • Blueprint

    simanam/theaiteam/team/skills/engineering/blueprint Skill

    no license1★ repo

    Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

    The same file is in 4 other repositories

  • Content strategy

    simanam/theaiteam/team/skills/marketing/content/content-strategy Skill

    no license1★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

    The same file is in 2 other repositories

  • Free tool strategy

    simanam/theaiteam/team/skills/marketing/growth/free-tool-strategy Skill

    no license1★ repo

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    The same file is in 2 other repositories

  • Lead magnets

    simanam/theaiteam/team/skills/marketing/growth/lead-magnets Skill

    no license1★ repo

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

    The same file is in 2 other repositories

  • Site architecture

    simanam/theaiteam/team/skills/marketing/seo/site-architecture Skill

    no license1★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

    The same file is in 4 other repositories

  • Launch strategy

    simanam/theaiteam/team/skills/marketing/strategy/launch-strategy Skill

    no license1★ repo

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

    The same file is in 1 other repository

  • Pricing strategy

    simanam/theaiteam/team/skills/marketing/strategy/pricing-strategy Skill

    no license1★ repo

    When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

    The same file is in 5 other repositories

  • Content brief

    SkillMedev/content-marketing-engine/skills/content-brief Skill

    1★ repo

    Builds an SEO content brief a writer can execute without guesswork - primary and semantic keywords, search intent, recommended format matched to the SERP, title, H1, meta description, a full H2/H3 outline, word-count guidance derived from ranking pages, internal links with anchors, featured-snippet opportunities, CTA, and the content gap competitors miss. Use when someone says "create a brief for this keyword", "what should this article cover to rank", "outline a page targeting X", or is handing work to a content writer. Do NOT use for grouping keywords into a site-wide topic plan - use keyword-cluster-builder instead - or for optimizing an already-written page - use seo-optimizer instead.

    The same file is in 2 other repositories

  • Longevity protocol

    SkillMedev/health-and-longevity/skills/longevity-protocol Skill

    1★ repo

    Assembles an evidence-tiered weekly longevity routine across the four pillars with the strongest healthspan data - sleep, zone 2 aerobic work, strength training, and dietary pattern - plus stress and connection, delivered as a filled weekly template with honest evidence labels. Use when someone asks "build me a longevity routine", "what actually extends healthspan", "audit my health habits", or "is this supplement stack worth it". General wellness guidance, not medical advice. Do NOT use to program the individual pieces in depth - use zone-2-cardio-plan for the aerobic block, strength-training-plan for lifting, sleep-optimizer for sleep, nutrition-planner for macros; for HIIT/conditioning use fitness-program; for interpreting labs use bloodwork-explainer.

    The same file is in 1 other repository

  • Nutrition planner

    SkillMedev/health-and-longevity/skills/nutrition-planner Skill

    1★ repo

    Sets personal nutrition targets - protein at 1.6-2.2 g/kg, a calorie budget from goal and activity, fiber and hydration floors - and a repeatable meal structure with a review-and-adjust protocol for fat loss, muscle gain, or maintenance. Use when someone asks "how much protein should I eat", "set my macros for a cut", "why has my weight stalled", or "build me a sustainable diet framework". General wellness guidance, not medical advice. Do NOT use to produce a specific week of recipes with a shopping list and prep schedule - use meal-planner instead (this skill sets the targets; meal-planner cooks to them); for the broader multi-pillar health routine, use longevity-protocol.

    The same file is in 1 other repository

  • Strength training plan

    SkillMedev/health-and-longevity/skills/strength-training-plan Skill

    1★ repo

    Use when someone starts lifting, hits a strength or hypertrophy plateau, restructures a lifting program, or wants to build strength or muscle - designing a progressive resistance program with splits, compound movement patterns, sets/reps, progressive overload, and deloads from barbells and dumbbells. General fitness guidance, not medical advice. Owns resistance/strength training only. Do NOT use to program high-intensity interval conditioning or circuits (use fitness-program), a steady-state aerobic-base or Zone 2 block (use zone-2-cardio-plan), or a mobility/flexibility routine (use mobility-routine).

    The same file is in 1 other repository

  • Zone 2 cardio plan

    SkillMedev/health-and-longevity/skills/zone-2-cardio-plan Skill

    1★ repo

    Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).

    The same file is in 1 other repository

  • One pager designer

    SkillMedev/document-studio/skills/one-pager-designer Skill

    1★ repo

    Writes a decision-driving one-pager - problem, evidence, impact, and a specific ask compressed into a single page readable in under three minutes. Use when someone asks "turn this into a one-pager", "write a brief for leadership", "I need a one-page pitch for this decision", or is preparing a document a busy reader must act on from one page. Do NOT use for a client-facing sales proposal with pricing and scope - use sales-proposal-writer instead; for condensing an existing long document use executive-summary; for multi-slide narratives use slide-deck-builder.

    The same file is in 1 other repository

  • Gate builder

    dayvisonassis/sdd-skills/skills/gate-builder Skill

    1★ repo

    Builds the deterministic quality-gate infrastructure for a project (typecheck, lint with zero-warnings, dependency/architecture checks, tests, dead-code, and a single runGate entry point) from the Deep Analysis Report (+ Architecture Analysis Report). Auto-detects greenfield vs. brownfield, proposes a gate plan for confirmation, then writes the configs/scripts and verifies each gate runs. The gates it builds are later declared in each feature's contract.md by spec-writer.

  • Implement feature

    dayvisonassis/sdd-skills/skills/implement-feature Skill

    1★ repo

    Implements a feature autonomously based on its spec, plan, AND contract.md, committing one commit per phase, satisfying the contract's quality gates and observable criteria, writing progress.json, and reporting results against the feature's acceptance criteria. Delegates test writing to the matching test-writer skill (unit/integration/monorepo) by path/stack when the project fits, and falls back to writing tests itself otherwise.

  • Prd writer

    dayvisonassis/sdd-skills/skills/prd-writer Skill

    1★ repo

    Generate complete PRDs (Product Requirements Documents) through iterative clarification. Use when: (1) Starting a new project and need structured requirements, (2) Creating product specifications with 9-section PRD format, (3) Defining product scope from a description or context files. Keywords: "prd", "product requirements", "create PRD", "generate PRD", "new product", "requirements document".

  • Spec writer

    dayvisonassis/sdd-skills/skills/spec-writer Skill

    1★ repo

    Generates technical implementation spec, plan, AND an operational contract for one or more features based on PRD, codebase analysis, and iterative clarification. Produces contract.md (environment contract, quality gates, coverage manifest, observable criteria) consumed by implement-feature and evaluator. Supports batch mode for generating multiple features from the same wave in parallel.

  • Agentmaster plan

    rhawk117/agentmaster/skills/agentmaster-plan Skill

    1★ repo

    Cost-tiered planning orchestrator. Use whenever the user wants an implementation plan, a spec, a root-cause investigation, or asks "how should we build/fix/refactor X" before code changes — especially multi-file features, bug hunts, refactors, and dependency problems. Keeps frontier-model reasoning for decisions only. Dispatches cheap subagents (scout on haiku, code-analyst on sonnet) for all repository and dependency evidence, stress-tests the draft with a fresh-context plan-critic that assumes the plan is wrong, then formalizes with the writing-plans skill. Trigger on "plan", "make a plan", "spec this out", "investigate before we change anything", or /agentmaster-plan.

  • Forge brief

    luminary19/atelier/skills/forge-brief Skill

    no license1★ repo

    Forge suite — define the 3D asset brief and write FORGE.md (the project-memory file every other Forge skill reads). Produces: a completed FORGE.md at the project root with target engine, coordinate system, poly/texel budgets, render settings, PBR workflow, the determinism contract (seed + sample counts for idempotent rebuilds), output paths, and (when ATELIER.md is present) the extracted world/aesthetic/signature-moment/OKLCH-hue that drives look-dev. Use this FIRST whenever starting any Forge 3D pipeline — including "define the asset", "set up a 3D project", "what are the budgets for this mesh", "create FORGE.md", "brief a 3D asset", "extract the aesthetic from ATELIER.md for Blender", "what engine is the target", "set poly budget", "set texel density", "configure render engine". (The bare "init Forge" / "forge init" phrase is owned by the `forge` router's `init` mode, which scaffolds FORGE.md inline and then calls this skill — this skill does not claim that trigger.) HEADLESS-ONLY: driven from code, output verified by reading a PNG. Part of the Forge suite.

  • Example mapping

    iggmasterdev/badquality-lab/example-mapping Skill

    1★ repo

    Turn a raw user story or feature request into a shared, testable specification BEFORE coding starts: clarifying questions, concrete examples, acceptance criteria as Given/When/Then, conditions of satisfaction, a ripple-effect impact list, and a "ready / not ready" verdict. Use this whenever someone is refining, grooming, or kicking off a story; writing or reviewing acceptance criteria; preparing a three-amigos / example-mapping session; checking a Definition of Ready; or asking "what should this feature actually do" or "is this story ready to build". Trigger even if the user only pastes a story and asks for tests or scenarios — the right first move is to map examples, not jump to test cases.

  • Expert product strategist

    mehtab78/skills/skills/expert-product-strategist Skill

    1★ repo

    Product strategy specialist — prioritization, scoping, roadmaps, feature trade-offs, MVP definition, success metrics, user-impact framing. Use when the task is about WHAT to build or WHY, rather than how. Normally invoked by model-router.

  • Estimation and scoping

    pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/estimation-and-scoping Skill

    no license1★ repo

    Honest sizing and scope — probe before promising, surface 10x discoveries immediately (never silently absorb or shrink), vertical slices, calibrate finish quality to the ask. Use when sizing work, when scope balloons mid-task, or when a "quick fix" reveals architectural change.

  • Task decomposition

    pipipip169/fable5-handoff/sources/adamentwistle-fable-skills/task-decomposition Skill

    no license1★ repo

    Planning discipline for multi-step work — acceptance test first, read the terrain, dependency-ordered steps, de-risk the riskiest step early, re-plan on surprise. Use at the start of any task touching 3+ files or steps, and mid-task when something invalidates the approach.

  • Openapi spec security scan

    Dolphinllc/claude-security-skills/skills/defensive/web/openapi-spec-security-scan Skill

    1★ repo

    Defensive security scan for OpenAPI 3.x specifications (openapi.yaml / openapi.json). Detects missing global security, unprotected mutating operations, HTTP-only servers, loose schemas (additionalProperties true, missing required), wildcard CORS, missing 401/403 responses, PII in examples, and weakly-typed parameters. Invoke when the user asks to "review", "audit", or "scan" an OpenAPI / Swagger spec, or when editing files named openapi.{yaml,json}, swagger.{yaml,json}, or under api/ directories.

  • Mktg content strategy

    MehdiBatExpert/MarketingPilot/commands/mktg-content-strategy Skill

    1★ repo

    Planifier la stratégie de contenu VibeCraft : topic clusters, piliers éditoriaux, calendrier de publication, roadmap contenu. Utiliser dès que Mehdi mentionne stratégie contenu, quoi écrire, blog strategy, piliers de contenu, calendrier éditorial, roadmap contenu, topics à couvrir, content marketing, ou ne sait pas quoi produire. Ne pas utiliser pour rédiger le contenu (mktg-copywriting) ou posts sociaux individuels (mktg-social-content).

  • Mktg pricing strategy

    MehdiBatExpert/MarketingPilot/commands/mktg-pricing-strategy Skill

    1★ repo

    Définir ou réviser la stratégie de prix d'un produit VibeCraft : positionnement tarifaire, tiers, pricing psychologique, freemium vs payant, one-shot vs abonnement. Utiliser dès que Mehdi mentionne fixer un prix, revoir son pricing, définir des tiers, price trop cher, price trop pas cher, créer un plan gratuit, ou toute phrase du type "combien je vends ça", "mon pricing est bon ?", "je sais pas quoi mettre comme prix", "freemium ou payant ?", "abonnement ou one-shot ?", "pricing pour X", "tier pricing". Produit une recommandation de pricing argumentée avec options chiffrées et logique de positionnement. Ne pas utiliser pour : rédiger la page de tarification (utiliser mktg-copywriting), créer un comparatif concurrent (utiliser mktg-sales-enablement).

  • Risk strategy

    TimurTsedik/ru-market-analyst/risk-strategy Skill

    1★ repo

    Используй, когда есть готовый снимок позиций РФ (с оценками) и нужны корзины риска, режим рынка и стратегия — что-если, варианты замен, что поменять; опц. вероятностный тир Monte-Carlo (ES/CVaR, перцентили, fan-chart) по запросу «глубоко». Не для парсинга сырых отчётов.

  • Strategist analyst framework

    KIRRAWA/cogniforge/skills/strategist-analyst-framework Skill

    no license1★ repo

    冷分析师·谋略推演框架。汇编12+位真实分析师/谋略家的著作方法论——情报分析(Heuer竞争性假设ACH/Kent概率语言)、 预测科学(Tetlock超预测/Kahneman偏差)、博弈战略(Schelling/克劳塞维茨/马基雅维利)、 法证溯因(Locard交换原理/福尔摩斯排除法/Hans Gross)、反欺骗(Whaley隐真示假)、 中国谋略(孙子五事七计/韩非参验/曾国藩结硬寨)。双模式可切换:【分析师模式】前向推演决策与谋略, 【侦探模式】后向还原真相与识破谎言。用途:给复杂局面做结构化推演、看穿信息背后的动机与欺骗、 设计谋略布局、冷静去偏见地逼近真相。触发词:「分析师模式」「侦探模式」「冷分析师」「楚轩模式」 「谋略推演」「竞争性假设」「帮我推演」「谁在撒谎」「还原真相」「看穿这件事」「概率是多少」 「测谎」「核查真伪」「溯源」「信息验证」「可疑信号」「哪里不对劲」。 EN triggers: strategic analysis, game theory analysis, strategy framework, analyze the situation, who benefits, strategic forecast, strategic thinking, deception detection. 不在普通闲聊或一般信息查询上自动触发——仅当涉及决策推演、真相还原、欺骗识别、谋略设计等 需要结构化冷分析的场景时激活。

  • Wow director

    praveentewatia26/award-grade/skills/wow-director Skill

    1★ repo

    Runs the full award-grade agency pipeline as a creative director — boots from the project taste ledger (design/TASTE.md) so settled taste stays settled, interrogates the brief down to one feeling, forces a choice between three concept territories, commits to a single signature moment, assigns sibling skills and budgets, and drives the build/judge/ship loop until verified numbers exist. USE WHEN: "build me an award-worthy site", "make this feel like an Awwwards winner", "design a landing page that people remember", "I have a brief, where do we start", "plan a portfolio site with wow factor", "creative direction for this product page", "which effects should this site have", "orchestrate a full redesign", "our site looks generic, direct a rework", "pitch me three creative directions", "what's the signature moment for this project", "scope this design engagement", "assemble the design pipeline for this app", "turn this Figma into something jury-grade".

  • Market intelligence

    kaustavr19/claude-skills/skills/market-intelligence Skill

    1★ repo

    Given a product name, idea, abstract, target audience, or competitor list, conducts a thorough strategic market intelligence brief: market trends, audience psychographics, full competitor deep-dives (business model, pricing, brand identity — voice, visual, messaging, content/channel strategy — plus SWOT per competitor), and strategic edge synthesis (unique differentiators, feature gap analysis, GTM angle, pricing strategy). Outputs a structured saveable markdown report. Trigger when the user shares a product idea, asks about competitors, wants to understand a market, or uses phrases like "market research", "competitive analysis", "validate my idea", "who else is doing this", "what's the landscape", "help me find my edge", "is there a gap in the market", or "how should I position this".

  • Product roadmap designer

    omarfarahatoglu-tur/ai-agent-skills/skills/startup-team/product-roadmap-designer Skill

    1★ repo

    Open-source AI agent skills for Claude Code, OpenAI Codex, Cursor, and modern developer workflows.

  • Saas mvp planner

    omarfarahatoglu-tur/ai-agent-skills/skills/startup-team/saas-mvp-planner Skill

    1★ repo

    Open-source AI agent skills for Claude Code, OpenAI Codex, Cursor, and modern developer workflows.

  • Request refactor plan

    steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/request-refactor-plan Skill

    no license1★ repo

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

    The same file is in 13 other repositories

  • To issues

    steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/to-issues Skill

    no license1★ repo

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

  • To prd

    steph-frtech/cdesign-expo/.claude/marketplaces/pocock/skills/to-prd Skill

    no license1★ repo

    Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.

  • Track management

    steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/conductor/skills/track-management Skill

    no license1★ repo

    Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.

    The same file is in 1 other repository

  • Openapi spec generation

    steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/documentation-generation/skills/openapi-spec-generation Skill

    no license1★ repo

    Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

  • Security requirement extraction

    steph-frtech/cdesign-expo/.claude/marketplaces/wshobson/plugins/security-scanning/skills/security-requirement-extraction Skill

    no license1★ repo

    Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.

    The same file is in 1 other repository

  • Create milestone

    itsjavi/skills/skills/create-milestone Skill

    1★ repo

    Coding agent skills to help projects adopt spec-driven development with durable product memory documents

  • Create plan

    itsjavi/skills/skills/create-plan Skill

    1★ repo

    Coding agent skills to help projects adopt spec-driven development with durable product memory documents

  • Estimation sizing

    janellecipriano/pm-skills/skills/estimation-sizing Skill

    1★ repo

    Facilitate estimation and turn sizes into a credible delivery forecast — T-shirt sizes or story points, assumptions, and a range rather than a false-precision date. Use when the user says "estimate this", "size these stories", "how long will this take", "story points", "give me a delivery range", or needs to convert scope into a defensible timeline.

  • Okr tracking

    janellecipriano/pm-skills/skills/okr-tracking Skill

    1★ repo

    Draft and track OKRs — objectives with measurable key results, current values, and confidence/health. Use when the user says "write OKRs", "set objectives and key results", "track our OKRs", "quarterly goals", "are we on track for our KRs", or needs to define or check progress on measurable goals.

  • Prd review

    janellecipriano/pm-skills/skills/prd-review Skill

    1★ repo

    Review a product requirements document (PRD) or spec against a quality checklist and surface gaps, ambiguities, and risks before engineering starts. Use when the user says "review this PRD", "is this spec ready", "critique my requirements", "PRD checklist", or shares a doc and wants it pressure-tested before build.

  • Roadmap planning

    janellecipriano/pm-skills/skills/roadmap-planning Skill

    1★ repo

    Turn goals, themes, and initiatives into a structured product roadmap — now/next/later or quarterly — with outcomes, rough sizing, dependencies, and confidence. Use when the user says "build a roadmap", "plan the quarter/half/year", "prioritize our initiatives", "what should we work on next", or needs to sequence work against objectives.

  • Sprint planning

    janellecipriano/pm-skills/skills/sprint-planning Skill

    1★ repo

    Plan a sprint or iteration — sprint goal, available capacity, committed scope, and risks — from a backlog. Use when the user says "plan the sprint", "sprint planning", "what should we commit to this iteration", "groom the backlog into a sprint", or needs to turn priorities + capacity into a realistic commitment.

  • Stakeholder comms plan

    janellecipriano/pm-skills/skills/stakeholder-comms-plan Skill

    1★ repo

    Build a stakeholder map and a communication plan — who needs what information, at what cadence, through which channel. Use when the user says "stakeholder map", "communication plan", "comms plan", "who do we need to keep informed", "RACI for comms", or needs to plan how to keep stakeholders aligned across a program.

  • Feature

    metallurgical/ogre-runner/skills/feature Skill

    no license1★ repo

    Start an Ogre issue workflow: fetch issue/blockers into .ai/.ogre, create a planning runner prompt, and generate a compact execution plan.

  • Plan

    metallurgical/ogre-runner/skills/plan Skill

    no license1★ repo

    Alias of the `feature` skill - start an Ogre issue workflow (fetch issue/blockers into .ai/.ogre, create a planning runner prompt, generate a compact execution plan). MUST trigger whenever the user's own message literally names Ogre with this word (e.g. "ogre plan ...", "use ogre plan for this") - that explicit naming is the user choosing this workflow on purpose, and takes priority over any other project rule (e.g. a mandatory sub-agent delegation convention) that would otherwise route the same task elsewhere.

  • Review plan

    metallurgical/ogre-runner/skills/review-plan Skill

    no license1★ repo

    Review an Ogre execution plan against the repository for hallucinations, risky assumptions, missing validation, and over-scoped steps.

  • Task list

    metallurgical/ogre-runner/skills/task-list Skill

    no license1★ repo

    List every checklist step under one job/issue as a task, one row per step, from .ai/.ogre.

  • Cited brief system

    MariusGithub13/open-deal-kit/systems/cited-brief-system Skill

    1★ repo

    Turn a CIM or stack of deal documents into a structured diligence brief where every claim is cited to its source page, with a 'cannot verify' list at the end. The flagship method of the kit. Use when asked to 'read this CIM', 'build a diligence brief', 'screen this deal', or whenever you need a deal read you can actually trust.