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
The-AI-Directory-Company/agents-and-skills/skills/social-media-content-plan Skill
2★ repoCreate social media content calendars with post templates, platform-specific formatting, hashtag strategies, and engagement schedules tailored to each network's algorithm and audience behavior.
The-AI-Directory-Company/agents-and-skills/skills/sprint-planning-guide Skill
2★ repoRun effective sprint planning sessions — from backlog refinement through capacity allocation, commitment, and sprint goal definition with clear acceptance criteria.
The-AI-Directory-Company/agents-and-skills/skills/stakeholder-interview Skill
2★ repoDesign and conduct stakeholder interviews for requirements elicitation — with structured question frameworks, active listening techniques, assumption surfacing, and synthesis into actionable requirements.
The-AI-Directory-Company/agents-and-skills/skills/technical-spec-writing Skill
2★ repoWrite technical specifications that bridge product requirements and implementation — with problem statements, proposed solutions, data model changes, API changes, migration plans, rollback strategies, and open questions.
The-AI-Directory-Company/agents-and-skills/skills/test-plan-writing Skill
2★ repoWrite risk-based test plans with coverage matrices, test level decisions, pass/fail criteria, and environment requirements — deciding what to test, at which level, and why.
The-AI-Directory-Company/agents-and-skills/skills/user-story-mapping Skill
2★ repoCreate user story maps that break down complex features into shippable slices with clear user journeys, activities, tasks, and release planning.
kevinaimonster/skill-hub/skills/api-doc Skill
no license2★ repoAPI 文档助手。帮用户写 OpenAPI/Swagger 文档、接口说明、请求示例、错误码定义。当用户说「帮我写 API 文档」「Swagger 文档」「OpenAPI」「接口文档」「API 说明」「写个接口文档」「RESTful API 文档」「接口定义」「API spec」「api documentation」「swagger spec」时触发。关键词:API文档、OpenAPI、Swagger、接口文档、RESTful、请求示例、响应格式、错误码、API设计、接口定义、YAML、JSON Schema、端点、认证、鉴权、版本管理、api doc、api specification、endpoint、request、response、HTTP method、status code
kevinaimonster/skill-hub/skills/biz-plan Skill
no license2★ repo商业计划书撰写助手。帮用户撰写专业的商业计划书、BP、创业方案。当用户说「帮我写商业计划书」「写个BP」「创业计划」「融资方案」「商业模式」「商业计划」「business plan」「创业项目书」「投资计划书」「项目可行性报告」「盈利模式」时触发。关键词:商业计划书、BP、创业计划、融资方案、商业模式、可行性分析、市场分析、财务预测、竞争分析、目标市场、客户画像、营收模型、成本结构、盈利模式、投资回报、ROI、TAM、SAM、SOM、商业画布、价值主张、渠道策略、business plan、pitch、startup plan、revenue model
kevinaimonster/skill-hub/skills/budget-planner Skill
no license2★ repo预算规划助手。帮用户做个人记账、家庭预算、项目预算、财务规划。当用户说「帮我做预算」「记账」「家庭预算」「月度预算」「财务规划」「怎么省钱」「预算表」「项目预算」「花销分析」「理财规划」「budget plan」「financial plan」「月光族」「存钱」「开支」时触发。关键词:预算、记账、财务规划、家庭预算、个人理财、月度预算、年度预算、项目预算、开支分析、花销、省钱、存钱、理财、收支、financial planning、budget、expense、saving、投资、基金、应急金、债务、信用卡、房贷、消费分析、开销、账单、50-30-20法则、紧急储备金、财务自由
kevinaimonster/skill-hub/skills/fitness-plan Skill
no license2★ repo健身计划助手。帮用户制定健身计划、饮食方案、训练动作指导、身材管理。当用户说「帮我制定健身计划」「减肥计划」「增肌计划」「训练方案」「饮食计划」「健身动作」「怎么练胸」「怎么减脂」「健身入门」「workout plan」「fitness plan」「meal plan」「怎么练」「gym routine」时触发。关键词:健身、健身计划、减脂、增肌、训练、力量训练、有氧运动、HIIT、饮食、蛋白质、碳水、热量、卡路里、体脂、BMI、胸肌、背肌、腿部、核心、拉伸、恢复、分化训练、全身训练、家庭训练、gym、workout、fitness、muscle、diet、protein、cardio
kevinaimonster/skill-hub/skills/okr-coach Skill
no license2★ repoOKR教练。帮用户制定OKR、拆解目标、做绩效复盘、季度回顾。当用户说「帮我写OKR」「OKR怎么定」「目标拆解」「KPI怎么设」「绩效复盘」「季度目标」「年度目标」「帮我定目标」「OKR模板」「绩效考核」「目标管理」「set OKR」「quarterly goals」时触发。关键词:OKR、目标管理、关键结果、KPI、绩效、绩效复盘、目标拆解、季度目标、年度目标、SMART目标、绩效考核、360评估、自评、他评、目标对齐、对齐上级OKR、关键行动、进度追踪、objectives、key results、goal setting、performance review、北极星指标、飞轮、战略拆解、团队OKR、个人OKR、公司OKR
kevinaimonster/skill-hub/skills/prd-writer Skill
no license2★ repo产品需求文档(PRD)撰写助手。帮产品经理写PRD、需求分析、用户故事、功能规格说明。当用户说「帮我写PRD」「写个需求文档」「产品需求文档」「功能需求」「用户故事」「需求分析」「写个功能说明」「PRD模板」「product requirements」「user story」「feature spec」「需求评审」「产品设计文档」时触发。关键词:PRD、产品需求文档、需求分析、用户故事、功能规格、feature spec、user story、acceptance criteria、验收标准、产品设计、需求评审、MRD、BRD、功能清单、优先级排序、MVP、信息架构、交互流程、异常流程、边界条件、product requirements document、backlog、epic、sprint、敏捷开发、产品规划
kevinaimonster/skill-hub/skills/project-planner Skill
no license2★ repo技术项目规划助手。帮用户做技术项目拆解、里程碑规划和排期。当用户说「帮我规划项目」「项目拆解」「技术方案」「排个期」「怎么做这个项目」「项目计划」「project plan」「技术选型」「milestone」「sprint planning」「需求分析」「项目规划」「功能拆分」「开发计划」时触发。关键词:项目规划、项目拆解、排期、里程碑、技术选型、需求分析、项目计划、sprint、迭代、开发计划、功能拆分、模块设计、project plan、roadmap、milestone、估时、工时
kevinaimonster/skill-hub/skills/travel-planner Skill
no license2★ repo旅行规划助手。帮用户做旅行攻略、行程规划、预算估算。当用户说「帮我做旅行攻略」「旅行规划」「行程安排」「旅游推荐」「去哪玩」「出行计划」「旅行预算」「自由行攻略」「跟团还是自由行」「签证」「机票」「酒店推荐」「travel plan」「itinerary」时触发。关键词:旅行、旅游、攻略、行程、规划、plan、itinerary、自由行、跟团、签证、机票、酒店、民宿、景点、美食、交通、预算、穷游、亲子游、蜜月、毕业旅行、自驾游、国内游、出境游、日本旅行、泰国旅行、欧洲旅行、东南亚、特种兵旅游
xmqywx/claude-code-skills/skills/freelance-proposal-writer Skill
no license2★ repoGenerate personalized Upwork/freelance proposals from job postings. Paste a job description, and get a tailored cover letter that highlights relevant experience, addresses client pain points, and includes a concrete action plan. Optimized for high response rates.
sidtheone/tarot-skills/high-priestess Skill
no license2★ repoThe High Priestess II — The Reader. Reads between the lines to surface what's unsaid, implied, assumed, or deliberately omitted. Breaks the LLM default of context blindness — working with the literal text without inferring what's missing, what's implied by structure or omission, or what the gaps between the lines reveal. Use this skill when a spec feels incomplete, when a conversation has subtext, when requirements have gaps, or when what's NOT said matters as much as what is. Trigger on: 'priestess this', 'read between the lines', 'what's missing', 'what aren't they saying', 'gap analysis', 'read the subtext', or when a document feels too clean, too brief, or suspiciously absent on certain topics.
ks6088ts-labs/skills/skills/prd-creator Skill
2★ repoプロダクト要求仕様書(PRD)を作成するスキル。ユーザーがプロダクトの要件を明確にし、チームメンバー間の認識を統一するためのPRDドキュメントを作成する必要がある場合に使用します。このスキルは、Product Requirements Document の作成、編集、または既存プロダクトの要求仕様書の更新が必要な場合に使用してください。
coreline-ai/antigravity_gemini_skills/.agent/skills/spec_analyst Skill
2★ repoGemini/Antigravity 기반 에이전틱 DevOps·SDLC 오케스트레이션 스킬 시스템 | Gemini/Antigravity skill system for agentic DevOps and SDLC orchestration
jtsang4/efficient-coding/skills/plan-coaching Skill
2★ repo规划教练。通过访谈引导用户形成能被批准和推行的规划材料,或对已有规划稿做评审与拷问。当用户要写规划、Roadmap、立项或方向提案,或要求 review 规划文档时使用。
jtsang4/efficient-coding/skills/plan-me Skill
2★ repo通过访谈从零梳理一份规划材料。
jtsang4/efficient-coding/skills/plan-review Skill
2★ repo评审并拷问已有的规划稿。
jtsang4/efficient-coding/skills/shape Skill
2★ repoProduct thinking tool that helps shape vague ideas into clear, structured design decisions before and during development. Use this skill whenever the user invokes /shape, or asks to "think through" a product idea, "plan out" what to build, "define requirements", "spec out" a feature, "shape" an idea, or wants help deciding what to build before writing code. Also trigger when users say things like "I want to build X but haven't figured out the details", "help me think through this", "what should I consider before building", or "let me scope this out". This skill is about product-level thinking (what to build and why), not implementation planning (how to build it) — the latter is handled by plan mode.
ClarentCinematics/Codex-Skills-for-Enterprise/skills/pr-review-brief Skill
2★ repoTurn pull request descriptions, diffs, changed files, review comments, or merge requests into reviewer-ready briefs with change summary, risk areas, missing tests, review focus, blockers, and suggested comments. Use when Codex needs to prepare, accelerate, or improve code review across PR platforms.
ClarentCinematics/Codex-Skills-for-Enterprise/skills/project-status-brief Skill
2★ repoStandardize project updates into concise status briefs with health, milestones, blockers, risks, owner actions, and escalation needs. Use when Codex needs to synthesize project notes, stakeholder updates, sprint summaries, launch plans, or program status into a leadership-ready brief.
ClarentCinematics/Codex-Skills-for-Enterprise/skills/proposal-drafting-assistant Skill
2★ repoDraft tailored enterprise proposals from customer needs, discovery notes, constraints, product or service capabilities, proof points, commercial context, and implementation assumptions. Use when Codex needs to create a proposal, statement of work draft, solution narrative, scope summary, or next-step document for a revenue workflow.
Requirements to acceptance criteria
ClarentCinematics/Codex-Skills-for-Enterprise/skills/requirements-to-acceptance-criteria Skill
2★ repoConvert product requirements, feature notes, customer asks, PRD drafts, issue descriptions, or rough specifications into acceptance criteria, test scenarios, dependencies, launch constraints, owners, and open questions. Use when Codex needs to make requirements implementation-ready without inventing scope, owners, or commitments.
ClarentCinematics/Codex-Skills-for-Enterprise/skills/research-synthesis-brief Skill
2★ repoSynthesize multiple sources, reports, notes, articles, datasets, interviews, or research excerpts into claims, evidence, caveats, contradictions, confidence levels, and recommended actions. Use when Codex needs to create source-grounded research briefs, executive summaries, evidence reviews, or decision support.
qiuy-collab/AutoFlow.skill/integrations/agent-skills/interview-me Skill
2★ 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 8 other repositories
qiuy-collab/AutoFlow.skill/integrations/agent-skills/planning-and-task-breakdown Skill
2★ 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 4 other repositories
qiuy-collab/AutoFlow.skill/integrations/engineering-quality/spec-driven-development Skill
2★ 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 3 other repositories
ralfyishere/rules-with-receipts/.claude/skills/deep-decomposition Skill
2★ repoBreak hard tasks into smaller solvable units with explicit dependencies and unknowns. Activate when a task feels too big to plan in one pass — large features, migrations, research questions with many sub-questions, multi-part documents, business analyses, gnarly debugging with several possible fault lines, or anything where the honest answer to "what's step 4?" is "no idea yet". Trigger signals: the user asks for something "end to end", "the whole thing", a system rather than a change, or you notice your plan has steps like "figure out the rest".
ralfyishere/rules-with-receipts/.claude/skills/failure-mode-awareness Skill
2★ repoIdentify what could go wrong before it goes wrong. Activate when designing anything new, before committing to a plan or recommendation, before shipping changes with real blast radius, and when evaluating ideas, strategies, or proposals. Trigger signals: "will this work?", "review this plan", "any risks?", designing an integration or workflow, writing a strategy or proposal, or a plan that contains zero mention of what could fail. Complements adversarial-verify, which attacks finished work; this skill runs earlier, on designs and plans.
ralfyishere/rules-with-receipts/.claude/skills/foresight Skill
2★ repoProject the trajectory before committing - pre-register dated, credenced predictions about what breaks, what becomes necessary, and what pays off 5/10/20 steps ahead, then resolve them when the future arrives and score your calibration. Activate when starting any build, plan, or strategy; making architecture, roadmap, scaling, or investment bets; choosing between directions; or shipping something whose problems will surface later. Trigger signals: "will this scale", "what will we regret", "where does this break at 10x", "what will we need by then", a plan whose risk section only covers the present, or a direction justified only by today's constraints.
ralfyishere/rules-with-receipts/.claude/skills/frontier-workflow-mode Skill
2★ repoThe high-rigor operating mode that orchestrates the full skill pack in order for complex, high-stakes, ambiguous, multi-step, strategic, technical, or quality-sensitive work. Activate when a task is important enough that a rushed answer would be a disservice - major features, migrations, hard bugs, strategy documents, consequential decisions, anything the user marks as important, production-touching, or customer-facing. Trigger phrases: "this is important", "be thorough", "production", "get this right", or any task that effort-calibration would rate High or Critical.
ralfyishere/rules-with-receipts/.claude/skills/plan-gate Skill
2★ repoRequire a written plan before starting complex or multi-step work. Activate when the task involves building a feature, implementing something new, refactoring, migrating, restructuring a document, multi-file edits, research projects, or any work with more than ~3 dependent steps, unclear requirements, or an expensive wrong start. Trigger phrases include "build", "implement", "create", "migrate", "redesign", "set up", "overhaul". Do NOT activate for single-step edits, factual questions, or quick lookups.
ralfyishere/rules-with-receipts/.claude/skills/product-thinking Skill
2★ repoReason from user problems and evidence of demand, not from features - for build/don't-build decisions, prioritization, MVP scoping, and interpreting feature requests and user feedback. Activate on "should we build", "users are asking for", "what should we prioritize", "scope the MVP", roadmap questions, and any feature request about to be taken literally. Trigger signal: a solution being evaluated before the problem it solves has been stated.
ralfyishere/rules-with-receipts/.claude/skills/structured-reasoning Skill
2★ repoPick and apply the right reasoning framework for the problem - first principles, tradeoff analysis, decision matrix, root-cause analysis, steelman, evidence grading, risk/reward, sequencing. Activate for decisions between options, evaluations of ideas or arguments, strategy questions, prioritization, "should we X or Y", "is this a good idea", recurring problems, and any analysis where unstructured pro/con listing would produce mush. Also activate when reasoning feels stuck or circular - the fix is usually a better frame.
subhansh-dev/agent-maxxing/system-prompts/03-reasoning-planning Skill
2★ repoThinking, planning, and decision-making patterns extracted from Codex Plan Mode, Claude Code, and Gemini CLI.
rakibulism/agent-skills-os/skills/campaign-planner Skill
2★ repoBuilds a full marketing campaign brief — objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign.
rakibulism/agent-skills-os/skills/design-engineer Skill
2★ repoThe core orchestrator skill for elite design engineering — building award-tier interactive web experiences that fuse designer-level visual taste with GPU-level computational performance (120 FPS). Use this skill whenever the user asks to build, review, plan, or teach anything involving creative web development, interactive websites, WebGL/Three.js, animation-heavy UI, motion design in code, Awwwards-style sites, 3D hero sections, physics-based interactions, shader effects, or mentions "design engineer", "creative developer", or "cyborg design engineer". Also trigger when reviewing frontend code for visual quality AND performance simultaneously, or planning a training roadmap for a developer learning these skills. The full 9-track curriculum (rail-by-rail depth on taste, sketching, 3D/GPU math, physics, browser internals, architecture, performance, deployment, and the animation-library stack) lives in references/ — load the specific rail file(s) the task touches.
rakibulism/agent-skills-os/skills/engineering-testing-strategy Skill
2★ repoDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
The same file is in 51 other repositories
rakibulism/agent-skills-os/skills/event-planning Skill
2★ repoHelp plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and budgets.
rakibulism/agent-skills-os/skills/marketing-campaign-plan Skill
2★ repoGenerate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
The same file is in 2 other repositories
rakibulism/agent-skills-os/skills/marketing-competitive-brief Skill
2★ repoResearch competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.
The same file is in 2 other repositories
rakibulism/agent-skills-os/skills/seo-cluster Skill
2★ repoSERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/seo-content-brief Skill
2★ repoGenerate competitive SEO content briefs with per-section word counts, competitor scoring, keyword density guidance, and page-type templates. Supports both new page briefs and improve-existing-page briefs. Use when user says "content brief", "write a brief", "content outline", "blog brief", "service page brief", "brief for", "writing brief", "content plan", or "outline for".
The same file is in 3 other repositories
rakibulism/agent-skills-os/skills/seo-plan Skill
2★ repoStrategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".
The same file is in 1 other repository
rakibulism/agent-skills-os/skills/seo-sxo Skill
2★ repoSearch Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".
The same file is in 1 other repository
IamK77/Skill/skills/engineering/groundwork Skill
2★ repoDiscover and pin down what to build before building it, with a gated five-stage flow: elicit the real need (not the stated solution), analyze and prioritize, write verifiable requirements, validate shared understanding, and manage change. Use when the user asks for a feature, system, or change — especially a vague or solution-shaped one ("add an export button", "make it faster", "build me an X"); mentions requirements, specs, user stories, acceptance criteria, scope, stakeholders, MoSCoW, or non-functional needs; or before you start coding anything non-trivial whose real goal is not yet nailed down.
IamK77/Skill/skills/inquiry/ledger Skill
2★ repoThe experiment-design lens: turn the surviving method into a protocol that produces evidence a reviewer believes — for any field that runs experiments to publish (ML, optimization, operations research, systems). Use after crucible lands a method, when planning the experiments, or stress-testing a plan. The one shift: you write down what counts as EVIDENCE before you look at the data — the protocol (claims, instances, baselines, metrics, and the bar for support OR refutation) is FROZEN before the main run, because choosing a good story after the fact is p-hacking. The keystone is a firewall between EXPLORATION (generates hypotheses, never enters the paper) and CONFIRMATION (survivors, fresh seeds). Triggers on "design the experiments / experiment protocol", "which baselines / is this comparison fair", "p-hacking / pre-register", "is my evaluation honest".
IamK77/Skill/skills/surface/bearings Skill
2★ repoThe before-the-first-line lens for a frontend build: fix what is expensive to reverse before sunk cost exists. Use when starting a frontend product or major feature, or stress-testing a plan that jumped straight to a framework. The three ruling principles: BOUNDARIES > FRAMEWORKS (frameworks get swapped; the network/trust line and state classification fossilize into bedrock); ALLOCATE CAUTION BY REVERSIBILITY (one-way doors earn slow human judgment, two-way doors get a default for agents); and THE SOURCE OF TRUTH LIVES IN THE USER'S MIND, not the database. The one shift: frontend is the one discipline whose correctness spec lives in a brain, so taste is load-bearing and cannot be outsourced. Triggers on "starting a frontend / from scratch", "which framework", "how should I architect this UI".
m-binimran/real-estate-pack/skills/farming-prospecting Skill
2★ repoBuild a geographic-farm or sphere-of-influence prospecting plan - target area, cadence, content mix, and tracking - that's consistent and compliant. Use when planning lead generation or a farm.
m-binimran/real-estate-pack/skills/negotiation-strategy Skill
2★ repoDevelop a negotiation strategy for offers, counters, repair requests, and multiple-offer situations - leverage, priorities, and walk-away points. Use when negotiating a deal for a buyer or seller.
m-binimran/real-estate-pack/skills/open-house-plan Skill
2★ repoPlan an open house end to end - prep checklist, marketing, sign-in/lead capture, day-of flow, safety, and follow-up. Use when scheduling an open house.
campfront/camp-skills/skills/evening-program Skill
2★ repoWhen camp staff need to plan an evening program, such as a campfire, an all-camp wide game, or a theme night that kids remember and that winds down to bedtime. Use for evening program, campfire planning, an all-camp or wide game, theme night, a last-night or first-night program, a rainy-night indoor program, or how to end the night calm. It draws on camp-profile for the camp's ages and facilities, and hands the games themselves to activity-planner.
tbhb/social-skills/plugins/process-theater/skills/strategic-ambiguity Skill
2★ repoProvides balanced, context-sensitive guidance that accounts for every contingency. Use when the user asks for advice, a recommendation, a comparison, or any question that expects a definitive answer. Also use when the user asks for an estimate, whether something is a good idea, a best practice, or anything phrased as 'should I' or 'is it better to.'
F-e-u-e-r/opus-pack/skills/cross-model-review Skill
2★ repoGet an adversarial review from a DIFFERENT model family before a load-bearing merge/ship — the mechanized form of "the author is not the judge" when the strongest independent lens is another model, not just a fresh-context subagent of your own. Load when about to merge/ship load-bearing work (code, or a load-bearing plan/spec/doctrine doc), or when the user asks to get an external/second model to review. Do NOT load for routine changes a same-model fresh-context critic covers (delegation-and-review §3), for routine copy/marketing/user-facing prose, or as a way to skip reproducing findings yourself.
F-e-u-e-r/opus-pack/skills/personal-goal-planning Skill
2★ repoCoach-style personal goal planning — a five-step protocol that turns a person's situation into tiered goals (2–4 weeks / 2–3 months / 6–12 months) with one mainline, a small set of executable tasks, a realistic weekly rhythm, and a weekly review loop with a stuck rule. Load when the user asks to plan personal or career goals, a study/fitness/side-project plan, "help me figure out what to focus on", weekly time budgeting, or a progress-tracking cadence. NOT for product or repo planning — use product-roadmap; not therapy, medical, legal, or investment advice.
F-e-u-e-r/opus-pack/skills/product-roadmap Skill
2★ repoProduct-owner planning partner — turns a goal plus the repo's actual state into a verdict, a Now/Next/Later/Not-now roadmap, milestones with acceptance criteria, and agent-ready tasks. Load when the user asks "what should we build next?", any roadmap/milestone/release/MVP/priority/PRD question, wants the current repo assessed for product direction, or wants similar GitHub projects mined for insight. NOT for picking today's coding task inside an already-agreed milestone, and not marketing/pricing strategy.
alexvtejeda/elenchus/skills/elenchus-plan Skill
no license2★ repoUse when you have an approved spec (or firm requirements) for a multi-step build and want the implementation plan itself stress-tested before you execute it — "write the plan and have the council check it", "verify this plan against the spec", "turn this spec into a plan I can trust", or the writing-plans stage of the Elenchus pipeline. The plan/verification front end over the elenchus-council engine. NOT for stress-testing a build PREMISE that isn't settled yet (that's elenchus-build), NOT for authoring plan craft from scratch with no council (that's plain writing-plans), and NOT for verifying a finished implementation in the browser (that's finishing-implementation-elenchus).