Plan & spec
10,746 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
viktorbezdek/skillstack/communication/skills/stakeholder-alignment Skill
15★ repoAlign stakeholders in writing using RFCs, design docs, proposals, pre-reads, and decision docs with explicit role assignments (DACI, RAPID). Use when the user asks to write an RFC, design doc, proposal, pre-read, or decision doc, wants to align async stakeholders on a decision, needs to assign deciders vs consulted vs informed, wants to structure a cross-team proposal, or is preparing a pre-read for a decision meeting. NOT for structuring a generic memo (use structured-writing). NOT for stakeholder power maps (use persona-mapping). NOT for storytelling pitches or investor decks (use storytelling-for-stakeholders).
viktorbezdek/skillstack/creative-problem-solving/skills/creative-problem-solving Skill
15★ repoGenerate new ideas and breakthrough solutions using brainstorming, lateral thinking, SCAMPER, first principles reasoning, game theory, and strategic reframing. Use when the user asks to brainstorm, ideate, "think outside the box", generate alternatives, explore creative solutions, reframe a problem, or come up with ideas — especially when stuck in conventional thinking. NOT for stress-testing or finding flaws in existing ideas (use critical-intuition), NOT for making a final decision between options (use strategic-decision or prioritization), NOT for detecting bias or evaluating evidence quality (use critical-intuition).
viktorbezdek/skillstack/critical-intuition/skills/critical-intuition Skill
15★ repoStress-test, critique, and challenge existing ideas through pattern recognition, bias detection, Bayesian reasoning, blind-spot exposure, and red-flag identification. Use when the user asks to stress-test a plan, challenge assumptions, find flaws, identify risks in an idea, expose hidden biases, audit a proposal for blind spots, or "poke holes in this". NOT for generating new ideas or solutions (use creative-problem-solving), NOT for structured risk registers or mitigation plans (use risk-management), NOT for brainstorming or divergent thinking (use creative-problem-solving).
viktorbezdek/skillstack/prioritization/skills/prioritization Skill
15★ repoApply RICE, MoSCoW, ICE, and effort-impact frameworks to rank options and decide what to work on next. Use when the user asks to prioritize a backlog, rank features, decide what to build first, apply RICE or MoSCoW scoring, cut scope, or compare items by effort vs impact. NOT for defining success metrics or OKRs (use outcome-orientation). NOT for making a strategic bet under uncertainty (use strategic-decision workflow).
viktorbezdek/skillstack/product-thinking/skills/outcome-oriented-thinking Skill
15★ repoApply outcome-over-output product thinking — separating what gets built from what actually changes for the user, running the "so what" test to climb from output to outcome to impact, choosing leading vs lagging metrics, and identifying a North Star metric. Use when the user asks whether something is an outcome or an output in a product context, wants to run the "so what" test on a deliverable, wants a North Star metric, needs to choose leading indicators for a product bet, or is debating whether shipping a feature equals success. NOT for generic OKR authoring (use outcome-orientation). NOT for feedback-loop analysis (use systems-thinking). NOT for metric scoring or ranking (use prioritization).
viktorbezdek/skillstack/product-thinking/skills/trade-off-analysis Skill
15★ repoAnalyze trade-offs between competing product options using cost-benefit, opportunity cost, reversibility (one-way vs two-way doors), and second-order effects. Use when the user faces a product choice with non-trivial trade-offs, asks "what are we giving up", weighs short-term vs long-term impact, or needs to frame a decision before committing. NOT for scored prioritization of a backlog (use prioritization). NOT for quantified risk assessment (use risk-management). NOT for strategic go/no-go (use strategic-decision).
viktorbezdek/skillstack/skillstack-workflows/skills/strategic-decision Skill
15★ repoGate workflow for making a strategic decision under uncertainty when multiple options have merit and the stakes are high. Defines the success criteria first (outcome-orientation), maps what actually drives the outcome (systems-thinking), generates options including uncomfortable ones (creative-problem-solving), stress-tests each for blind spots and hidden assumptions (critical-intuition), assesses downside per option (risk-management), ranks using the original criteria (prioritization), and uses outcome-orientation as an end gate — does the top-ranked option actually achieve the outcome we defined? Use for irreversible bets, resource allocation across competing priorities, pivot/persevere decisions, hire-for-speed vs hire-for-quality choices. NOT for reversible decisions with cheap experimentation — just experiment.
allemaar/open-skills/skills/handoff-execute Skill
15★ repoExecute a handoff brief with enforced source-read discipline — load the brief's @SOURCES.required tier fully before planning, cite sources per plan step, run @OUTCOME.verify after, emit the retro per @GROUND_TRUTH_REQUIRED. Trigger when the user runs /handoff-execute <brief-path>, or pastes the activation phrase emitted by /handoff. Not auto-triggered — the receiving session invokes explicitly. Use /plan-execute for PLAN.md files (different schema); use /handoff to *create* a brief; use /cold-review for outside-agent review, not for executing the work itself.
allemaar/open-skills/skills/insight-explore Skill
15★ repoBrainstorm 3+ possible implementations before committing. Trigger when the user runs /explore or asks to "brainstorm options", "what are the ways to do this", "explore approaches", "give me alternatives", or wants divergent thinking before planning or assessment. Use insight-assess to evaluate known options, insight-critique to review an existing output, and plan-create to turn a chosen direction into an implementation plan.
allemaar/open-skills/skills/orient-roadmap Skill
15★ repoAnswers "What comes next, and what gates it?" on any subject — the increment arc (built → current → next), what shipped now, the gates, the next increment's clusters (paramount starred), and the runway of stage boxes (now → gated-next → future) plus the deferred lanes, computed fresh via a bounded read-only subagent. Trigger phrases: "/orient-roadmap", "show me the roadmap", "show me the runway", "what's next". Not /orient-status (how far along am I and when will it be done), /orient-map (what changed since I last looked), or /orient-gaps (what is stuck or missing) — orient-roadmap shows the FORWARD HORIZONS and the runway.
allemaar/open-skills/skills/plan-cleanup Skill
15★ repoPost-execution cleanup — remove planning artifacts and tech debt left behind after a plan runs. Trigger when the user runs /plan-cleanup, says 'clean up artifacts', 'remove the plan file', or 'no tech debt'. Not /plan-evolve (plans the next version) — plan-cleanup only removes leftovers and adds no new work.
allemaar/open-skills/skills/plan-create Skill
15★ repoPropose a phased, gated implementation plan before any work begins. Trigger when the user runs /plan-create, says "make a plan", "plan this out", "design before coding", "let's plan first", "architect this", or asks for a phased approach before implementation. Also trigger proactively when a task is complex enough that jumping straight to execution would be risky — multi-file changes, new features, architectural shifts, refactors spanning multiple components, or any task where misalignment early would be expensive to fix later. Output: a structured PLAN.md with phases, changes, risks, and verification criteria. Design only — no implementation code is written during /plan-create. Use plan-phases to restructure an existing plan, plan-execute to run an approved plan, plan-deep-dive to inspect a plan, plan-evolve to evolve shipped work, and plan-cleanup after execution.
allemaar/open-skills/skills/plan-deep-dive Skill
15★ repoPhase-by-phase deep inspection of any multi-phase plan — stop at each phase and assess completeness, quality, and future-readiness before advancing. Trigger when the user runs /deep-dive or asks to "do a deep dive", "inspect each phase", "look at this more carefully", or "check if we're missing anything" on an existing plan. Use plan-create to create a new plan, plan-execute to run an approved plan, and plan-phases to add gates to a plan.
allemaar/open-skills/skills/plan-evolve Skill
15★ repoEvolve a target to its next version — treat what shipped as v1, plan the next iteration. The target can be a plan, a repo, a system, a document, a feature, or a skill. If a v1 plan artifact exists, evolve it; if not, the current state of the target IS v1. Trigger: 'what would v2 look like', 'evolve this', 'what's next for this', 'next iteration of this', 'plan the next version'. Use plan-deep-dive to inspect the current state, plan-execute to run the new plan, and plan-cleanup to remove artifacts after execution.
allemaar/open-skills/skills/plan-execute Skill
15★ repoApply the last approved plan exactly. Trigger when the user runs /execute or says "execute the plan", "implement this", "do it", or "go ahead" after a plan has been approved. Surface judgment calls — do not make them silently. Not /plan-create (designs the plan first) or /plan-deep-dive (inspects a plan without running it) — plan-execute runs an already-approved plan.
allemaar/open-skills/skills/plan-phases Skill
15★ repoRestructure an existing plan into phases with /verify gates after each phase and critical steps. Trigger when the user runs /phase-plan or asks to "add phases to this plan", "gate this plan", "restructure the plan", or "add checkpoints". Use plan-create for new plans and plan-deep-dive for inspection without restructuring.
hellotern/Sextant/skills/plan Skill
15★ repoYou MUST use this skill before starting multi-step implementation work when no ordered task breakdown exists yet. Use when the requirement is confirmed and clear, and you need to answer "how do we build this and in what order" — producing an ordered task list with skill assignments and acceptance criteria. Stronger signals: "plan this", "how should we build this", "break this into tasks", "sprint plan", "what order should we do this in", "create a task list", "what's the implementation sequence". Use sextant:refine-requirements first if the requirement itself is still ambiguous (that skill answers "what"; this skill answers "how and in what order"). Use sextant:add-feature directly when the task is a single, well-scoped unit that needs no sequencing.
hellotern/Sextant/skills/refine-requirements Skill
15★ repoYou MUST use this skill before writing any design or code when the requirement is vague, ambiguous, or too broad. Use when the "what" is unclear — the requirement needs scoping, feasibility assessment, or decomposition before anyone touches code. Stronger signals: "unclear requirements", "break this down", "is this feasible", "help me design", "what do we need to build", vague one-sentence feature requests, open-ended asks like "build me X". Skip this skill and go directly to sextant:add-feature only when the requirement is already concrete, scoped, and unambiguous.
jackchuka/skills/claude-skill-spec-audit Skill
15★ repoAudit skill SKILL.md files for compliance with the agentskills.io specification and house conventions. Checks frontmatter fields (name, description, compatibility, metadata, argument-hint), metadata sub-fields (author, scope, layer, confirms), and layer/suffix consistency. Use when adding new skills, reviewing skill quality, or ensuring all skills follow the spec. Triggers: "audit skills", "check skill spec", "skill compliance", "are my skills up to spec", "/claude-skill-spec-audit".
rengwu/iudex/templates/dot_iudex/skills/to-issues Skill
no license15★ repoBreak a plan, spec, or PRD into independently-grabbable iudex tickets using tracer-bullet vertical slices, and register them in the iudex queue with their dependencies. Use when the user wants to convert a plan into tickets, create implementation tickets, or break down work into the iudex queue.
rengwu/iudex/templates/dot_iudex/skills/to-prd Skill
no license15★ repoTurn the current conversation context into a PRD and write it to .context/prd/ so it can be sliced into iudex tickets. Use when the user wants to create a PRD from the current context.
iblai/api/skills/iblai-api-milestone Skill
15★ repoRead and write an ibl.ai organization's catalog milestones via the platform API — course, resource, program, and pathway completions, plus skill points at block, course, platform, and user level (including bulk and group updates). Use when querying or recording user progress and skill-point totals.
bntvllnt/agent-skills/workflow Skill
15★ repoHigh-velocity solo development workflow. Idea to production same-day. 10 commands: plan, spike, ship, fix, review, spec-review, focus, done, drop, workflow. Auto-activates on: "plan", "spec", "ship", "spike", "fix", "debug", "repair", "spec-review", "review spec", "analyze spec", "challenge spec", "focus", "what should i do", "prioritize", "overwhelmed", "what should i work on", "done", "finish", "complete", "drop", "abandon", "workflow", "what's next", "whats next", "next step", "what now".
cofin/flow/plugins/flow/skills/flow-planning Skill
15★ repoUse when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
The same file is in 1 other repository
cofin/flow/plugins/flow/skills/flow Skill
15★ repoUse when a repository has .agents, when the user asks for Flow lifecycle routing, Beads-backed task memory, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help.
cofin/flow/skills/flow-planning Skill
15★ repoUse when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
The same file is in 1 other repository
cofin/flow/skills/flow Skill
15★ repoUse when a repository has .agents, when the user asks for Flow lifecycle routing, Beads-backed task memory, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help.
v0lka/skills/development/sdd/vibespec-create Skill
15★ repoCreate a new specification document following the project's spec system templates and conventions. Use when adding a new domain, component, contract, architecture doc, or Architecture Decision Record (ADR). Ensures correct format, naming, placement, cross-references, and INDEX.md update.
v0lka/skills/development/sdd/vibespec-init Skill
15★ repoInitialize a specification system for a project from scratch. Analyzes the codebase to identify architectural layers, domains, boundaries, and key decisions, then generates the initial set of specs (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR template). Use when bootstrapping specs for a new project, setting up documentation governance, or creating a spec system for an existing codebase that has none.
v0lka/skills/development/sdd/vibespec-update Skill
15★ repoUpdate existing specification documents after code changes that alter documented behavior, interfaces, or invariants. Use after implementation when you have changed behavior covered by a spec, added/removed/renamed interfaces in a contract, modified architectural boundaries, or changed configuration. Ensures format preservation, cross-reference integrity, and INDEX.md currency.
v0lka/skills/engineering/research-synthesis Skill
15★ repoExecute the synthesis phase of an research project. Analyzes the hypothesis graph, determines report verbosity (simple vs. complex path), generates the final report, creates a prototype inventory, and finalizes the implementation plan in the brief. Use when concluding a research project, writing the final report, or when the research question has been answered or the budget is exhausted.
v0lka/skills/research/explore Skill
15★ repoExplore → Plan → Implement. A thinking partner for exploring ideas, investigating problems, and clarifying requirements, that transitions into a structured roadmap specification (tasks in What/How/Where/Acceptance criteria format) for user approval, then implements the approved plan. Use when the user wants to think through something before a change, when requirements are unclear, or when discussing architecture and design decisions.
DKeken/codex-skills-alternative/skills/creative-positioning Skill
15★ repoConnect business positioning to a concrete visual language. Maps strategic positioning (category, differentiator, who-it's-for, who-it's-against) onto visual decisions — palette, type, imagery, tone — so the look reinforces the strategy. Use when the user says "positioning into visuals", "what should the brand look like given our strategy", "align visuals with positioning", or is moving from strategy to brand expression. Part of the Creative Production set.
DKeken/codex-skills-alternative/skills/design-get-context Skill
15★ repoClarify the brief BEFORE any design work to avoid building the wrong thing. Interrogates goal, user, constraints, success criteria, and scope, then writes a short context doc the other design skills consume. Use when the user says "let's design X", "build a UI for Y", "get context", "clarify the brief", or kicks off any product-design task without a clear spec. First stage of the Product Design set — highest leverage for reducing rework.
XCode-NLP/KodaSkills/skills/koda-plan Skill
15★ repoНавык декомпозирования сложных задач. Помоги пользователю декомпозировать задачу, определить подзадачи, составить план их выполнения и выполнить согласно плана. Используй другие доступные навыки, которые могут помочь в этом.
ivanshamaev/de-agent-skills/group_skills/starrocks_group_skills/starrocks_explain_plan Skill
no license15★ repoStarRocks EXPLAIN plan reading — EXPLAIN/EXPLAIN VERBOSE/EXPLAIN COSTS output structure, operator nodes (OlapScanNode/HashJoinNode/AggregationNode/ExchangeNode/SortNode/ProjectNode), reading fragment instances, identifying bottlenecks (shuffle exchange cost, large scan rows, memory spill), runtime filter nodes, partition pruning in scan, query profile (SHOW PROFILELIST/EXPLAIN ANALYZE)
ivanshamaev/de-agent-skills/group_skills/trino_group_skills/trino_explain_plan_review Skill
no license15★ repoTrino EXPLAIN and EXPLAIN ANALYZE plan reading — DISTRIBUTED/LOGICAL/IO/VALIDATE formats, fragment types (SINGLE/HASH/ROUND_ROBIN/BROADCAST/SOURCE), exchange node analysis, stage bottleneck detection, data skew identification via task row-count variance, spill detection, operator-level metrics (ScanFilterProject/HashJoin/Aggregation/LocalExchange), cost estimate vs actual row disparity, slow plan patterns and fixes
byronxlg/skillfold/library/skills/planning Skill
15★ repoBreak problems into steps, identify dependencies, and estimate scope.
hwl668/Scientific-learning-skills-/skills/study-plan-builder Skill
15★ repo适用于制定学习计划、复习安排、备考路线、自学路径和时间规划。用户问怎么学、多久学完、如何备考、每天学什么、短期补弱、考试冲刺或项目学习路线时使用。根据目标、时间、当前基础,生成现实可执行的学习计划。
alexander-danilenko/cortex-ai-skills/skills/spec-mining Skill
14★ repoApply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
Amey-Thakur/AI-SKILLS/skills/architecture/scalability-planning Skill
14★ repoPlan scalability from a load model and bottleneck math, designing for realistic growth without premature over-engineering. Use when designing for scale or after a load-driven incident.
Amey-Thakur/AI-SKILLS/skills/architecture/technical-vision Skill
14★ repoWrite a north-star architecture document that sequences migrations and guides decisions without pretending to be a roadmap. Use when a team's technical direction is unclear or every design debate restarts from zero.
Amey-Thakur/AI-SKILLS/skills/big-tech-processes/design-doc-google-style Skill
14★ repoWrite a Google-style design doc that argues a decision through context, goals, and rejected alternatives before code is written. Use when a change is large enough that picking the wrong approach is expensive to undo.
Amey-Thakur/AI-SKILLS/skills/big-tech-processes/okr-cascade Skill
14★ repoCascade OKRs so team and individual goals ladder up to company strategy without sandbagged targets or scoring that rewards easy wins. Use when setting quarterly or annual objectives across more than one team and you want alignment, not a spreadsheet of restated tasks.
Amey-Thakur/AI-SKILLS/skills/big-tech-processes/quarterly-planning Skill
14★ repoRun quarterly planning with honest capacity, negotiated cross-team dependencies, and an explicit cut line that names what will not get done. Use when a team commits to a quarter of work and needs the plan to survive contact with reality.
Amey-Thakur/AI-SKILLS/skills/big-tech-processes/rfc-process Skill
14★ repoRun a Request for Comments process so a proposal reaches the right audience, collects objections inside a bounded window, and records a decision people can point to later. Use when a change affects teams beyond the author's and needs durable buy-in.
Amey-Thakur/AI-SKILLS/skills/business-growth/landing-page-strategy Skill
14★ repoBuild landing pages with a clear message hierarchy, credible proof, and one decisive call to action, tested where it matters. Use when creating or fixing pages that must convert visitors.
Amey-Thakur/AI-SKILLS/skills/data-science/leaderboard-strategy Skill
14★ repoTrust your cross-validation over the public leaderboard, avoid overfitting it, and select final submissions wisely. Use in the endgame of a Kaggle competition, where rank is won or lost by validation discipline.
Amey-Thakur/AI-SKILLS/skills/databases/indexing-strategy Skill
14★ repoDesign indexes from query patterns with correct column order, covering indexes, and write-cost awareness. Use when queries are slow or a table has too many or too few indexes.
Amey-Thakur/AI-SKILLS/skills/databases/query-plan-reading Skill
14★ repoRead EXPLAIN ANALYZE output to find the real cause of a slow query and fix the right thing. Use when a query is slow and you need to know why before changing indexes or SQL.
Amey-Thakur/AI-SKILLS/skills/devops/capacity-planning Skill
14★ repoForecast load, size headroom, discover scaling limits before they bite, and track cost curves. Use when planning capacity for growth or a known traffic event, or after a saturation incident.
Amey-Thakur/AI-SKILLS/skills/devops/rollback-strategy Skill
14★ repoDecide rollback versus fix-forward, handle migrations safely, and rehearse rollbacks so they work under pressure. Use when planning deploy safety or during an incident deciding how to recover.
Amey-Thakur/AI-SKILLS/skills/git-collaboration/branch-strategy Skill
14★ repoChoose a branching model, default to trunk-based with short-lived branches, and set protection rules. Use when establishing team git workflow or fixing long-lived-branch merge pain.
Amey-Thakur/AI-SKILLS/skills/gpu-ai-infrastructure/gpu-cost-planning Skill
14★ repoPlan GPU spend by comparing owned hardware, reserved cloud, and on-demand against real utilization and lead time, so you commit at the right break-even. Use when deciding whether to buy GPUs, reserve cloud capacity, or burst on-demand for a workload.
Amey-Thakur/AI-SKILLS/skills/mobile/mobile-release-strategy Skill
14★ repoShip mobile releases through phased rollouts with hotfix paths and a forced-upgrade policy that never strands users. Use when planning app releases, a rollout gate, or recovery from a bad build in the stores.
Amey-Thakur/AI-SKILLS/skills/performance/caching-strategy Skill
14★ repoDecide what to cache and where by choosing layers, key shapes, and TTLs against the read pattern and freshness need. Use when reads are hot and repeated and you are deciding whether and where to add a cache before writing invalidation code.
Amey-Thakur/AI-SKILLS/skills/performance/cdn-strategy Skill
14★ repoPush work to the edge so requests never touch your origin, using cache headers, invalidation, and origin shielding. Use when origin load is high, global latency is uneven, or a CDN sits in front of your app but barely caches.
Amey-Thakur/AI-SKILLS/skills/product-management/mvp-scoping Skill
14★ repoScope minimum viable products around the riskiest assumption, cut to learn fast, and hold an explicit quality floor. Use when defining a first version or rescuing an MVP that grew into a v3.
Amey-Thakur/AI-SKILLS/skills/product-management/prioritization-frameworks Skill
14★ repoPrioritize with RICE-class scoring applied honestly, cost of delay, and refusals that carry reasons. Use when ordering a roadmap or defending priority calls under stakeholder pressure.
Amey-Thakur/AI-SKILLS/skills/product-management/roadmap-communication Skill
14★ repoCommunicate roadmaps with now/next/later horizons, honest commitment levels, and audience-shaped views. Use when publishing product direction or managing the fallout of roadmap changes.