Plan & spec
10,699 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
mikulgohil/claude-skills/skills/personal/proposal-writer Skill
0★ repoDraft client proposals, quotes, scopes of work, and engagement letters for service work — project understanding, scope, timeline, pricing presentation, and terms. Use when writing any B2B service engagement document.
mikulgohil/claude-skills/skills/personal/task-prioritization Skill
0★ repoBacklog prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity-cost scoring. Use when ranking features, comparing initiatives, or justifying roadmap order.
lensetek/Research-Agent-Skills-Collection/skills/research_design_planner Skill
no license0★ repoMerancang desain penelitian terperinci, termasuk pendekatan metodologi (kuantitatif, kualitatif, mixed-method, eksperimental), variabel, pengumpulan data, dan rencana analisis.
sebastian-software/skills.sebastian-software.com/skills/product-design Skill
0★ repoPlan, research, model, explore, prototype, and review digital product experiences. Use when turning product evidence or a provisional brief into a design brief; planning or synthesizing behavioral research to shape how the experience works; documenting a problem space, user expectations, or mental models; framing design opportunities; modeling objects, actions, relationships, journeys, and moments; creating information architecture, flows, wireframes, or prototype plans; designing or reviewing habit loops, triggers, rewards, investment, gamification, engagement, retention, or sticky experiences; or deciding how autonomy, learnability, fidelity, and visual character should shape an experience. Use for product and interaction design before or alongside implementation, especially when research, behavioral design, systems thinking, and interface craft must remain connected.
sebastian-software/skills.sebastian-software.com/skills/product-management Skill
0★ repoPlan, review, and improve evidence-led product decisions for software and digital products. Use for product discovery and research to decide what or whether to build, product briefs and evidence audits, customer problems and Jobs to be Done, product strategy, outcomes, MVP or initial scope, product operating models and empowered teams, continuous discovery and delivery, AI-assisted idea exploration, prioritization, roadmaps, feature requests, quality bars, product delight, release decisions, product experiments, adoption and retention learning, or transitions from consulting and services to repeatable products. Use when deciding what to build, why, for whom, how the team should explore it, or whether a product artifact or product is ready to act on, especially when product, design, engineering, and go-to-market evidence must stay aligned.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/extract-state-type Skill
no license0★ repoRead-only EXPLAIN skill that converts a function operating on an implicit mutable dict (or ad-hoc kwargs/namespace) into a typed @dataclass or TypedDict migration plan. Produces reports/extract-state-type/<target>/proposal.md with the current-shape table, proposed type definition, caller-by-caller migration plan, characterization-test matrix, and stop condition. Hands off to /fix-workflow or manual migration.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/impact-feature Skill
no license0★ repoSecond skill in the System-tier chain. Reads a `scoped`-status plan, fans out one scout per touched subsystem to map call sites + behaviors-to-preserve, synthesizes the cross-subsystem impact + blast radius, and fills §3-4 of the plan. Advances plan status to `impacted`. Heavier than /scope-feature (scout fan-out) but lighter than /plan-feature (no spec scaffold; that's /plan-spec).
KhurrumMahmood/senior-vibe-engineer/.claude/skills/organize-project-structure Skill
no license0★ repoArrive at an ideal or near-ideal repo folder structure and organization approach under framework/tool/human constraints. Use when a project has historical top-level folders, source/input/output dumps, KB/spec/eval/runtime boundaries, or a proposed directory map that needs recursive folder summaries, ideal-vs-constrained topology review, boundary discovery, folder-worth judgment, deterministic move-plan options, dry-run validation, and a safe implementation approach. Not for one-off file moves or Python package prefix clusters.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/plan-feature Skill
no license0★ repoPlan a Feature-tier change (1-3 day scope, touches one workflow, needs impact analysis but not new subsystem). Reads subsystem/workflow docs, canonical patterns, architectural smells, and the decision registry; fans out scouts per touched subsystem to map call sites, model touchpoints, and behaviors-to-preserve; surfaces decision stubs for material forks; and scaffolds a proposed-lifecycle spec under `ai-docs/specs/<feature-name>.md` so implementation work can resume from the spec.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/plan-skill Skill
no license0★ repoPlan and harden a new or revised skill before implementation, including adversarial requirements pushback, trigger design, evidence contracts, dogfood cases, and review gates. Use when creating a new .claude/skills skill or materially changing an existing skill.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/plan-spec Skill
no license0★ repoFinal skill in the System-tier chain. Reads an `architected`-status plan, validates that §6 has no unresolved P0 forks, then calls `scripts/plans.py promote` to scaffold a successor spec under `ai-docs/specs/<spec-id>.md` and mark the plan `promoted`. The plan's §3-5 inform the spec's Architecture / Implementation / Exceptions sections. Hands off to `/refactor-subsystem` for execution.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/propose-boundary Skill
no license0★ repoTurn a confirmed or suspected missing-boundary into a read-only boundary-extraction proposal. Family-local evidence supports Python, TypeScript/checked-JavaScript, Go, Java 17, Kotlin/JVM, C#, Swift 6.3.3, PHP, Ruby, bounded Rust, and bounded Dart. It emits reports/propose-boundary/<target-slug>/proposal.md with candidate seams, public API, compatibility plan, caller impact, and characterization/native-verification plan. Read-only — no edits. Hands off to /refactor-subsystem (decomposition mode).
KhurrumMahmood/senior-vibe-engineer/.claude/skills/propose-folder-reorganization Skill
no license0★ repoTurn a confirmed Python, Go, Java 17, Kotlin/JVM, C#, Swift 6.3.3, TypeScript, checked-JavaScript, PHP, Ruby, bounded Rust, or bounded Dart folder-topology cluster into a per-cluster reorganization proposal. Typed-source v1 resolves import impact, records compatibility and convention constraints, and emits a read-only move/test plan. No file moves or edits; hand off only after human review.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/refactor-subsystem Skill
no license0★ repoExecute a large-subsystem refactor (split a bloated module, extract a service, reorganize a domain) using an orchestrator/scout pattern driven by a spec file in `ai-docs/specs/`. Operates in seven phases — Inventory, Characterize+Extract, Plan, Approve, Execute, Verify, Crystallize — with mandatory three-output scouts (primary brief + findings.md + extracted-behaviors.md), spec-first enforcement via `scripts/specs.py`, ledger updates via `scripts/ledger.py`, and a conservative default that unknown code STAYS until explicit human approval. Refactors are behavior-preserving; bug fixes surfaced along the way become separate commits.
KhurrumMahmood/senior-vibe-engineer/.claude/skills/scope-feature Skill
no license0★ repoFirst skill in the System-tier chain. Scaffolds an `ai-docs/plans/<name>.md` plan if needed, reads decisions / canonical-patterns / smells, then drives clarifying questions to fill §1 (Scope & Bounds) and §2 (Success Criteria) of the plan. Advances plan status to `scoped`. Designed for System-tier work — new subsystems, cross-subsystem features, multi-week initiatives — where the judgment pause between scoping and impact analysis is the whole point.
Hayatelin/founder-skills/skills/mvp-spec Skill
0★ repoTurns a raw idea into a lean MVP spec: problem, goals/non-goals, core user flow, scope cut, and a single success metric. Trigger on "scope my MVP", "what should I build first", "MVP spec", "cut this to an MVP", or "turn my idea into a build plan".
Hayatelin/founder-skills/skills/pricing-strategy Skill
0★ repoChooses a pricing model (per-seat, usage, outcome-based, or hybrid), sets tiers, and sanity-checks unit economics. Trigger on "how should I price", "help me price my SaaS", "pricing tiers", "what should I charge", "outcome-based pricing", or "are my unit economics okay".
markstent/muster/skills/spec Skill
0★ repo(Muster) Turn the agreed idea into a written spec and a set of small, buildable tasks - saved as one file you can edit - then create the GitHub issues once you say go. Run after /think, or straight away if the idea is already clear. Won't re-interview you.
markstent/muster/skills/think Skill
0★ repo(Muster) Talk through your idea, one question at a time, until every open question is settled - so the plan is solid before any code gets written. Use when you say "I want to build X", "I have an idea", or want to pressure-test a plan. Writes nothing. Ends by pointing you to /spec.
vindreshsingh/engineering-skills/skills/caching-strategy Skill
0★ repoAdds caching that speeds reads without serving stale or wrong data. Use when a read is expensive and repeated, when adding or tuning a cache layer, or when debugging stale-data and invalidation bugs.
vindreshsingh/engineering-skills/skills/long-running-agents Skill
0★ repoKeeps an agent (or a planner/worker/judge fleet) coherent across hours or days and thousands of model calls — using external plan and progress files, checkpoint-and-resume, and context compaction so the run survives context limits, crashes, and drift. Use when a task is too big for one context window or must run unattended over a long horizon.
vindreshsingh/engineering-skills/skills/marketing/growth-strategy Skill
0★ repoBuilds a go-to-market plan for a product — positioning, ICP, channel mix, messaging, and campaign calendar. Use when launching a product, planning marketing, choosing channels, or aligning the growth team on what to say and where.
vindreshsingh/engineering-skills/skills/product-brief Skill
0★ repoWrites a product brief / PRD or technical RFC that aligns stakeholders before building. Use when a feature needs sign-off across teams, a significant technical approach needs review, or you need a durable record of what and why (or how) before commitment.
vindreshsingh/engineering-skills/skills/product-discovery Skill
0★ repoTurns a raw idea into a decision-ready discovery package — validated problem, PRD with scope and success metrics, RFC handoff, and an ordered task breakdown — by running the PM persona trio (business-analyst, product-manager, product-analyst) through the Define and Plan phases. Use at the front of a feature when you have a one-line idea and need a buildable, measurable plan before any code.
vindreshsingh/engineering-skills/skills/spec-first Skill
0★ repoWrites a short, testable specification before implementation. Use when starting a new project, feature, or non-trivial change, when requirements are vague or ambiguous, or before estimating, planning, or handing work to others.
vindreshsingh/engineering-skills/skills/work-planning Skill
0★ repoBreaks a spec or goal into an ordered, verifiable plan before building. Use when work spans multiple steps or files, when collaboration or handoff is needed, or when you need a credible estimate and visible progress.
hillzeealex/skills/deprecated/request-refactor-plan Skill
no license0★ repoCreate 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
hillzeealex/skills/engineering/to-issues Skill
no license0★ repoBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
The same file is in 3 other repositories
hillzeealex/skills/engineering/to-prd Skill
no license0★ repoTurn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
The same file is in 6 other repositories
0xgetz/xi-agent-skills/trading-skills/scalping-strategy Skill
no license0★ repoAnalyze markets using Scalping Strategy (scalping). Capture small frequent moves with tight risk control. Activate when the user asks to analyze, interpret, or build signals based on Scalping Strategy or scalping.
tcf-jw/plan-with-loops/skills/plan-with-loops Skill
0★ repoPlan a task like Plan mode, then design the agent loop that executes it. Produces a read-only 4-part design doc: (1) standard step plan, (2) agent roster, (3) loop topology, (4) implementation plan wired to the Claude Code Workflow tool + subagents. Loop complexity scales with effort level (low/medium/high). Decides the roster and loop autonomously, then presents for approval. Writes no files. Use when the user wants to plan multi-agent, looped, or orchestrated work, asks to "design an agent loop", "plan with loops", "orchestrate this", or invokes /plan-with-loops.
dbmrq/agent-skills/skills/ralph-loop-plan Skill
no license0★ repoWrite Markdown implementation plans and checklists optimized for Ralph loops — one checkbox per agent run, autonomous ordering, integration tasks, verification criteria, and human-only gates at the end. Use when the user wants a Ralph loop plan, autonomous agent todo list, or says "use a ralph loop to build/create X" and needs the plan before running the loop.
Yco-0314/strata/skills/l2-planning/to-issues Skill
0★ repoBreak a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Yco-0314/strata/skills/l2-planning/to-prd Skill
0★ repoTurn the current conversation into a PRD and publish it to the project issue tracker — synthesis of what you've already discussed, not a fresh interview.
Yco-0314/strata/skills/l2-planning/writing-plans Skill
0★ repoUse to author a heavyweight, junior-engineer-proof implementation plan for LARGE multi-session work — exact file paths, complete code, and 2-5 minute TDD steps. The opt-in heavy path; for routine work prefer to-issues. Trigger phrases include "write a detailed plan", "full implementation plan", "spec this out before coding".
Yco-0314/strata/skills/l3-execution/subagent-driven-development Skill
0★ repoExecute an implementation plan or set of issues by dispatching a fresh subagent per task, with two-stage review (spec compliance, then code quality) after each.
juff17/docify/skills/ticket-write Skill
0★ repoCreate and update engineering tickets — a user story, then requirements, then acceptance criteria, written for the engineer who'll build it. Use when the user wants to write, create, or file a ticket, or to update or edit an existing one.
juff17/docify/skills/trd-write Skill
0★ repoCreate and update a Technical Requirements Document (TRD) — the epic-level technical plan for how a PRD gets built: an overview of why, then the implementation broken into stages. Use when the user wants to write a TRD, plan out an epic, spec a feature technically, turn a PRD into a technical plan, or update an existing TRD.
cipradu/Agent-Workbench/skills/create-engineering-spec Skill
0★ repoUse when a rough feature, bug report, compliance request, operational/domain/product note, or existing-system change must become an engineering-facing spec before planning, implementation, migration, or review
cipradu/Agent-Workbench/skills/create-implementation-pattern Skill
0★ repoUse when creating, revising, validating, or deciding whether to create a reusable implementation pattern from repeated project code, review findings, ADR/spec/plan decisions, or post-implementation pattern-capture signals.
cipradu/Agent-Workbench/skills/create-implementation-plan Skill
0★ repoUse when an approved engineering spec must become a deeply researched, dependency-ordered implementation plan before a human engineer or coding agent changes code
cipradu/Agent-Workbench/skills/create-project-prd Skill
0★ repoUse only when the user explicitly asks to create, draft, revise, or validate a PRD for a project, product, or feature before engineering specification or implementation planning.
cipradu/Agent-Workbench/skills/create-spec-readiness-map Skill
0★ repoUse when an existing PRD, product brief, or requirements artifact is too broad or uncertain to become an engineering spec without first resolving multiple spec-readiness questions or one broad spec-readiness blocker across sessions.
cipradu/Agent-Workbench/skills/testing-strategy Skill
0★ repoUse when designing, writing, reviewing, or planning software tests, test coverage, regression tests, characterization tests, integration/contract/E2E tests, mocks, fixtures, flaky-test fixes, or verification evidence.
cipradu/Agent-Workbench/skills/visual-artifact Skill
0★ repoUse when a user asks for an evidence-backed visual artifact, HTML explainer, diagram, unknowns map, dependency map, decision map, implementation-plan visualization, review explainer, or comprehension report for an existing PRD, spec-readiness map, engineering spec, implementation plan, review packet, implementation result, or complex technical artifact.
ffidelis16/GEO-OS/skills/content-brief Skill
0★ repoUse quando uma intenção priorizada precisa virar um brief editorial executável, com audiência, estágio de decisão, entidades, relações, claims, evidências, citation opportunities, answer blocks, frescor, links, riscos e estrutura.
ffidelis16/GEO-OS/skills/rewrite-plan Skill
0★ repoUse quando gaps de scorecard, extraibilidade, confiança, planejamento, concorrência ou evidência precisam ser convertidos em um plano de reescrita por seção antes da produção editorial final.
udsy19/.claude/skills/interview-me Skill
no license0★ repoExtracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
The same file is in 130 other repositories
udsy19/.claude/skills/planning-and-task-breakdown Skill
no license0★ repoBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
The same file is in 9 other repositories
udsy19/.claude/skills/spec-driven-development Skill
no license0★ repoCreates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
The same file is in 80 other repositories
mustafa3252/vibe-loop-engineering/skills/loop-brief Skill
0★ repoTurn a vague automation idea into a safe, bounded loop brief.
ch040602/skill-vaccine/tests/fixtures/benchmark_expansion/benign_test_plan Skill
no license0★ repoHelps maintainers transform user-selected local project text into safer review artifacts.
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/ceo-advisor Skill
0★ repoExecutive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
The same file is in 2 other repositories
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/contract-and-proposal-writer Skill
0★ repoGenerate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material.
The same file is in 3 other repositories
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/cpo-advisor Skill
0★ repoProduct leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.
The same file is in 2 other repositories
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/cs-product-strategist Skill
0★ repoProduct strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation. Use when the question is direction rather than delivery — e.g., cascading company OKRs into product-team objectives for next quarter, or running a competitive teardown to decide whether to enter an adjacent market.
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/marketing-strategy-pmm Skill
0★ repoProduct marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
The same file is in 5 other repositories
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/odoo-backup-strategy Skill
0★ repoComplete Odoo backup and restore strategy: database dumps, filestore backup, automated scheduling, cloud storage upload, and tested restore procedures.
The same file is in 6 other repositories
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/okr Skill
0★ repoGenerate OKR cascades from company strategy to team objectives. Usage: /okr generate <strategy>
srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/product-strategist Skill
0★ repoStrategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level.
The same file is in 4 other repositories