Plan & spec
10,741 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
SkillMedev/skills/skills/lesson-plan-builder Skill
5★ repoBuilds a complete single-lesson plan - measurable objective, timed four-part arc (hook, direct instruction, guided practice, closure), a formative check with a proceed/re-teach rule, and differentiation notes - clear enough that a substitute could run it. Use when someone asks "write a lesson plan for...", "plan a 50-minute class on photosynthesis", "how should I structure tomorrow's lesson", or "turn this standard into a lesson". Do NOT use for sequencing a multi-week unit or full course - use curriculum-mapper instead; for deep per-learner adaptation of an existing lesson, use differentiated-instruction; for writing the quiz itself, use quiz-generator.
The same file is in 2 other repositories
SkillMedev/skills/skills/logo-brief-writer Skill
5★ repoWrites a complete creative brief for a logo or identity project - business context, a three-adjective personality axis, deliverables and constraints, competitive territory, rounds and timeline, and concrete success criteria. Use when someone asks "write a logo brief", "brief a designer for our rebrand", "what do I send the identity studio", or is kicking off a brand identity engagement. Do NOT use for generating the brand name itself - use brand-naming instead; for documenting the finished identity system's usage rules, use brand-guidelines; for briefing broader creative direction, use moodboard-builder.
The same file is in 1 other repository
SkillMedev/skills/skills/longevity-protocol Skill
5★ repoAssembles an evidence-tiered weekly longevity routine across the four pillars with the strongest healthspan data - sleep, zone 2 aerobic work, strength training, and dietary pattern - plus stress and connection, delivered as a filled weekly template with honest evidence labels. Use when someone asks "build me a longevity routine", "what actually extends healthspan", "audit my health habits", or "is this supplement stack worth it". General wellness guidance, not medical advice. Do NOT use to program the individual pieces in depth - use zone-2-cardio-plan for the aerobic block, strength-training-plan for lifting, sleep-optimizer for sleep, nutrition-planner for macros; for HIIT/conditioning use fitness-program; for interpreting labs use bloodwork-explainer.
The same file is in 1 other repository
SkillMedev/skills/skills/meal-planner Skill
5★ repoBuilds a realistic weekly meal plan - protein anchors first, a batch-cook prep schedule, and a deduplicated grocery list grouped by store section - sized to household, budget, and weeknight time limits. Use when someone asks "plan my meals for the week", "make me a grocery list", "what should we eat this week", or "help me meal prep on Sunday". Do NOT use for setting calorie and macro targets or nutrition strategy - use nutrition-planner instead; this skill turns targets into cookable weeks.
SkillMedev/skills/skills/microservices Skill
5★ repoDesigns microservice architectures - service boundaries from business capabilities and team ownership, sync vs async communication choices, saga and outbox patterns for consistency, and resilience defaults - producing a boundary map with an extraction verdict per candidate service. Use when someone asks "should this be its own service", "how do I split my monolith's domains", "sync or event-driven between these services", "how do I handle transactions across services", or is reviewing a distributed architecture. Do NOT use for planning the step-by-step migration off an existing monolith - use monolith-decomposer or strangler-fig-planner for the migration process; this skill owns the target architecture. Do NOT use for designing an individual REST contract - use api-design instead.
SkillMedev/skills/skills/motion-spec Skill
5★ repoSpecifies animation and motion precisely - duration, easing curve, trigger, and intent - for accurate engineer implementation. Use when handing off transitions, micro-interactions, or loading states.
The same file is in 1 other repository
SkillMedev/skills/skills/mutual-action-plan Skill
5★ repoBuilds a mutual action plan (MAP) with shared milestones, named owners, and buffer-padded dates that drives a qualified deal from verbal intent to signature and go-live. Use when someone asks "build a mutual action plan for this deal", "how do I keep this deal from stalling", "the buyer said yes but nothing is moving", or once a prospect is qualified and has expressed intent to move forward. Do NOT use for preparing the qualification call itself - use discovery-call-prep instead. Do NOT use for scripting the negotiation and close conversation - use closer-sales-script instead.
The same file is in 1 other repository
SkillMedev/skills/skills/nutrition-planner Skill
5★ repoSets personal nutrition targets - protein at 1.6-2.2 g/kg, a calorie budget from goal and activity, fiber and hydration floors - and a repeatable meal structure with a review-and-adjust protocol for fat loss, muscle gain, or maintenance. Use when someone asks "how much protein should I eat", "set my macros for a cut", "why has my weight stalled", or "build me a sustainable diet framework". General wellness guidance, not medical advice. Do NOT use to produce a specific week of recipes with a shopping list and prep schedule - use meal-planner instead (this skill sets the targets; meal-planner cooks to them); for the broader multi-pillar health routine, use longevity-protocol.
The same file is in 1 other repository
SkillMedev/skills/skills/okr-builder Skill
5★ repoDrafts a quarter's OKRs - an inspiring qualitative objective with 3-5 measurable key results, each with a baseline, target, and owner - plus the weekly confidence check-in and end-of-quarter grading cadence. Use when someone asks "help me write OKRs", "are these key results any good", "turn our goals into OKRs for next quarter", or "how do we score our OKRs". Do NOT use for building the full-year company plan that OKRs slot into - use annual-plan instead - or for personal goal-tracking with a check-in partner - use goals-accountability instead.
The same file is in 2 other repositories
SkillMedev/skills/skills/onboarding-plan-builder Skill
5★ repoProduces a 30/60/90-day onboarding plan for a specific role with phased milestones, first-week setup, observable success criteria, and ramp reviews. Use when a new hire has an accepted offer or start date, or when asked to write, draft, or improve a 30/60/90 / ramp / onboarding plan for a role. Do NOT use for the structure of ongoing recurring 1:1s - use 1on1-agenda instead.
The same file is in 1 other repository
SkillMedev/skills/skills/one-pager-designer Skill
5★ repoWrites a decision-driving one-pager - problem, evidence, impact, and a specific ask compressed into a single page readable in under three minutes. Use when someone asks "turn this into a one-pager", "write a brief for leadership", "I need a one-page pitch for this decision", or is preparing a document a busy reader must act on from one page. Do NOT use for a client-facing sales proposal with pricing and scope - use sales-proposal-writer instead; for condensing an existing long document use executive-summary; for multi-slide narratives use slide-deck-builder.
The same file is in 1 other repository
SkillMedev/skills/skills/partition-planner Skill
5★ repoProduces a partitioning or sharding plan for an oversized table - range/list/hash strategy, partition-key choice, composite-key and pruning constraints, and a verdict on whether to partition at all. Use when one table has grown past tens of millions of rows or hundreds of GB, vacuum/autovacuum on it runs for hours, retention deletes are giant DELETEs, or you are deciding between range/list/hash partitioning or sharding a hot table. Do NOT use when the goal is choosing indexes for specific slow queries - use index-advisor instead.
The same file is in 1 other repository
SkillMedev/skills/skills/partnership-strategy Skill
5★ repoIdentifies, prioritizes, and structures business partnerships that produce measurable revenue - matching partnership type to goal, setting economics with real rev-share ranges, and enforcing a pilot-before-contract rule. Use when someone asks "should we partner with X", "how do we structure a reseller deal", "what rev share is normal", "our partnerships never produce anything", or "which partners should we prioritize". Do NOT use for choosing between partnerships and other distribution channels - use channel-strategy instead - or for the overall market-entry plan a partnership sits inside - use go-to-market-planner instead.
SkillMedev/skills/skills/policy-brief Skill
5★ repoWrites a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, use whitepapers; for condensing an existing long document, use executive-summary.
The same file is in 1 other repository
SkillMedev/skills/skills/pricing-strategy Skill
5★ repoSet or revise pricing for any product by triangulating value, competition, and cost floor into a recommended structure, price points, and a test plan. Use when someone asks "what should I charge", "how do I price my product", "are we priced too low", "should we go usage-based or flat", or is preparing a repricing or a new-product launch. Do NOT use for designing SaaS tier ladders, value metrics, and expansion packaging in detail - use saas-pricing instead; for gym front-end offers and guarantees use gym-pricing-and-guarantees; for checking whether the resulting price produces healthy CAC payback use unit-economics.
The same file is in 2 other repositories
SkillMedev/skills/skills/primary-research Skill
5★ repoDesigns a rigorous primary research protocol for collecting new data - research question, hypotheses, method selection, sampling with a power analysis, instrument design, a named control for every bias threat, and a pre-specified analysis plan. Use when someone asks "design a study to test this", "how many respondents do I need", "should this be a survey or interviews", or must produce defensible first-hand evidence rather than cite existing work. Do NOT use for synthesizing already-published sources - use deep-research or literature-review instead; for writing the discussion guide for a single expert conversation, use expert-interview instead; for detailed survey question wording and scale design, use survey-designer instead.
SkillMedev/skills/skills/product-roadmap Skill
5★ repoTurns product strategy into a themed Now/Next/Later roadmap with explicit trade-offs, confidence levels, and no committed dates beyond one quarter. Use when someone asks "build our product roadmap", "turn these priorities into a roadmap", "execs want committed ship dates for next year", or needs to communicate direction without over-promising. Do NOT use for company-wide annual operating plans - use annual-plan instead; for defining the goals a roadmap serves, use okr-builder; for scheduling work inside a sprint, use sprint-planning.
The same file is in 1 other repository
SkillMedev/skills/skills/prototype-spec Skill
5★ repoTurns a static design into a numbered, testable, dev-ready specification covering every state, interaction, breakpoint, motion detail, and edge case the mockup cannot show. Use when someone asks "write the spec for this screen", "engineering keeps asking what happens when", "document the interactions before handoff", "what states does this component need", or a build came back wrong because behavior was never written down. Do NOT use for the motion token details themselves - use motion-spec instead; for verifying a finished build against the spec, use design-qa-checklist.
The same file is in 2 other repositories
SkillMedev/skills/skills/responsive-spec Skill
5★ repoSpecifies responsive behavior across breakpoints - layout reflow, content priority, touch targets, and fluid-versus-stepped scaling rules - precisely enough for engineers to implement directly. Use when someone asks "how should this work on mobile", "spec the breakpoints", "write the responsive rules for this page", or is adapting a single-viewport design for multi-device use. Do NOT use for static measurements inside one frame - use redline-annotation instead; for the overall handoff package with flows and edge cases, use design-handoff-doc.
The same file is in 1 other repository
SkillMedev/skills/skills/retirement-projection Skill
5★ repoProjects retirement readiness from savings rate, target nest egg, and compound growth - computes the required portfolio via safe-withdrawal-rate math, years to financial independence, and pension or Social Security offsets, with a runnable calculator. Use when someone asks "how much do I need to retire", "am I on track to retire at 60", "what does my savings rate get me", or "can I retire early". General financial education, not personalized investment advice. Do NOT use for choosing funds or setting an asset allocation - use investment-basics instead; do NOT use for a full financial plan with budgeting and insurance - use financial-planner instead.
The same file is in 1 other repository
SkillMedev/skills/skills/sales-enablement-kit Skill
5★ repoUse when equipping a sales motion with the full set of assets reps actually carry into deals, produced as one coherent kit - a one-pager, a competitive battlecard, a demo script outline, and an objection-handling matrix. Triggers on "build the sales enablement kit for our new product", "equip our sales reps with enablement assets", "put together the sales collateral for our launch". Do NOT use for a single standalone battlecard or a one-competitor deep-dive - use competitive-intelligence instead; do NOT use when the category frame (for whom, unlike what) is not yet fixed - use positioning-statement first; do NOT use when the value ladder and proof points are not settled - use messaging-hierarchy first; do NOT use to sequence the rollout calendar - use launch-plan-sequencer; do NOT use to brief the team and run the checklist on launch day - use launch-day-runbook; do NOT use for a self-serve / no-rep-in-the-room motion - use plg-motion-designer instead.
The same file is in 1 other repository
SkillMedev/skills/skills/sales-proposal-writer Skill
5★ repoWrites a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a proposal", "how should I present pricing in this proposal", or when a deal needs a document to move from discovery to close. Do NOT use for a one-page internal decision brief - use one-pager-designer instead; for investor decks use pitch-deck-builder; for setting the underlying price model use pricing-strategy.
The same file is in 3 other repositories
SkillMedev/skills/skills/segmentation-strategy Skill
5★ repoBuilds a behavioral segmentation system for lifecycle messaging - RFM-based segments, event-driven membership triggers, one next action per segment, size audits, and send-time suppression rules. Use when someone asks "how should I segment my users", "our emails get ignored, who should get what", "how do I message at-risk users differently", or is personalizing lifecycle campaigns to cut unsubscribes and lift click-through. Do NOT use for building ad-platform audiences - use audience-targeting instead; for narrative customer personas use user-persona or icp-persona-builder; for mapping the full lifecycle stages and journeys use lifecycle-journey-map.
The same file is in 1 other repository
SkillMedev/skills/skills/social-content-calendar Skill
5★ repoBuilds a 4-week multi-platform posting calendar for a brand or social team, balancing content pillars, per-channel cadence, and real key dates into a week-by-week grid. Use when the user asks to plan, build, or audit a social content calendar or posting schedule across multiple channels (LinkedIn, X, Instagram, TikTok, YouTube Shorts), assign content pillars and ratios, or map a month of posts to launches and events. Do NOT use when planning a solo creator's single-channel video or podcast cadence and theme rotation - use creator-content-calendar instead.
The same file is in 1 other repository
SkillMedev/skills/skills/sprint-planning Skill
5★ repoFacilitates sprint planning end to end - backlog refinement checks against a Definition of Ready, a one-sentence sprint goal, capacity math from velocity and PTO, story selection and team commitment, task breakdown, and flagged risks with owners. Use when a team asks "plan our next sprint", "how much should we commit to", "write a sprint goal", or keeps blowing sprint forecasts. Do NOT use for running the retrospective after the sprint ends - use sprint-retro-facilitator instead.
The same file is in 1 other repository
SkillMedev/skills/skills/sql-query-optimizer Skill
5★ repoDiagnoses slow SQL from the execution plan, names the cost driver, and delivers the rewritten query plus index DDL with the expected plan change and write-side cost stated. The general entry point for slow-query work that routes deep cases to specialist skills. Use when someone asks "why is this query slow", "can you optimize this SQL", "what index do I need", "this endpoint got slow and it's the database", or pastes an EXPLAIN output. Do NOT use for deep index strategy across a whole schema - use index-advisor instead; for pure query-shape rewrites when indexes are already right - use query-rewriter instead; for ORM-driven repeated-query patterns - use n-plus-one-hunter instead; for line-by-line EXPLAIN interpretation training - use explain-plan-reader instead; for table partitioning decisions - use partition-planner instead.
The same file is in 1 other repository
SkillMedev/skills/skills/stakeholder-update Skill
5★ repoWrites project stakeholder updates readable in under 60 seconds - honest RAG status, decisions made, explicit asks with owners and dates, next milestones - tiered to the audience. Use when someone asks "write my weekly project update", "how do I tell stakeholders we're at risk", "draft a status email for leadership", or "my updates get ignored, fix the format". Do NOT use for aggregating many teams' statuses into one engineering-wide report - use eng-status-rollup instead. For monthly investor letters with metrics and asks to VCs, use investor-update-writer; for customer-facing incident status, use status-page-update.
The same file is in 1 other repository
SkillMedev/skills/skills/strangler-fig-planner Skill
5★ repoProduces an incremental migration plan that runs a legacy and a new system side by side behind a routing seam, slicing and sequencing whole capabilities so the old system stays live until its last route is cut. Use when planning to replace or rebuild a large, business-critical system that must keep serving traffic throughout. Do NOT use when extracting a single service from a still-living monolith - use monolith-decomposer instead; for generic non-migration implementation planning, use the plan skill instead.
The same file is in 1 other repository
SkillMedev/skills/skills/strength-training-plan Skill
5★ repoUse when someone starts lifting, hits a strength or hypertrophy plateau, restructures a lifting program, or wants to build strength or muscle - designing a progressive resistance program with splits, compound movement patterns, sets/reps, progressive overload, and deloads from barbells and dumbbells. General fitness guidance, not medical advice. Owns resistance/strength training only. Do NOT use to program high-intensity interval conditioning or circuits (use fitness-program), a steady-state aerobic-base or Zone 2 block (use zone-2-cardio-plan), or a mobility/flexibility routine (use mobility-routine).
The same file is in 1 other repository
SkillMedev/skills/skills/tax-optimization Skill
5★ repoWorks through the legal tax-reduction sequence - tax-advantaged account priority, standard-vs-itemized decision math, tax-loss harvesting, income timing, and Roth-vs-traditional rules - and produces a personal tax checklist. Use when someone asks "how do I pay less in taxes", "should I itemize", "Roth or traditional", "what is tax-loss harvesting", or is doing year-end planning or reviewing withholding. Do NOT use for the broader ordering of savings and debt priorities - use financial-planner instead; for investing fundamentals beyond account tax treatment - use investment-basics; for projecting retirement account balances - use retirement-projection.
The same file is in 1 other repository
SkillMedev/skills/skills/tech-debt-prioritizer Skill
5★ repoInventories tech debt and ranks it economically - scoring each item 1-3 on cost of delay (the interest rate) and leverage (the principal unblocked), multiplying into a priority index, and packaging the winners into a leadership proposal framed on business impact. Use when someone asks "which tech debt should we tackle first", "help me build a case for refactoring to leadership", "our backlog of debt is huge, where do we start", or is preparing quarterly planning. Do NOT use for finding and removing unused code - use dead-code-eliminator instead - for auditing third-party dependency risk - use dependency-risk-audit - or for planning the sprint the work lands in - use sprint-planning instead.
The same file is in 1 other repository
SkillMedev/skills/skills/technical-spec Skill
5★ repoWrites engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.
The same file is in 1 other repository
SkillMedev/skills/skills/thumbnail-concept Skill
5★ repoProduces three distinct high-CTR YouTube thumbnail concepts per video - each a full spec with focal point, precise facial-expression direction, text overlay copy, color and background direction, and two paired title variants. Use when someone says "I need a thumbnail idea", "why is my CTR low", "help me pick a thumbnail and title", or is planning a video before filming and wants the click package designed first. Do NOT use for the spoken and visual opening seconds of the video itself - use video-hook-writer instead; do NOT use to write the full video - use youtube-script-writer instead; do NOT use for cropping, captioning, or exporting finished video files - use social-video-formatter instead.
The same file is in 1 other repository
SkillMedev/skills/skills/usability-test-plan Skill
5★ repoPlans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.
The same file is in 1 other repository
SkillMedev/skills/skills/zone-2-cardio-plan Skill
5★ repoUse when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).
The same file is in 1 other repository
Sudhakaran88/solopreneur-skills/skills/content-strategy Skill
5★ repoWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also trigger on "content strategy", "what should I write about", "content ideas", "blog strategy", "topic clusters", "content planning", "content calendar", "editorial calendar", "what content works for SaaS/ecom". For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media specifically, see social-content.
Sudhakaran88/solopreneur-skills/skills/free-tool-strategy Skill
5★ repoWhen the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO, or brand awareness. Also trigger on "engineering as marketing", "free tool", "marketing tool", "calculator", "generator", "interactive tool", "lead gen tool", "build a tool for leads", "free resource", "tool SEO". Bridges engineering and marketing.
Sudhakaran88/solopreneur-skills/skills/launch-strategy Skill
5★ repoWhen the user wants to plan a product launch, feature announcement, or go-to-market strategy. Also trigger on "launch", "Product Hunt", "feature release", "announcement", "go-to-market", "GTM", "beta launch", "early access", "waitlist", "product update", "SaaS launch plan". Covers pre-launch, launch day, and post-launch phases. For full sales GTM motion (ICP→positioning→channels), see gtm-saas. For pricing during launch, see pricing-strategy.
Sudhakaran88/solopreneur-skills/skills/pricing-strategy Skill
5★ repoWhen the user wants help with pricing decisions, packaging, or monetization strategy. Also trigger on "pricing", "how much should I charge", "pricing tiers", "freemium", "free trial", "packaging", "price increase", "value metric", "willingness to pay", "monetization", "pricing page". Covers pricing research, tier structure, packaging, and psychology. For pricing page conversion (design/copy), see paywall-upgrade-cro or page-cro.
Sudhakaran88/solopreneur-skills/skills/site-architecture Skill
5★ repoWhen the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also trigger on "sitemap", "site structure", "page hierarchy", "information architecture", "IA", "navigation design", "URL structure", "breadcrumbs", "internal linking strategy", "website planning". NOT for XML sitemaps (see seo-audit). For SEO audits, see seo-audit.
HsuanYuLee/polaris/.claude/skills/sprint-planning Skill
5★ repoUse when the user wants to conduct or prepare for a Sprint planning session — organizing ticket candidates, reviewing capacity, or preparing a release page. Trigger: 'sprint planning', 'sprint 規劃', '下個 sprint', '排 sprint', 'release page'.
HsuanYuLee/polaris/.claude/skills/verify-AC Skill
5★ repoQA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents observed vs expected as pure facts (no root-cause judgement). On FAIL, surfaces human disposition gate (spec issue vs implementation drift); on PASS, it may transition the AC ticket to Done only after verification artifact/report is current and the shared verification contract resolves to PASS. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to refinement Bug source mode; spec issue routes back to refinement.
ramboz/jig/hosts/claude/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/hosts/claude/skills/spec-workflow Skill
5★ repoDrive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition state markers (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; also DEFERRED for parked slices with a stated resolution trigger), enforce the reconciliation checklist before commit, and surface stale specs/ADRs whose `last_verified` date has aged past dependency changes. Use when starting non-trivial new work, creating a spec, transitioning a slice's state, parking a slice as DEFERRED, reconciling a reviewed slice, or auditing doc freshness. Do not use for quick one-off fixes that don't need a spec, or for bug-shaped work where `jig:bug-fix` is the better fit.
ramboz/jig/hosts/codex/plugins/jig/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/hosts/codex/plugins/jig/skills/spec-workflow Skill
5★ repoDrive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition state markers (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; also DEFERRED for parked slices with a stated resolution trigger), enforce the reconciliation checklist before commit, and surface stale specs/ADRs whose `last_verified` date has aged past dependency changes. Use when starting non-trivial new work, creating a spec, transitioning a slice's state, parking a slice as DEFERRED, reconciling a reviewed slice, or auditing doc freshness. Do not use for quick one-off fixes that don't need a spec, or for bug-shaped work where `jig:bug-fix` is the better fit.
ramboz/jig/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/skills/spec-workflow Skill
5★ repoDrive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition state markers (DRAFT → READY_FOR_REVIEW → READY_FOR_IMPLEMENTATION → IN_PROGRESS → REVIEWED → RECONCILED → DONE; also DEFERRED for parked slices with a stated resolution trigger), enforce the reconciliation checklist before commit, and surface stale specs/ADRs whose `last_verified` date has aged past dependency changes. Use when starting non-trivial new work, creating a spec, transitioning a slice's state, parking a slice as DEFERRED, reconciling a reviewed slice, or auditing doc freshness. Do not use for quick one-off fixes that don't need a spec, or for bug-shaped work where `jig:bug-fix` is the better fit.
gjoranv/claude-plan-skills/gh-implement-plan Skill
5★ repoImplement a GitHub plan issue step by step with checkpoints. Use when the user asks to "implement the plan", "start working on the plan", or "execute the plan".
gjoranv/claude-plan-skills/gh-read-plan Skill
5★ repoRead the GitHub plan issue given as argument. Use when the user tells you to "read this github plan issue" with the issue as argument.
gjoranv/claude-plan-skills/gh-update-plan Skill
5★ repoUpdate a GitHub plan issue with progress. Use when planning a task, or when the user tells you to "update the github plan issue".
BrennanJCollins/UnabatedPM-coaching/unabatedpm-career-growth/skills/impostor-to-strategist Skill
5★ repoConvert impostor syndrome from a career liability into strategic fuel — diagnosing the specific competence gap behind the feeling, building a personal development strategy around it, and stacking strengths others don't have. Coaches new PMs, recently promoted leaders, and career changers through Brennan Collins' Insecurity-to-Strategy framework.
BrennanJCollins/UnabatedPM-coaching/unabatedpm-influence/skills/adversarial-stakeholder-prep Skill
5★ repoDecode the hidden incentive map of every stakeholder in your room before you walk in. Coach the PM through the three archetypes (Risk Shield, Credit Catcher, Tribal Guardian), the three diagnostic questions (fired/promoted/validated), and the Adversarial Stakeholder Prompt — an AI devil's-advocate workflow that stress-tests your stakeholder read the night before a high-stakes pitch, roadmap review, or alignment meeting. Companion to the meeting before the meeting.
BrennanJCollins/UnabatedPM-coaching/unabatedpm-influence/skills/strategic-storytelling-pitch Skill
5★ repoTransform competent-but-forgettable pitches into compelling stories that get to 'yes' — using Brennan Collins' 3-Act Structure (Human Stakes → Scale → Solution), stakeholder-specific adaptation via the 'What Would Get Them Fired?' test, and the Bridge Madlib. Catches when PMs lead with logic instead of stakes.
BrennanJCollins/UnabatedPM-coaching/unabatedpm-strategic-thinking/skills/stakeholder-request-reframe Skill
5★ repoCoach a PM to respond to stakeholder feature requests using sincere curiosity, deliver a compelling reframe with the Mad Lib template, and position transparent tradeoffs using Stakeholder Judo (Stakeholder Judo) — turning stakeholder tension into strategic partnership.
BrennanJCollins/UnabatedPM-coaching/unabatedpm-strategic-thinking/skills/strategy-articulation Skill
5★ repoPressure-test your product strategy using Brennan Collins' Six Strategy Assessment Criteria (Pervasive Problem, Urgent Problem, Differentiated, Unique Advantage, Company Priority, Future Potential) and the DHM Filter (Delight, Hard to Copy, Margin-Enhancing) — catches feature roadmaps disguised as strategy, buzzword hand-waving, and missing competitive differentiation.
rohitgehe05/mindpowers/skills/mindstorming Skill
5★ repoUse before drafting any non-code knowledge-work deliverable, including strategic memos, business reviews, OKR defences, PRDs, decision docs, briefing docs, exec talking points, Slack messages to leadership, frameworks, post-mortems, one-pagers, BRDs. Triggers on asks like "help me write up X", "draft this memo", "what should I say to Y", even casually phrased. NOT for software implementation; for creating features, components, or code changes use superpowers:brainstorming instead; for authoring the PRD document itself, use this skill. For non-code deliverables this skill supersedes generic brainstorming. Do not skip for simple asks; simple tasks hide the costliest assumptions.
zeikar/hyperclaude/skills/hyper-implement Skill
5★ repoUse when about to execute a multi-task plan from .hyperclaude/plans/. Also when the user invokes /hyperclaude:hyper-implement. Runs each task in a fresh subagent with spec-compliance and code-quality gates between tasks.
zeikar/hyperclaude/skills/hyper-interview Skill
5★ repoUse when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you need", "clarify requirements first", "I'm not sure exactly what I want", "make sure you understand before building". Also when the user invokes /hyperclaude:hyper-interview. Runs a short one-question-at-a-time interview and writes a spec to .hyperclaude/specs/ — the front-end input to /hyperclaude:hyper-research and /hyperclaude:hyper-plan. Distinct from /hyperclaude:hyper-plan, which decomposes an ALREADY-CLEAR task into tasks.
zeikar/hyperclaude/skills/hyper-plan-loop Skill
5★ repoUse when a plan should be produced and critic-hardened in one gesture — plan → Codex review → revise, repeated until clean. Also when the user invokes /hyperclaude:hyper-plan-loop. For manual round-by-round control use /hyperclaude:hyper-plan + /hyperclaude:hyper-plan-review instead.