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
alexe-ev/product-plugins/ux-research/skills/plan-ux-research Skill
0★ repoDefine a UX research plan including methods, participants, goals, and timeline. Use this skill when a team needs to structure a research effort before executing it.
alexe-ev/product-plugins/ux-research/skills/write-design-brief Skill
0★ repoWrite a clear design brief that gives designers the problem framing, constraints, and success criteria they need to start design work. Use this skill when handing a problem from product to design for exploration.
deokjinlog/intent-locked-workflow/skills/code-pretty Skill
0★ repoUse AFTER verifying-spec passes and BEFORE generating-html during the initial-creation iteration loop of <slug>-implementation-plan.md ONLY. Dispatches a Sonnet subagent that performs a strict format + 자명한 정리 pass on every "수정 후" code block in the plan. NEVER touches "원본" blocks, prose, or tables. Stops firing once the first change-history entry is logged. Idempotent on already-clean blocks (no-op rule).
deokjinlog/intent-locked-workflow/skills/og-writing-plans Skill
0★ repoUpstream-original (superpowers 5.0.7) writing-plans, exposed under intent-locked-workflow. Use when invoked via /og-write-plan after /og-brainstorm. Identical behavior to upstream writing-plans except for the og- naming and downstream pointer (handoff goes to og-executing-plans / subagent-driven-development). Use this when the intent-locked-workflow extended workflow (변경이력 / 위험주석 / verifying-spec / generating-html) feels heavy and you want the original superpowers experience.
deokjinlog/intent-locked-workflow/skills/subagent-driven Skill
0★ repo서브에이전트 실행 경로 (1인 개발 + 사전 검증 게이트 가정). v1.1.14+ wave-parallel — 메인이 plan 분석으로 DAG 추론 → wave 단위 pair-parallel dispatch (implementer + spec reviewer). 메인이 wave 끝에서 직렬 commit + post-hoc 충돌 검출. quality reviewer는 사전 verifying-spec + TDD + RISK + 변경이력으로 분산 흡수.
deokjinlog/intent-locked-workflow/skills/verifying-spec Skill
0★ repoUse immediately after writing <slug>-tech-design.md (via tech-design) or <slug>-implementation-plan.md (via writing-plans), before final user handoff. Performs main-agent self-verification — A) consistency cross-check between target MD and all upstream MDs, plus C) code impact analysis (file existence, callers, side-effect candidates) — and produces a structured 4-axis report for user decision.
deokjinlog/intent-locked-workflow/skills/writing-plans Skill
0★ repoUse when <slug>-requirements.md and <slug>-tech-design.md exist for a feature, before touching code. Reads both, produces <slug>-implementation-plan.md (단계별 plan with bite-sized TDD tasks). Ends with the main agent's spec verification gate (verifying-spec) — covers 요구사항 + 개발방향 ↔ 구현계획서 consistency + code impact.
clever-cc-plugins/cc-concept/plugins/cc-concept/skills/cc-concept-content-strategy Skill
0★ repoUse this skill to produce an editorial planning framework covering content pillars, topic clusters, content type mix, and publishing cadence. Invoke when the user asks for a "content strategy", "editorial plan", "content pillars", or "topic clusters". Produces a content strategy document and registers it as project context so cc-content skills can align individual pieces to it.
clever-cc-plugins/cc-concept/plugins/cc-concept/skills/cc-concept-gtm Skill
0★ repoUse this skill to structure a go-to-market launch plan for a new product, service, feature, or market entry — audience, positioning, channel sequence, key messages, and milestones. Invoke when the user asks to "plan a launch", "go-to-market plan", "GTM plan", or names a launch type (e.g. "plan a feature release"). Produces a GTM plan and offers to save a brief.md-compatible campaign brief as a by-product.
clever-cc-plugins/cc-concept/plugins/cc-concept/skills/cc-concept-onboarding Skill
0★ repoUse this skill to set up or extend the strategic context a marketing project needs before positioning, competitive, or go-to-market work. Invoke when the user asks to "onboard for strategy", "set up strategy context", "add competitive context", or when a cc-concept skill reports a missing strategic need. Runs standalone and also recognises context an existing cc-content project already provides.
clever-cc-plugins/cc-concept/plugins/cc-concept/skills/cc-concept-performance-review Skill
0★ repoUse this skill to review whether a strategic concept's bets actually played out — a positioning claim, a channel allocation, a content-strategy pillar mix, a GTM milestone, or a campaign's stated goals. Invoke when the user says "review our strategy performance", "did our positioning hold up", "how did the campaign perform against plan", "review the channel mix results", or "strategic performance review". Works from whatever performance data the owner pastes in — there is no analytics API integration. Do NOT use it to analyze how an individual content piece performed structurally or tonally — that is cc-content-performance-review's job, a different plugin's skill at the content-piece altitude, not the strategy altitude.
yumih1129/skills-repo/skills/requirements-brief Skill
0★ repo将用户口语化、零散或模糊的需求整理为结构化、可交付的需求简报。适用于需求梳理、需求改写、需求补全、范围界定、验收标准整理、待确认项提炼,以及把对话记录转成正式需求简报时使用。
telefrek/vallorcine/skills/feature-plan Skill
0★ repoProduce a work plan and stub implementations from the brief and domain analysis
telefrek/vallorcine/skills/spec-author Skill
0★ repoAuthor a hardened spec through multi-pass adversarial review
telefrek/vallorcine/skills/spec-backfill Skill
0★ repoBackfill @spec annotations on existing code for an APPROVED spec (or --all specs)
telefrek/vallorcine/skills/spec-init Skill
0★ repoBootstrap the spec corpus for this project
telefrek/vallorcine/skills/spec-resolve Skill
0★ repoResolve a context bundle of relevant specs for a feature
telefrek/vallorcine/skills/spec-split Skill
0★ repoSubdivide a mature spec into a parent + child sub-domain specs
telefrek/vallorcine/skills/spec-verify Skill
0★ repoVerify a spec against its implementation and repair violations
telefrek/vallorcine/skills/spec-write Skill
0★ repoRegister a spec file in the manifest and validate it
telefrek/vallorcine/skills/spec Skill
0★ repoQuery specs, discover gaps, and trace change impact
telefrek/vallorcine/skills/work-decompose Skill
0★ repoDecompose a work group into work definitions with dependency graph
telefrek/vallorcine/skills/work-plan Skill
0★ repoSpecify a work definition — produce specs and ADRs without implementation
bokuwalily/claude-code-skills/skills/youtube-competitor-decompose Skill
0★ repo競合YouTubeチャンネルを韓国大手YouTuber式に要素分解したい時に発火。yt-dlp(APIキー・クォータ不要)でタイトル文字数/動画長/投稿時間帯/タグ/再生分布を機械抽出し、サムネ等のvision次元は別途補完。shukatsu-navi等のSEO競合調査・ジャンル参入前の偵察に使う。
yisean/claude-spec-skills/spec-design Skill
no license0★ repo以已定稿 PRD + 原型为输入,做技术设计:概要设计(架构/模块/技术选型/关键决策/接口清单/NFR 承接/风险)、数据 ER 模型(Mermaid)、详细设计(按模块/接口/关键流程组织,写接口签名与核心逻辑),写入 docs/engineering/design/。Use when PRD 与原型已确认、要先把架构与数据模型定下来,产出供 /spec-plan 拆任务。设计复用与 PRD 相同的 NNN 序号;任务拆分与 migration 在 /spec-plan。
yisean/claude-spec-skills/spec-plan Skill
no license0★ repo以已定稿 PRD + 原型 + 设计为输入,生成可执行的实现计划:把设计拆成可独立认领的实现单元(U:Files/依赖/Patterns/原型页面/设计依据/Execution note/覆盖需求/Test scenarios)、DB migration(与设计 ER 逐字段一致)、三向覆盖矩阵,写入 docs/engineering/plans/。Use when 技术设计(/spec-design)已完成、要据设计拆任务与迁移脚本。计划复用与 PRD/设计相同的 NNN 序号;架构与数据模型在 /spec-design,不在此重做。
yisean/claude-spec-skills/spec-prd Skill
no license0★ repo把原始需求澄清并定稿为规范化 PRD(带 R/F 功能需求编号与 AE/AC 可验收标准),写入 docs/product/prd/。Use when 用户给出原始需求/想法、要写或更新一份 PRD、把一个特性意图固化成正式需求。新需求取新序号;已有特性的增量改动请改用 /spec-change。
yisean/claude-spec-skills/spec-prototype Skill
no license0★ repo依据已定稿 PRD,按 prototype/_spec.md 生成或更新纯静态可点击原型(仿 Element-UI、无外部依赖、双击即开),用于内部对齐或向客户演示。Use when PRD 已完成、需要把界面/交互画成原型、或要把原型发客户确认。客户确认后的需求变更请走 /spec-change(先回流 PRD 再改原型)。
specdd/plugin-claude/skills/specdd-plan Skill
0★ repoUse when Claude Code is asked to plan SpecDD work or needs to resolve unclear scope, authority, risk, or verification before editing.
gordon1210/agent-goodies/plugins/idea-workbench/skills/plan-implementation Skill
0★ repoTurn an explicitly approved, implementation-ready design doc or equivalent specification into an actionable plan of vertical, independently verifiable slices with requirement traceability and explicit dependencies. Use when design decisions are settled and the user wants implementation tasks, tickets, sequencing, or a build plan; do not use to invent unresolved product or architecture decisions.
gordon1210/agent-goodies/plugins/idea-workbench/skills/review-design-doc Skill
0★ repoEvaluate an existing product or technical design document for comprehension, consistency, risk coverage, and implementation readiness. Use before approval or implementation planning, after substantial design changes, or when a team needs an independent critique that exposes missing decisions, contradictions, unsupported assumptions, unsafe failure modes, and verification gaps without rewriting the source by default.
gordon1210/agent-goodies/plugins/idea-workbench/skills/write-design-doc Skill
0★ repoTurn an approved idea brief, selected solution direction, or established product and technical context into a risk-scaled design document. Use when a direction has been chosen and implementation needs concrete boundaries, flows, interfaces, data behavior, failure handling, validation, and delivery decisions, or when an existing draft needs to become ready for independent review and planning.
kennyolofsson23-netizen/claude-code-config/skills/ai-marketing-suite/skills/market-proposal Skill
no license0★ repoThe most comprehensive Claude Code setup — 29 skills, 9 plugins, 13 hooks, 8 agents, 8 commands. Self-documenting, self-improving, CLI-first. Includes self-interview prompt for personalization.
kennyolofsson23-netizen/claude-code-config/skills/claude-ads/skills/ads-plan Skill
no license0★ repoStrategic paid advertising planning with industry-specific templates. Covers platform selection, campaign architecture, budget planning, creative strategy, and phased implementation roadmap. Use when user says "ad plan", "ad strategy", "campaign planning", "media plan", "PPC strategy", or "advertising plan".
kennyolofsson23-netizen/claude-code-config/skills/geo-proposal Skill
no license0★ repoAuto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo", "generate proposal", or after completing a GEO audit for a prospect.
The same file is in 2 other repositories
kennyolofsson23-netizen/claude-code-config/skills/kaizen/plan-do-check-act Skill
no license0★ repoIterative PDCA cycle for systematic experimentation and continuous improvement
kennyolofsson23-netizen/claude-code-config/skills/launch-strategy Skill
no license0★ repoWhen 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 3 other repositories
kennyolofsson23-netizen/claude-code-config/skills/pricing-strategy Skill
no license0★ repoWhen 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
kennyolofsson23-netizen/claude-code-config/skills/sdd/plan Skill
no license0★ repoRefine, parallelize, and verify a draft task specification into a fully planned implementation-ready task
kennyolofsson23-netizen/claude-code-config/skills/seo-content Skill
no license0★ repoSEO content strategy, writing, and auditing. Plans topic clusters, writes search-optimized articles, and audits existing pages. Use for blog posts, landing page copy, content calendars, keyword research, SEO audits, and content strategy planning. Use when the user says "SEO", "content plan", "write blog post", "optimize for search", "keyword research", "audit page", "content calendar", "write an article", "content strategy", or any content marketing task.
hsnuhow/how-skills/plugins/taiwan-biz-research/skills/strategy-frameworks Skill
no license0★ repoPick the right strategy framework for a Taiwan business question — and know when a framework is the wrong move. Routes a question ("should we enter this market", "how big is this", "why are we losing share", "is now the time") to the one framework that answers it, binds each framework to the tw-data command that feeds it with real numbers, and says which frameworks are undeliverable in Taiwan because the data does not exist. Use this before analysing a market-entry, sizing, competitor, investment or timing question, whenever someone proposes running a SWOT/Porter/BCG, or when an analysis has collected data but has no shape yet.
macmenes/vantage/skills/vantage-content-plan Skill
0★ repoTRIGGER when the user wants to PLAN their own content / content strategy — "content strategy", "content plan", "what should we write", "topic ideas", "content calendar", "pillar pages", "content briefs", "blog plan". Part of the `vantage` (Vantage.os) Content Engine pack. Builds a pillar/cluster plan, a prioritized topic backlog, full content briefs, and an editorial calendar. DO NOT trigger for ANALYZING a competitor's content (use vantage-content), live keyword DATA (use seo-dataforseo), or writing the final article (use copywriting / seo-content-writer).
Studio-Moser/skills-n-stuff/plugins/product-pulse/skills/weekly-strategist Skill
0★ repoWeekly strategic intelligence. Dispatches 5 analyst agents (Market Scout, Competitor Tracker, Audience Analyst, Growth Analyst, Product Scout), reads the last 7 daily reports, and produces a strategy brief + recommendations for PM ingestion. Reads pulse-config.yaml from the nearest research directory. Run Monday mornings or whenever you need strategic direction. Trigger: "run weekly strategy", "weekly brief", "what should we focus on", "weekly priorities", or /product-pulse:weekly-strategist.
Evan-Daruwalla/claude-skill-suite/milestone-track Skill
0★ repoREAD-ONLY roadmap status rollup for a PRD_ROADMAP.md-style doc. Parses markdown checkboxes ("- [ ]"/"- [x]"), table-cell glyphs (☐/☑), ~~struck~~ items (counted as dropped/folded, NEVER as open), and milestone headings ("## N.", "### M...", rows of a MILESTONES table), then rolls up per-milestone done/open/struck counts, an overall completion %, and the FIRST open item as "next:". Fork-aware: if a "## CURRENT DIRECTION" heading exists, default scope is that fork section only (--all covers the whole file), and the output says which scope it used. Use when the user says "milestone status", "roadmap rollup", "how much of the PRD is done", "what's next on the roadmap", "PRD progress", or "milestone-track". Never edits the PRD. Deterministic, zero dependencies, no model calls.
Evan-Daruwalla/claude-skill-suite/reorg-proposal Skill
0★ repoProduce a NON-DESTRUCTIVE, read-only proposal for restructuring a codebase's file/directory layout — current tree, proposed tree, and a per-move risk table — WITHOUT moving, renaming, or editing any file. Use ONLY when the user explicitly asks to propose/plan/design a reorganization or directory structure. Do NOT use for generic organize/clean-up/tidy/refactor requests, for performing moves, or for code-level refactors.
Evan-Daruwalla/claude-skill-suite/research-brief Skill
0★ repoDeep research on a technical or market topic producing a structured, sourced brief saved to the project's docs. Use when the user says "research X", "deep dive into X", "do research into X and propose candidates", or asks for analysis of an architecture, paper, strategy, or market event. Not for quick factual questions.
dkmqflx/claude-tools/.claude/skills/to-prd Skill
no license0★ repoTurn 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
prvthmpcypher/skills-design/skills/icon-brief-writer Skill
0★ repoYou are a design systems expert specializing in iconography. When given feature descriptions, recommend appropriate icons with clear briefs for designers or icon libraries. ## Process 1. List all features and actions needing icons 2. Match each with a clear, universally understood concept 3. Specify icon style (line, filled, duotone, etc.) 4. Provide size and spacing guidelines 5. Suggest icon library sources ## Output Format ## Icon Brief: \[App Name\] ### Style Guide - Type: Line/Filled/Duotone - Stroke width: 2px - Grid: 24x24 - Corner radius: 2px ### Icon Mapping <table header-row='true'> <tr> <td>Feature</td> <td>Icon Concept</td> <td>Library Name</td> <td>Size</td> </tr> <tr> <td>Search</td> <td>Magnifying glass</td> <td>search</td> <td>20px</td> </tr> <tr> <td>Settings</td> <td>Gear/cog</td> <td>settings</td> <td>20px</td> </tr> </table> ### Accessibility - All icons have...
prvthmpcypher/skills-design/skills/motion-graphics-producer Skill
0★ repoWrites detailed motion graphics execution briefs — shot-by-shot animation timing, easing curves, transition types, and keyframe descriptions ready to hand to an animator or implement in code (CSS/SVG animation, Lottie, After Effects). Use this whenever the user wants a motion graphics concept turned into an executable spec, needs animation timing/easing guidance, wants a logo animation or UI micro-interaction planned in detail, or has an animation-planner-level concept that needs to become a buildable brief.
agony1997/TouchFish-Skills/plugins/spec-to-md/skills/spec-to-md Skill
0★ repo讀取規格文件轉換為 AI coding 實作文件(.md),產出技術規格、後端實作指示、前端實作指示等結構化文件。 使用時機:當使用者提供規格文件並要求產生實作文件、轉換規格為 coding 文件時觸發。 關鍵字:規格轉換、spec to md、產生實作文件、讀取規格、分析需求、coding 文件、開發文件、 to md、toMD、toMd、TOMD、specification, 規格文件, 需求文件, 需求轉換, 實作指示, 實作文件, 技術規格, 文件生成, 文件產生, 前端實作, 後端實作, convert, 轉換。
The same file is in 2 other repositories
ArthurZakirov/SystemSmith/skills/swe-method Skill
0★ repoGuide for working through a Jira story efficiently by separating context gathering, immutable evidence collection, codebase exploration, human-in-the-loop specification refinement, execution planning, and implementation. Use when turning a ticket into a reliable engineering workflow instead of jumping straight to code.
AI-Driven-School/aiki/.claude/skills/requirements Skill
0★ repoGenerate a requirements document with user stories, acceptance criteria, and constraints. Use when defining features, writing specs, or running /requirements before implementation.
AI-Driven-School/aiki/.claude/skills/spec Skill
0★ repoGenerate UI screen design documents with component lists, state transitions, interactions, and responsive breakpoints. Use when designing screens, creating wireframes, or running /spec.
jgsystemsconsulting/jgs-goal-spec/skills/spec-review Skill
0★ repoAutonomously harden an engineering specification through a roundtable of independent engineering-discipline reviewers (architecture, security, test/QA, operations, product). Each reviewer is a real subagent thinking independently; the orchestrator collects findings, revises the spec itself, and loops until convergence (no CRITICAL or MAJOR findings) with NO user checkpoints. Use when you say "review this spec", "harden this spec", "spec review", "run the roundtable on this spec", or want a spec battle-tested before implementation. Self-contained, with no dependency on any other skill.
ArthurZakirov/ProofStack/skills/proof-promise-plan-openers Skill
no license0★ repoCreate strong Proof-Promise-Plan openings for articles, landing pages, README files, LinkedIn posts, videos, and guides.
latuconsinafr/claude-code-config/skills/plan Skill
no license0★ repoUse before writing any code for a new feature, task, or significant change — produces a structured implementation plan with affected files, ordered steps, risks, and open questions. Always invoke this at the start of any non-trivial implementation task and wait for explicit approval before writing code.
latuconsinafr/claude-code-config/skills/spec Skill
no license0★ repoUse before implementing a complex, high-stakes, or cross-cutting feature — produces a full technical specification including data model, API contract, edge cases, and open questions. The planning layer above /plan. Invoke this when /plan alone isn't detailed enough.
az9713/youtube-transcript-to-skills/.claude/skills/plan-feature Skill
no license0★ repoPlan a new feature before writing code. Explores the codebase, creates a structured plan with verification criteria, and only implements after approval.
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/brain-dump-to-phased-roadmap Skill
0★ repoUse when the user presents a loose collection of items (a brain-dump, an inbox-list, a "I want to do all of these" list, scattered TODOs) and wants help turning it into an actionable plan — phases with dependencies, entry triggers, and confirmation questions on each meaningful design decision. Trigger on phrases like "I have a few things here", "clean up the brain-dump", "how do I tackle all this", "roadmap from these items", "consolidate the inbox", "I don't know where to start", "make me a plan out of this", "consolidate this list into a plan", "turn this dump into a roadmap". Do NOT load when the user already has a phase plan and wants to execute it (use gsd:gsd-execute-phase), when there is a single concrete task (just do it), or for design exploration where the items are not yet committed work (use design-first-iteration). Complements gsd:gsd-new-milestone and gsd:gsd-plan-phase — this skill bridges the gap *before* either of those, when items are still unstructured and clusters are not yet visible.
Decision plan hypothesis matrix
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/decision-plan-hypothesis-matrix Skill
0★ repoUse BEFORE implementing a non-trivial decision-driven task where multiple outcomes are plausible — backtest planning, algorithm comparison, architecture choice, migration strategy, "should build X or not". Trigger on phrases like "should build X", "plan a backtest", "I need a decision", "test algo variants", "how do I measure success", "max-effort session", "choose refactoring strategy", "define Compound-GO". Produces a Plan-Note with explicit Hypothesis-Matrix (each H + counter-thesis + Distinguishing Metric), Compound-GO-Logic, Out-of-Scope, and Done-Definition. Do NOT load for single-path implementations with no decision ("fix this typo"), brainstorming/exploration phase (use `superpowers:brainstorming` first), plans without binary GO/NO-GO outcome (use `superpowers:writing-plans`), or tasks without a measurable success criterion.