agentsclimarketplace

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

  • Ultrathink craftsmanship

    DYAI2025/Plumbline/config/claude/skills/ultrathink-craftsmanship Skill

    no license6★ repo

    Use for expensive, one-pass reasoning gates that stress-test a specification, plan, or near-final implementation for bias, hidden coupling, weak evidence, and craftsmanship risks.

  • Requirements analysis

    viacheslav-tronko/claude-code-harness/.claude/skills/requirements-analysis Skill

    6★ repo

    Evidence-bound transformation of vague human requirements (Jira ticket, Confluence page, free text, file path) into AI-ready specifications for coding agents. Use WHENEVER user asks to /distill, "analyze requirements", "clarify task", "vague requirements", "ambiguous AC", "task vs bug", "EARS", "Given-When-Then", "GWT", "AI-ready spec", "prepare spec for implementation", "Open Questions", "INVEST", "MoSCoW", "user story analysis", "acceptance criteria", "steps to reproduce", "expected vs actual", or pastes Jira-key / Confluence URL / free-text requirement asking "make this implementable / specifiable / unambiguous". Three modes — --brief (≤5pp preflight before /howto-implement), --standard (default Tier 2 full SPEC with EARS+GWT+traceability+glossary), --deep (Tier 3 security boundary / public API / migration / financial; multi-agent k=3 vote on ambiguity). Falsification-first, anti-hallucination — Killer Requirement FAIL-FAST, Goal Anchor Step-Back, Anti-Anchoring KNOWN/OBSERVED/UNKNOWN BEFORE normalization, ISO/IEC/IEEE 29148:2018 smell detector, Berry 4-class ambiguity classification (lexical/syntactic/semantic/pragmatic), Conservative Reading on ambiguity, Differential-Reading Test (would 2 reasonable readers produce contradictory acceptance tests?), CoVe Gate 2 factored verification on every REQ, Mutation Counterfactual on every "shall" claim, Disconfirmation-First on top hypothesis, Cross-REQ Consistency Check, Spec Pre-Mortem Adversarial Self-Check, SSOT preservation (Jira/Confluence > context > Atlassian search), 100% bidirectional traceability matrix (OR ↔ REQ), Sycophancy guard, INCONCLUSIVE valid verdict. Specification ONLY — produces SPEC-*.md report under LOCAL-MEMORY/; NEVER modifies source. Output feeds /howto-implement (implementation-blueprint) and /verify (task-verification). Do NOT use for fix-implementation (/bug-fix → surgical-implementation), root-cause investigation (/bug-why → root-cause-analysis), pre-implementation planning when spec already clear (/howto-implement → implementation-blueprint), code-path tracing (/trace → white-box-trace), or trivial Tier 0 typo / single-line clarification (Read/Grep + ASK USER).

  • Surgical implementation

    viacheslav-tronko/claude-code-harness/.claude/skills/surgical-implementation Skill

    6★ repo

    Surgical code-execution skill for AI coding agents on legacy codebases. Use WHENEVER the user asks to IMPLEMENT, CODE, BUILD, APPLY, or FIX from a contract source — IMP / Plan + TASK-NN, RCA report, freeform task, or Jira ticket. Triggers on /implement, /bug.fix, /code, /apply, /fix, "implement this", "code this", "build this", "apply this fix", "fix this bug", "execute the plan", "implement the blueprint", paths like `IMP-*.md`, `PLAN-*.md`, `RCA-*.md` followed by "implement"/"fix"/"apply", or pasted Jira ticket asking "implement / fix / build". Two MODES — IMPLEMENT (from IMP / Plan + TASK-NN / freeform) and FIX (from RCA Section 7.1 PRIMARY fix). Surgical-changes-first, verifier-guided, falsification-first, anti-hallucination — Read-Before-Edit + 3-line anchored edits, Stale-Context check, YAGNI master checklist, Diff-Budget hard cap (1.5× planned), Semantic Diff Guard (forbidden orthogonal damage), Verifier-Guided Self-Refinement Loop (run → on FAIL revise → rerun, max 3), Mutation Challenge on the fix, authorization scope check, Open Question Register at HIGH+, Cross-File Consistency, Final Verification CHAT-ONLY, Reflexion lesson on FAIL. MODIFIES source via Edit/Write — the only sibling that does. Layered onto CLAUDE.md §3 Tier · §4 Checkpoint · §6 Reasoning · §7 Adversarial Toolkit · §9 Output Contract · §10 Diff Budgets · §11 Pre-Send Checklist · §12 Repro Kernel · §13 Reflexion · P0 #1/#4/#7/#8/#10/#13/#16. Do NOT use for design-phase planning (use implementation-blueprint), root-cause investigation (use root-cause-analysis), pure code review (/review), distributed tracing, or trivial Tier 0 typos.

  • White box trace

    viacheslav-tronko/claude-code-harness/.claude/skills/white-box-trace Skill

    6★ repo

    White-box code-path tracing in two modes. REAL — empirical verification of completed code via CFG/MPC traversal, Counterfactual + optional Live Mutation Testing, PBT hook, Tandem-FL on FAIL, Killer-Path-First, FAIL-FAST, persistent index-prefixed JSONL trace with resume + confidence decay, Reviewer Agent re-rank, Reflexion lessons, structured fix_proposal + repro_snippet. VIRTUAL — pre-implementation falsification of RCA reports / Implementation Blueprints / Plans / freeform ideas via Planner-Simulator, POPPER falsification-first, LTL plan consistency, cross-artifact drift detection, defended against Mental-Reality Gap. Use WHEN user says /trace, /trace.real, /trace.virtual, /verify-plan, "verify this code", "trace these paths", "check coverage", "verify this plan", "falsify my RCA", "is this blueprint sound", "will this implementation work", "will my fix work", "white-box tracing", "mutation testing", "CFG analysis", "MPC", "SBFL", "Tandem-FL", "fault localization". Investigation only — never modifies source. Anti-hallucination (Citation-Grounded re-read, Mutation Counterfactual, CoVe, Disconfirmation-First, Sycophancy guard); declares INCONCLUSIVE rather than fabricate. Do NOT use for fix implementation (/bug.fix), root-cause investigation (/bug.why = root-cause-analysis skill), or distributed tracing (B-085).

  • Product manager

    CrashBytes/claude-role-skills/skills/product-manager Skill

    6★ repo

    Act as a strategic Product Manager to drive product strategy, roadmapping, competitive analysis, metrics definition, and go-to-market planning. Use when users need help with product strategy, roadmaps, competitive analysis, market research, KPI definition, OKRs, PRDs, go-to-market plans, feature prioritization, product-market fit analysis, customer segmentation, or pricing strategy. Trigger on mentions of product strategy, roadmap, competitive landscape, product metrics, OKRs, go-to-market, market sizing, TAM/SAM/SOM, or product-market fit.

    The same file is in 3 other repositories

  • Product owner

    CrashBytes/claude-role-skills/skills/product-owner Skill

    6★ repo

    Act as an experienced Product Owner to manage product backlogs, write user stories, define acceptance criteria, prioritize work, and align stakeholders. Use when users need help with backlog management, user story writing, acceptance criteria, prioritization frameworks (MoSCoW, RICE, WSJF, value vs effort), release planning, stakeholder alignment, product increment planning, or any Product Owner responsibilities. Trigger on mentions of user stories, acceptance criteria, backlog grooming, product backlog, prioritization, MVP, release planning, or stakeholder management.

    The same file is in 3 other repositories

  • Software migration engineer

    CrashBytes/claude-role-skills/skills/software-migration-engineer Skill

    6★ repo

    Act as a Software Migration Engineer to plan and execute technology migrations, legacy system modernization, database migrations, cloud migrations, and framework upgrades. Use when users need help with migrating between technology stacks, legacy system assessment, migration planning and risk analysis, database migration strategies, cloud migration (lift-and-shift, re-platform, re-architect), framework or language upgrades, data migration and ETL, API versioning and migration, monolith-to-microservices decomposition, or migration testing strategies. Trigger on mentions of migration, legacy modernization, technology upgrade, re-platform, re-architect, lift-and-shift, database migration, cloud migration, framework upgrade, or monolith decomposition.

    The same file is in 3 other repositories

  • Blue ocean strategy

    deciqAI/knowledge-skills/blue-ocean-strategy Skill

    6★ repo

    Activate when: user asks 'how do we stop competing on price?', 'what new market can we create?', 'is there a way to differentiate and cut costs at the same time?', describes an industry where all competitors look identical and margins are eroding, or a team is choosing a market entry angle to avoid head-to-head competition. Do NOT activate when: competitive dimensions are fixed by regulation (utilities, certain financial products); or a network-effects incumbent already dominates the space — use disruptive-innovation instead. More: deciqai.com/s/blue-ocean-strategy

  • Definite optimism

    deciqAI/knowledge-skills/definite-optimism Skill

    6★ repo

    Activate when: user says 'definite optimism,' 'Thiel's 2x2,' 'do we have a real plan or just options,' 'we're keeping our options open,' or asks whether a strategy/career/company is a concrete bet on the future or a diversified hedge; a plan consists mainly of process (iterate, A/B test, stay lean, stay flexible) with no falsifiable long-term thesis; someone must choose between committing to one path and preserving optionality. Do NOT activate when: the question is tactical execution inside an already-committed thesis (sprint planning, feature triage); genuine uncertainty is so high and reversal so cheap that optionality is correct for now and the user knows it; the user needs bet-sizing or probability math rather than a stance on planning itself. More: deciqai.com/s/definite-optimism

  • Map is not the territory

    deciqAI/knowledge-skills/map-is-not-the-territory Skill

    6★ repo

    Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter. More: deciqai.com/s/map-is-not-the-territory

  • Momentum and form

    deciqAI/knowledge-skills/momentum-and-form Skill

    6★ repo

    Activate when: user says 'we have a better product but we're losing,' 'they're growing despite less funding,' 'our moat isn't protecting us,' 'the market shifted under us,' 'we just need to hire harder,' or is diagnosing why strong incumbents lose to weaker newcomers, evaluating a market entry, or asking whether a strategy depends too much on specific people. Do NOT activate when: the decision is purely tactical (not strategic), or the context is cooperative/ethical leadership where 'winning configurationally' is the wrong frame. More: deciqai.com/s/momentum-and-form

  • Narrow gate strategy

    deciqAI/knowledge-skills/narrow-gate-strategy Skill

    6★ repo

    Activate when: user says 'this is taking too long', 'everyone else is doing X', 'should we take the easier path', 'is this worth it', 'we need to build a moat', 'choosing which capability to invest in long-term', or 'should we persist or pivot on this hard path'. Do NOT activate when: the path is only hard but not value-building (sunk-cost rationalization), or when the vindication horizon exceeds the organization's survival window. More: deciqai.com/s/narrow-gate-strategy

  • North star metric

    deciqAI/knowledge-skills/north-star-metric Skill

    6★ repo

    Activate when: teams are fighting over which metric to optimize; someone says 'north star metric,' 'NSM,' 'OMTM,' or 'one metric that matters'; a dashboard has 30+ metrics with no clear priority; a leading indicator is needed that predicts revenue before it moves; or someone asks 'what should we optimize?' Do NOT activate when: the product has no customers yet (no value to measure — use lean-startup instead); a single team in a mature business needs execution KPIs rather than cross-team alignment. More: deciqai.com/s/north-star-metric

  • Okr goal setting

    deciqAI/knowledge-skills/okr-goal-setting Skill

    6★ repo

    Activate when: user says 'set OKRs', 'write objectives and key results', 'our goals aren't measurable', 'teams are hitting targets but the business isn't moving', 'we need stretch goals', 'align teams around quarterly goals', or mentions Doerr / Measure What Matters. Do NOT activate when: the team is under ~10 people with informal alignment that works fine; output is genuinely uncertain (deep R&D, research labs) making 'achieve X by Q3' structurally impossible. More: deciqai.com/s/okr-goal-setting

  • Pricing strategy

    deciqAI/knowledge-skills/pricing-strategy Skill

    6★ repo

    Activate when: user says 'how should we price this', 'we should just charge more', 'our competitors charge X', 'willingness to pay', 'anchor price', 'value-based pricing', 'freemium structure', setting a first price for a new product, considering a price increase and worried about churn, or needing to design tiered/usage-based pricing. Do NOT activate when: the product has no demonstrated value yet (use lean-startup instead); price is fixed by regulation. More: deciqai.com/s/pricing-strategy

  • Scenario planning

    deciqAI/knowledge-skills/scenario-planning Skill

    6★ repo

    Activate when: user says 'what are the scenarios,' 'stress test our strategy,' 'what if X happens,' 'multiple futures,' 'strategic resilience,' or is making a high-stakes irreversible decision with a 3+ year horizon where a single forecast could be catastrophically wrong. Do NOT activate when: the decision is short-horizon and easily reversible (sprint priorities, A/B test order); or only one driver matters and it is already measurable — use sensitivity analysis instead. More: deciqai.com/s/scenario-planning

  • Strategic commitment

    deciqAI/knowledge-skills/strategic-commitment Skill

    6★ repo

    Activate when: someone says 'they don't believe we'll follow through', 'how do I make my threat credible?', 'how do we deter a competitor from entering?', 'we need to lock in this customer/partner', 'should we burn our bridges?', or when a stated threat or promise is being discounted by the other side. Do NOT activate when: the problem is capability (you cannot execute the threat, not just credibility that you will), or when the environment is changing so fast that any lock-in creates more rigidity than credibility gain. More: deciqai.com/s/strategic-commitment

  • Strategic execution 3d9

    deciqAI/knowledge-skills/strategic-execution-3d9 Skill

    6★ repo

    Activate when: strategy results are consistently below target despite strong market conditions; a team agrees on a plan but results fall far short; diagnosing why execution broke down after a leadership change or merger; auditing whether the organization can support a new growth phase. Do NOT activate when: the team is fewer than 10 people with no defined organizational system; no strategy exists yet and the task is pure strategy formulation. More: deciqai.com/s/strategic-execution-3d9

  • Strategic spiral momentum

    deciqAI/knowledge-skills/strategic-spiral-momentum Skill

    6★ repo

    Activate when: organization's strategy is losing momentum despite doing the right things; team disagrees on which strategic phase they're in; deciding whether to push deeper into current strategy or start a new cycle; setting phase-appropriate goals and resource allocation; preparing a mid-cycle board or investor assessment. Do NOT activate when: individual career or personal strategy planning (use shi-momentum); single-product feature prioritization; organization is in true crisis/turnaround mode. More: deciqai.com/s/strategic-spiral-momentum

  • Strategy execution levers

    deciqAI/knowledge-skills/strategy-execution-levers Skill

    6★ repo

    Activate when: 'our strategy is clear but nothing changes,' 'people understand the goal but revert to old behaviors,' 'initial launch energy faded after 2 months,' 'we keep having the same post-mortem findings,' or execution consistently falls short despite repeated planning. Do NOT activate when: the strategy itself is wrong or unvalidated (fix the strategy first); or failure is caused by resource constraints, not behavioral/process gaps. More: deciqai.com/s/strategy-execution-levers

  • Swot analysis

    deciqAI/knowledge-skills/swot-analysis Skill

    6★ repo

    Activate when: user says 'SWOT', 'our strengths and weaknesses', 'internal/external analysis', 'strategic audit', 'what's our edge', 'competitive threats we face', or is beginning a strategy planning cycle, evaluating market entry, or preparing investor materials. Do NOT activate when: user needs a purely quantitative financial model or precise numerical decision (use financial analysis instead); user wants to map competitive industry structure forces (use Porter's Five Forces instead). More: deciqai.com/s/swot-analysis

  • Travel trip contingency planning

    deciqAI/knowledge-skills/travel-trip-contingency-planning Skill

    6★ repo

    Activate when: building a complex/high-value itinerary; multi-supplier or international trip; hurricane/advisory season; client asks 'what if something goes wrong?'; designing a group/FIT trip. Do NOT activate when: single refundable booking with trivial exposure. More: deciqai.com/s/travel-trip-contingency-planning

  • Blue ocean strategy

    l4ci/latticework/skills/blue-ocean-strategy Skill

    6★ repo

    Use when the user wants a Blue Ocean Strategy analysis of a business or product, or asks how to stop competing on the same factors as everyone else and create uncontested market space. Maps the industry's strategy canvas, then fans out four parallel subagents (eliminate, reduce, raise, create) to build a new value curve through value innovation, then synthesizes the blue-ocean move and its risks into a detailed markdown report. Triggers include "Blue Ocean", "value innovation", "ERRC", "four actions framework", "strategy canvas", "uncontested market", "stop competing on the same factors".

  • Digital maturity assessment

    l4ci/latticework/skills/digital-maturity-assessment Skill

    6★ repo

    Use when the user wants to assess an organization's digital maturity across strategy, customer experience, technology, data, operations, people and culture, and innovation, scoring each on a five-level scale and producing a gap analysis and roadmap. Fans out parallel assessor subagents per dimension, then synthesizes the maturity profile, the binding gaps, and a sequenced roadmap in a detailed markdown report. Triggers include "digital maturity", "digital maturity assessment", "how digitally mature are we", "digital transformation readiness", "maturity model".

  • Fermi estimation

    l4ci/latticework/skills/fermi-estimation Skill

    6★ repo

    Use when the user needs a defensible quantitative estimate of something with no data at hand, and wants a reasoned order-of-magnitude answer rather than a blind guess or a refusal. Runs Fermi estimation: defines the target quantity precisely, decomposes it in parallel into a chain of sub-factors each estimable to within an order of magnitude, estimates each factor as a range with its basis, multiplies the chain and propagates the uncertainty, then cross-checks the result against independent decompositions and known bounds and names the factor that dominates the error. Triggers include "Fermi estimate", "back of the envelope", "order of magnitude", "ballpark", "how many / how much / how big roughly", "estimate the market size", "we don't have data but need a number".

  • Mece decomposition

    l4ci/latticework/skills/mece-decomposition Skill

    6★ repo

    Use when the user wants to break a problem, question, metric, or topic into a clean structure with no overlaps and no gaps, or build an issue tree / logic tree. Generates competing MECE decompositions in parallel, selects the sharpest cut, builds the tree, then audits it for mutual exclusivity and collective exhaustiveness with parallel checkers. Triggers include "MECE", "mutually exclusive collectively exhaustive", "issue tree", "logic tree", "break this down", "structure this problem", "decompose".

  • Okr

    l4ci/latticework/skills/okr Skill

    6★ repo

    Use when the user wants to turn strategy into measurable goals using OKRs (Objectives and Key Results), the goal-setting method from Andy Grove at Intel and popularized by John Doerr in Measure What Matters. Guides a drafting cycle: clarify a qualitative objective, draft 3-5 measurable key results, stress-test the key results with parallel critics, set ambition and cadence, and check alignment. Maintains an OKR document. Triggers include "OKR", "OKRs", "objectives and key results", "set quarterly goals", "Measure What Matters", "draft our objectives".

  • Pre mortem

    l4ci/latticework/skills/pre-mortem Skill

    6★ repo

    Use when the user wants to stress-test a plan, proposal, PRD, strategy, or decision before committing to it. Runs a prospective-hindsight pre-mortem by fanning out independent failure-finder subagents across distinct risk lenses, deduplicating and scoring the risks by likelihood and impact, then designing mitigations for the worst ones. Triggers include "pre-mortem", "red-team this plan", "what could go wrong", "stress-test this", "poke holes in this proposal".

  • Rice prioritization

    l4ci/latticework/skills/rice-prioritization Skill

    6★ repo

    Use when the user wants to rank a backlog of product initiatives or features by expected value per unit of effort using Intercom's RICE model. Calibrates the goal, the Reach time window, the Impact scale, the Confidence levels, and the Effort unit first, then estimates each initiative in parallel, one subagent per initiative, before computing RICE = (Reach × Impact × Confidence) / Effort, ranking, running a sensitivity check on Confidence and Effort, and recommending a roadmap order in a markdown report. Triggers include "RICE", "RICE score", "RICE prioritization", "prioritize the backlog", "rank these features", "what should we build first", "score our roadmap", "reach impact confidence effort".

  • Scenario planning

    l4ci/latticework/skills/scenario-planning Skill

    6★ repo

    Use when the user wants scenario planning for an uncertain future: framing a focal question, finding critical uncertainties, building a 2x2 of plausible futures, and deriving strategy that holds across them. Gathers driving forces and selects the two critical uncertainties as axes, then fans out four scenario-builder subagents in parallel (one per quadrant) to develop named narratives, and synthesizes robust versus contingent strategy with the signposts to monitor. Triggers include "scenario planning", "scenario analysis", "2x2 scenarios", "critical uncertainties", "what if the future", "plan for uncertainty".

  • Stakeholder analysis

    l4ci/latticework/skills/stakeholder-analysis Skill

    6★ repo

    Use when the user wants a stakeholder analysis or stakeholder map of a project, change, or decision, or asks who they need on board and how to engage them. Identifies the stakeholders, then fans out one analyst subagent per stakeholder in parallel to assess power, interest, current stance, interests and fears, and how to engage them, then synthesizes a power-interest grid, a per-quadrant engagement plan, the supporter coalition, the set of blockers, and the highest-leverage relationships to shift, in a detailed markdown report. Triggers include "stakeholder analysis", "stakeholder mapping", "power-interest grid", "power/interest matrix", "Mendelow", "stakeholder management", "who do we need on board".

  • Strategy kernel

    l4ci/latticework/skills/strategy-kernel Skill

    6★ repo

    Use when the user wants to build or test a real strategy for an organization, unit, or initiative, or to check whether an existing "strategy" is actually one. Captures the challenge, fans out competing diagnostician subagents to name the crux from different angles in parallel, then synthesizes the sharpest diagnosis into a kernel (diagnosis, guiding policy, coherent action) and audits the result against Rumelt's four hallmarks of bad strategy in a detailed markdown report. Triggers include "strategy kernel", "good strategy bad strategy", "Rumelt", "what's our strategy", "diagnosis guiding policy", "is this a real strategy".

  • Swot analysis

    l4ci/latticework/skills/swot-analysis Skill

    6★ repo

    Use when the user wants a SWOT analysis of a company, product, project, team, or decision, or asks to assess strengths, weaknesses, opportunities, and threats. Fans out four parallel analyst subagents (one per quadrant), grounds each factor in evidence and prioritizes it, then crosses the quadrants into a TOWS strategy matrix and a ranked set of strategic options in a detailed markdown report. Triggers include "SWOT", "SWOT analysis", "strengths and weaknesses", "TOWS", "analyze our position".

  • Chef menu event planning

    DedInc/chef-agentic-skills/skills/chef-menu-event-planning Skill

    6★ repo

    Menu, banquet, and event planning authority — designing multi-course and family-style menus, portion math per guest, cook-ahead timelines, plating and table serving, buffet vs plated logistics, and hosting without panic. Use whenever the user plans a dinner party, birthday, holiday table, banquet, or picnic, asks how much food for N guests, needs a day-before/day-of timeline, or wants restaurant-style plating at home.

  • Dev lifecycle

    tinhtran24/maestro/backend/internal/skillassets/dev-lifecycle Skill

    6★ repo

    Full-cycle delivery method for Maestro sessions — Analysis and Plan when a task is created, then Development and Testing, then a conventionally-named branch and Conventional Commit. Use when planning a task draft or driving a worker task from start to pull request.

  • Go to market

    samuelcastro/startup-skills/go-to-market Skill

    6★ repo

    Guide founders through launch planning and early traction strategies. Use when a founder says "How do I launch this?", "Help me get my first customers", "What's my go-to-market strategy?", "What's my GTM strategy?", "How do I get traction?", "Launch plan for my startup", "first 100 customers", "pre-launch waitlist", or asks about channel selection, launch execution, or early growth tactics.

  • Operations

    samuelcastro/startup-skills/operations Skill

    6★ repo

    Guide founders through startup operations including hiring, OKRs, and board management. Use when a founder says "help me write a job description", "how do I set OKRs", "create a board deck", "structure investor updates", "build a hiring plan", "interview scorecard", "quarterly planning", "team goals", "board meeting", or needs operational templates for running their startup.

  • Product

    samuelcastro/startup-skills/product Skill

    6★ repo

    Guide founders through product documentation, planning, and execution. Use when a founder says "help me write a PRD", "create a product roadmap", "write user stories", "prioritize features", "scope this feature", "product requirements", "acceptance criteria", "what should we build next", or needs to articulate product vision for teams or investors.

  • Legal matter brief

    davendra/uk-legal-skills/skills/legal-matter-brief Skill

    no license6★ repo

    State-of-the-matter brief consolidating legal posture across all documents, prior reviews, deadlines, and outstanding redlines for a single matter. Designed for partner check-ins, client updates, and pre-meeting prep.

  • Legal negotiate

    davendra/uk-legal-skills/skills/legal-negotiate Skill

    no license6★ repo

    Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

  • Domain modeling

    idaibin/skills/skills/domain-modeling Skill

    6★ repo

    Independent Agent Skills for repository analysis, planning, implementation, review, delivery, design, and runtime verification.

  • Product spec

    idaibin/skills/skills/product-spec Skill

    6★ repo

    Independent Agent Skills for repository analysis, planning, implementation, review, delivery, design, and runtime verification.

  • Ui spec

    idaibin/skills/skills/ui-spec Skill

    6★ repo

    Independent Agent Skills for repository analysis, planning, implementation, review, delivery, design, and runtime verification.

  • Backlog proposal

    loremaster-ai/loremaster/skills/backlog-proposal Skill

    6★ repo

    Use when the user asks to propose or create new backlog items from the PRD (e.g. "propose backlogs", "create backlog items for me", /backlog-propose) — proposes PRD-grounded candidates with externally verifiable done criteria, then creates in Jira only what a human selected and approved per item.

  • Resolve conflicts

    loremaster-ai/loremaster/skills/resolve-conflicts Skill

    6★ repo

    Use when team members have posted prose verdicts on open conflicts (via /resolve, a "resolve conflicts" request, or a direct spec-change request) to draft a PRD revision plus diff, apply it only after human button approval, and align downstream docs to the updated PRD (PRD = SoT); acts in the PM/SM role; verdict = human, edit = Loremaster proposal, apply = approval gate; never auto-overwrite; this channel = this project only.

  • Sprint planning

    loremaster-ai/loremaster/skills/sprint-planning Skill

    6★ repo

    Use on /sprint-planning or when the user asks for planning poker or story-point estimation: the AI seeds Fibonacci story-point estimates with grounded rationale and the team votes in a Slack thread, with the AI only proposing and humans finalizing, scoped to this channel's project only.

  • Pre call research brief

    amplemarket/skills/skills/pre-call-research-brief Skill

    no license6★ repo

    Generate a comprehensive, structured research brief before any sales call by combining person enrichment, company intelligence, CRM history, web research, and competitive analysis into a single actionable document.

    The same file is in 2 other repositories

  • Rep coaching brief

    amplemarket/skills/skills/rep-coaching-brief Skill

    no license6★ repo

    Generate coaching notes for a manager preparing a 1:1 with a rep, covering activity, engagement quality, conversion efficiency, and areas for improvement.

    The same file is in 2 other repositories

  • Sdr account prioritization plan

    amplemarket/skills/skills/sdr-account-prioritization-plan Skill

    no license6★ repo

    Help SDRs figure out which accounts to focus on and how to break into them -- combining internal engagement data with external signals to prioritize accounts and plan next moves.

    The same file is in 2 other repositories

  • Eronred monetization strategy

    JordanCoin/ios-skills-collection/skills/eronred--monetization-strategy Skill

    no license6★ repo

    When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.

    The same file is in 2 other repositories

  • Eronred rating prompt strategy

    JordanCoin/ios-skills-collection/skills/eronred--rating-prompt-strategy Skill

    no license6★ repo

    When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.

    The same file is in 2 other repositories

  • Momentum strategy

    kuhung/weread-book-skills/skills/momentum-strategy Skill

    6★ repo

    运用《动量策略》的核心方法论,指导量化交易模型的设计、回测和风险控制。适用于用户想要构建系统交易策略、评估回测结果、或进行投资组合配置时使用。

  • Options strategy

    kuhung/weread-book-skills/skills/options-strategy Skill

    6★ repo

    运用《麦克米伦谈期权》的核心方法论,指导期权策略设计与风险管理。适用于用户要设计期权交易策略(买方/卖方/价差/波动率交易)、评估期权组合的风险收益特性、用隐含波动率和认沽认购比做市场预测、以及管理期权头寸的资金和止盈止损时使用。

  • Strategy safari

    kuhung/weread-book-skills/skills/strategy-safari Skill

    6★ repo

    运用《战略历程》(Mintzberg) 的十大战略学派作为分析透镜审视战略问题。适用于用户要制定或评审公司/业务/个人战略、诊断战略规划为何沦为形式、拆解咨询报告或管理话术的理论出身与盲区、以及在深思熟虑与随机应变之间找平衡时使用。

  • Seo keyword research

    Muvon/octomind-tap/skills/seo-keyword-research Skill

    6★ repo

    Operational funnel for discovering high-intent, low-competition long-tail keywords (4+ word phrases with weak SERP defenders) — the keyword class that actually ranks for new and mid-authority sites without massive backlink spend. Encodes the discovery method (seed → modifier expansion → Google autocomplete + 'People Also Ask' + Reddit/forum mining + competitor SERP-gap), the qualification rubric that goes beyond KD scores (top-10 SERP authority profile, content-fit gap, intent match, traffic-potential vs ranking-realism, query freshness), the 2026 GEO overlay (definition + question + comparison queries that earn AI-search citations), and the kill-rules (head-term traps, fake-volume keywords, branded-SERPs, paid-ads-dominated SERPs). Use BEFORE writing any content brief, calendar, or pillar-cluster plan. Stays in the SEO lane: produces a keyword brief — content writing, on-page wrapping, and link-building are downstream concerns owned elsewhere.

  • Video spec sheet

    Muvon/octomind-tap/skills/video-spec-sheet Skill

    6★ repo

    Canonical reference for platform-by-platform video output specs: aspect ratio, length cap, codec, bitrate, frame rate, color, caption style and safe-zone bands. Use when picking output settings, validating an export, or spec-checking before publishing. Covers TikTok, Reels, Shorts, IG/FB feed, Stories, X, LinkedIn — all four format families: short-form vertical, square/feed, long-form 16:9, story 9:16.

  • Speckit analyze

    ldilov/harness-forge/skills/speckit-analyze Skill

    6★ repo

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

  • Speckit plan

    ldilov/harness-forge/skills/speckit-plan Skill

    6★ repo

    Execute the implementation planning workflow using the plan template to generate design artifacts.

  • Test strategy and coverage

    ldilov/harness-forge/skills/test-strategy-and-coverage Skill

    6★ repo

    Define right-sized test layers and coverage priorities for a change.

  • Scoping

    zenml-io/skills/skills/zenml-scoping/skills/scoping Skill

    6★ repo

    Scope and decompose ML workflow ideas into realistic ZenML pipeline architectures. Runs an in-depth interview to help users break down ambitious or over-engineered plans into well-composed multi-pipeline setups, identify what belongs in a pipeline vs. what doesn't, define cross-pipeline data flow via the Model Control Plane, and select an MVP to build first. Produces a pipeline_architecture.md specification document. Use this skill whenever a user describes a complex ML workflow, mentions multiple pipelines, talks about end-to-end ML platforms, asks how to structure their ML system in ZenML, or seems to be over-engineering their pipeline design. Also use when the user's pipeline idea sounds like it's trying to do too many things at once, or when they ask about composing pipelines together. Even if the user just says "I want to build an ML pipeline" with a long list of requirements, this skill helps scope it down before the pipeline-authoring skill takes over.