agentsclimarketplace

Plan & spec

10,807 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

  • New adr

    eugenelim/agent-ready-repo/.agents/skills/new-adr Skill

    31★ repo

    Use this skill when the user asks to create, write, draft, or open a new ADR (architecture decision record). Triggers on phrases like "new ADR", "write an ADR for...", "record this decision", "let's ADR this". Do NOT use for RFCs (use `new-rfc`) or feature specs (use `new-spec`).

  • New guide

    eugenelim/agent-ready-repo/.agents/skills/new-guide Skill

    31★ repo

    Create or substantially revise user guides, pack pages, and journey pages using Diátaxis plus conversation-first UX. Use when asked to write, simplify, restructure, audit, or modernize tutorials, how-to guides, reference pages, explanations, pack pages, or journey pages so readers can start from a natural-language goal, see what to say, understand what happens next, and reach an outcome without learning internal skill names first. Do NOT use for feature contracts (use `new-spec`), cross-cutting proposals (use `new-rfc`), recording decisions (use `new-adr`), minor single-line edits (normal PR), contributor docs, docstrings, release notes, or blog posts.

  • New rfc

    eugenelim/agent-ready-repo/.agents/skills/new-rfc Skill

    31★ repo

    Use this skill when the user asks to propose, draft, or open an RFC, update the rules, amend the charter, change our principles, or change the convention for something; also use it for follow-on RFC artifacts after acceptance. Triggers on "RFC", "propose a change to...", "let's get input on...", "draft a proposal", "create the follow-on specs for RFC-NNNN", "generate ADRs for the accepted RFC", and "implement the follow-on work from an RFC". Do NOT use for a settled architectural decision (use `new-adr`, including a superseding ADR), or for a standalone settled feature spec (use `new-spec`).

  • New spec

    eugenelim/agent-ready-repo/.agents/skills/new-spec Skill

    31★ repo

    Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).

  • Receive brief

    eugenelim/agent-ready-repo/.agents/skills/receive-brief Skill

    31★ repo

    Use this skill when the user has an existing externally-authored, multi-feature product brief -- a PRD, a solution handoff, a requirements packet -- and needs to mark it Ready or turn confirmed slices into shippable specs. Triggers on "receive a brief", "decompose this PRD", "we got a product brief", "break this handoff into specs". Elicits the load-bearing fields without mandating a schema, passes a Ready gate even with zero specs, and invokes new-spec only for confirmed slices. Do NOT use to author a single feature from scratch (use new-spec) or to record a decision (use new-adr).

  • Rfc status

    eugenelim/agent-ready-repo/.agents/skills/rfc-status Skill

    31★ repo

    Surface the current RFC landscape at a glance — how many RFCs are in each lifecycle state, which are active, and how many findings are waiting in the candidate register. Triggers on 'rfc status', 'show rfcs', 'what rfcs are open', 'rfc dashboard', 'how many rfcs', 'rfc candidates', 'rfc report', or any request for an overview of the RFC landscape. Read-only: never creates or modifies RFC files.

  • Work loop

    eugenelim/agent-ready-repo/.agents/skills/work-loop Skill

    31★ repo

    Use when implementing or resuming a non-trivial repository change: a feature, behavior-changing fix, refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under `docs/specs/`. Also use for bare continuation commands ('resume', 'continue', 'keep going', 'pick up where I left off', 'let's get going') when conversation or workspace context identifies active build work. Do not use for shaping, research, strategy, product planning, design exploration, monitoring or status-only work, review-only, explanation-only, specification-authoring-only, spike-only or throwaway exploration, or trivial edits that are cosmetic, tightly local, behavior-preserving, and have obvious verification.

  • Architect diagram

    eugenelim/agent-ready-repo/packs/architect/.apm/skills/architect-diagram Skill

    31★ repo

    The complete AI operating model for software teams — from first idea to production. Three peer-supervised loops (discovery → build → release) over a catalogue of curated packs: skills, subagents, and hooks, each installed in one line. It's npm for your coding agent. Any agent, any stack — Claude Code, Codex, Cursor, Copilot, Gemini, Kiro.

  • Jira align brief intake

    eugenelim/agent-ready-repo/packs/atlassian/.apm/skills/jira-align-brief-intake Skill

    31★ repo

    Use this skill when the user points at a Jira Align Feature and asks you to turn it into a product brief or shippable specs — "intake Feature 1234", "turn JA feature 789 into specs", "pull this Jira Align feature into a brief". The skill fetches the Feature and its child stories/tasks/defects via the `jira-align` skill, maps them onto a Shape B product brief (Feature title/description → Outcome, children → `US-n` user stories tagged with their Jira Align IDs, Feature ID → `Epic:` provenance pointer), writes it to `docs/product/briefs/<slug>.md`, and hands off to `receive-brief` to elicit gaps, decompose, and build. 1-way intake only — never writes back to Jira Align. Use the field mapping in `references/field-mapping.md` (customize for your org before first use). Do NOT use for defects (use `jira-defect-flow` for Jira defects) or for individual Jira issues (use `jira-brief-intake` for Jira epics).

  • Jira brief intake

    eugenelim/agent-ready-repo/packs/atlassian/.apm/skills/jira-brief-intake Skill

    31★ repo

    Use this skill when the user points at a Jira epic (or a board / sprint / JQL selection of issues) and wants it turned into shippable specs -- "turn PROJ-100 into specs", "decompose this epic", "we plan kanban-style in Jira, break this epic into a product brief". The skill pulls the epic and its children via the `jira` skill, maps them onto a product brief (epic -> Outcome, child issues -> Shape B user stories tagged with their Jira key, epic key -> `Epic:` pointer), writes it to `docs/product/briefs/<slug>.md`, and hands off to the `receive-brief` skill to elicit gaps, decompose, and build. Do NOT use for a single feature (use `new-spec`) or a defect (use `jira-defect-flow`).

  • Author brief

    eugenelim/agent-ready-repo/packs/core/.apm/skills/author-brief Skill

    31★ repo

    Use this skill when the user has unstructured external input (an email thread, a prose description, a Linear Issue, a stakeholder message) and needs to produce a DoR-compliant product brief and queue it in workspace.toml. Triggers on "author a brief", "write a brief from this email", "create a brief from this Linear issue", "intake this brief", "turn this into a brief". Do NOT use to decompose an existing brief into specs (use receive-brief) or to author a single feature from scratch (use new-spec).

  • New spec

    eugenelim/agent-ready-repo/packs/core/.apm/skills/new-spec Skill

    31★ repo

    Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).

  • Receive brief

    eugenelim/agent-ready-repo/packs/core/.apm/skills/receive-brief Skill

    31★ repo

    Use this skill when the user receives an externally-authored, multi-feature product brief -- a PRD, a solution handoff, a requirements packet -- and needs to turn it into shippable specs. Triggers on "receive a brief", "decompose this PRD", "we got a product brief", "break this handoff into specs". Elicits the load-bearing fields without mandating a schema, decomposes by shippability, and executes each slice through new-spec then work-loop. Do NOT use to author a single feature from scratch (use new-spec) or to record a decision (use new-adr).

  • Work loop

    eugenelim/agent-ready-repo/packs/core/.apm/skills/work-loop Skill

    31★ repo

    Use when implementing or resuming a non-trivial repository change: a feature, behavior-changing fix, refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under `docs/specs/`. Also use for bare continuation commands ('resume', 'continue', 'keep going', 'pick up where I left off', 'let's get going') when conversation or workspace context identifies active build work. Do not use for shaping, research, strategy, product planning, design exploration, monitoring or status-only work, review-only, explanation-only, specification-authoring-only, spike-only or throwaway exploration, or trivial edits that are cosmetic, tightly local, behavior-preserving, and have obvious verification.

  • Build outline

    eugenelim/agent-ready-repo/packs/desk-research/.apm/skills/build-outline Skill

    31★ repo

    Decompose a research question into the sub-questions a thorough answer must address. Builds the outline that `/source-map` then populates and `/desk-research` then synthesises against. Grounded in STORM's outline stage (multi-perspective topic decomposition) and PRISMA's PICO framework (Population, Intervention, Comparison, Outcome — the systematic-review decomposition). Produces `<topic-slug>-outline.md` listing each sub-question with a brief rationale. Depth cues — `quickly`, `top three`, `briefly`, `summary only` for the must-answer few; `comprehensively`, `exhaustively`, `in depth`, `extensive` to chase second-order sub-questions.

  • Desk research project synthesize

    eugenelim/agent-ready-repo/packs/desk-research/.apm/skills/desk-research-project-synthesize Skill

    31★ repo

    Synthesize a research project into its typed verdict and a self-contained governance brief. Triggers on project-lifecycle phrasing — "synthesize the project", "write up the findings", "produce the brief" — inside an existing project folder. Reads synthesis-matrix.md + memos.md and writes BOTH the project's own typed synthesis (<type>.md, named by the project's shape) AND a single-file <topic-slug>-brief.md that governance can lift whole into an RFC. Applies GRADE confidence + ≥3-source triangulation; warns when the matrix is empty (digest was skipped). The brief is answer-first, self-contained, cited and per-finding confidence-tagged, with a Known unknowns section. Prompt-only: advances no phase on its own.

  • Github brief intake

    eugenelim/agent-ready-repo/packs/github/.apm/skills/github-brief-intake Skill

    31★ repo

    Use this skill when the user points at a GitHub Milestone and wants it turned into shippable specs — "turn our Q3 milestone into specs", "intake this milestone as a brief", "we track work in GitHub Issues, pull milestone v2-launch into the spec pipeline". The skill pulls the milestone and its issues via the `gh` CLI, maps them onto a product brief (milestone title -> Outcome draft, open and closed issues -> Shape B user stories tagged with their issue number, milestone URL -> `Epic:` provenance pointer), writes it to `docs/product/briefs/<slug>.md`, and hands off to the `receive-brief` skill to elicit gaps, decompose, and build. Do NOT use for a single issue without a milestone (use `new-spec`) or when the user wants to pull multiple repos (this skill is single-repo, single-milestone).

  • New adr

    eugenelim/agent-ready-repo/packs/governance-extras/.apm/skills/new-adr Skill

    31★ repo

    Use this skill when the user asks to create, write, draft, or open a new ADR (architecture decision record). Triggers on phrases like "new ADR", "write an ADR for...", "record this decision", "let's ADR this". Do NOT use for RFCs (use `new-rfc`) or feature specs (use `new-spec`).

  • New rfc

    eugenelim/agent-ready-repo/packs/governance-extras/.apm/skills/new-rfc Skill

    31★ repo

    Use this skill when the user asks to propose, draft, or open an RFC, OR when generating follow-on implementation artifacts (specs, ADRs) for an already-Accepted RFC. Triggers on "RFC", "propose a change to...", "let's get input on...", "draft a proposal", "create the follow-on specs for RFC-NNNN", "generate ADRs for the accepted RFC", "implement the follow-on work from an RFC". Do NOT use for recording a standalone architectural decision outside an RFC context (use `new-adr`), or for authoring a spec with no associated Accepted RFC (use `new-spec` for standalone spec authoring; for RFC follow-on work, invoke this skill first).

  • Rfc status

    eugenelim/agent-ready-repo/packs/governance-extras/.apm/skills/rfc-status Skill

    31★ repo

    Surface the current RFC landscape at a glance — how many RFCs are in each lifecycle state, which are active, and how many findings are waiting in the candidate register. Triggers on 'rfc status', 'show rfcs', 'what rfcs are open', 'rfc dashboard', 'how many rfcs', 'rfc candidates', 'rfc report', or any request for an overview of the RFC landscape. Read-only: never creates or modifies RFC files.

  • Linear brief intake

    eugenelim/agent-ready-repo/packs/linear/.apm/skills/linear-brief-intake Skill

    31★ repo

    Use this skill when the user points at a Linear Issue or Project and wants it turned into a shippable product brief — "turn LIN-123 into a brief", "create a brief from this Linear project". Pulls the issue or project via the `linear` skill, maps fields onto a product brief per the fixed mapping (issue.title + issue.description → Outcome verbatim; issue.children → US-n stories tagged with their identifier; issue.project.url → Epic: provenance pointer), writes to `docs/product/briefs/<slug>.md`, registers under [brief_queue].draft in workspace.toml, and hands off to `receive-brief`. For projects with >10 issues, surfaces the count and asks PE to filter before proceeding.

  • Linear brief sync

    eugenelim/agent-ready-repo/packs/linear/.apm/skills/linear-brief-sync Skill

    31★ repo

    Use this skill when you want to catch up an existing product brief with changes in the linked Linear Issue — "sync the brief with LIN-123", "the Linear issue has been updated, update the brief". Re-fetches the Issue via the `linear` skill, diffs only the Linear-sourced fields (Outcome and User stories) against the current brief, presents section-level before/after for PE approval, and writes only the approved changes. Never touches PE-authored fields (Scope/Non-goals, Appetite, Rabbit holes, Instrumentation, Success metrics). Refuses when brief Status is Executing.

  • Decompose intent

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/decompose-intent Skill

    31★ repo

    Use when a de-risked intent needs breaking into the next level down — child intents, or a shippable spec/slice at the leaf — and optionally projecting onto a tracker. Triggers on "decompose this", "break this down", "slice this", "what specs come out of this", "push this to Linear/Jira". Recursive (one level at a time); at app scale the leaf is an ordinary `core` brief. Do NOT use to author an intent (use `frame-intent`) or to test a bet (use `de-risk-intent`).

  • Discovery loop

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/discovery-loop Skill

    31★ repo

    Use to turn a raw product idea into a ratified, build-ready decision brief — the upstream discovery loop run by the discovery-lead agent. Triggers on "scaffold the product vision for X", "run a discovery for X", "diverge on the product shape then converge to a brief", "take this idea to a decision brief", "resume the X discovery". It diverges across candidate product shapes, converges the chosen one through a research/product/UX/architecture/safety lens roster, pauses at the consent gates (G0 vision, G1.5 altitude/MVP, G2 the "what"), emits a connected hypothesis with validation hooks, and hands off to work-loop at G3 — with no new engine, scheduler, or service. Do NOT use to build a spec (use new-spec → work-loop), to ship one (the release loop), or to author one discovery artifact standalone (use frame-intent / frame-domain / explore-options directly).

  • Explore options

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/explore-options Skill

    31★ repo

    Use to generate multiple candidate product shapes before the discovery loop converges on one — the divergence stage that guards against myopic-greedy commitment. Triggers on "give me candidate product shapes", "diverge on the product shape", "what are the options before we commit", "explore alternatives for X", "don't converge yet". Generates N candidates across altitude × mechanic, each with its riskiest assumption, then frames an explicit compare-and-choose. Do NOT use to break down a chosen approach (use `decompose-intent`), to critique one produced artifact (use `devils-advocate`), or to converge (that is the discovery loop's job).

  • Frame intent

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/frame-intent Skill

    31★ repo

    Use when shaping a piece of product work before it becomes a spec — turning an idea, a request, or a strategy into a level-tagged `intent` (an outcome + the opportunity behind it). Triggers on "shape this", "what's the intent here", "frame the problem", "before we build X", "turn this into a brief/PRD". Authors an `intent` at any altitude in the open recognized set — product-vision, product-strategy, capability, or feature — resolves Scale (app ↔ business-unit) at intake, and offers current-state inputs only when brownfield. Do NOT use to test an assumption (use `de-risk-intent`) or to break an intent down (use `decompose-intent`).

  • Map capabilities

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/map-capabilities Skill

    31★ repo

    Step 6 (terminal) of the PE six-step shaping sequence. Translates a committed bet into a Capability Map — L1 domain organisation, Wardley × strategic-criticality annotation, Build/Buy/Partner/Adopt disposition, and a Build-only suggested build sequence anchoring M3–M6 spec-writing. Run after `place-bet`. Triggers on "map our capabilities", "what do we need to build", "what's our build/buy split", "capability areas for this bet". Do NOT use for a single feature (use `frame-intent`) or to author a brief (use `lean-canvas` / `author-brief`).

  • Plan validation

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/plan-validation Skill

    31★ repo

    Use to turn a converged product's load-bearing assumptions into a validation plan — and to scaffold the primary-research instruments that would test them. Triggers on "plan the validation", "how do we validate these assumptions", "turn assumptions into a validation plan", "scaffold an interview guide / usability test", "what would confirm this". Produces assumption → kill-condition → real-world-activity hooks and the instrument scaffolds (interview guide, usability-test plan, transcript-synthesis frame). Do NOT use to run the sessions (out of charter — a human runs them), to test a single bet (use `de-risk-intent`), or to converge (the discovery loop's job).

  • Define content strategy

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/define-content-strategy Skill

    31★ repo

    Use when a strategist needs to set the organizational content direction before content design begins — the governance and structural layer above per-surface content execution. Triggers on "define the content strategy", "I need to set the content strategy before content design", "content governance framework", "Halvorson content strategy", "Purpose Process Structure Governance". Produces a committed content-strategy.md. Do NOT use to write per-surface content or microcopy — that belongs to the content-design skill in the experience-design pack.

  • Define ux strategy

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/define-ux-strategy Skill

    31★ repo

    Use when a strategist needs to set the experience direction before design begins — the bridge between business goals and what the designed product must achieve. Triggers on "define the UX strategy", "I need to set the experience strategy before design", "what should our UX strategy be", "align design to business goals", "set the experience vision". Produces a committed ux-strategy.md. Do NOT use to produce a customer journey map — that belongs to journey-mapping in the experience-design pack.

  • Run okr cascade

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/run-okr-cascade Skill

    31★ repo

    Use when a strategist needs to cascade company OKRs to team level and identify strategic gaps for the product-engineering shaping queue. Triggers on "run an OKR cascade", "I need to cascade company OKRs", "align team OKRs to company goals", "identify OKR gaps", "what are we missing to hit our objectives". Produces okr-cascade.md and workspace.toml shaping-queue entries. Do NOT use for per-feature goal-setting — cascade is org-wide alignment, not product backlog prioritization.

  • Run swot

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/run-swot Skill

    31★ repo

    Use when a strategist needs a structured situation synthesis before committing to a strategic direction. Triggers on "run a SWOT", "I need to understand our position", "situation synthesis before setting strategy", "what are our strengths and weaknesses", "map out opportunities and threats". Produces a committed SWOT artifact. Do NOT use as a substitute for market data — SWOT organizes what you know; it does not generate evidence you don't have.

  • Synthesize stakeholder research

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/synthesize-stakeholder-research Skill

    31★ repo

    Use when a strategist needs to turn existing stakeholder research into a strategic narrative organized by theme. Triggers on "synthesize stakeholder research", "I need to turn research into strategic direction", "what does the research tell us strategically", "consolidate stakeholder perspectives", "research synthesis for strategy". Requires existing research inputs — surfaces a diagnostic when none are found. Do NOT use to conduct research — this skill synthesizes; it does not interview, survey, or produce primary research.

  • New guide

    eugenelim/agent-ready-repo/packs/user-guide-diataxis/.apm/skills/new-guide Skill

    31★ repo

    Create or substantially revise user guides, pack pages, and journey pages using Diátaxis plus conversation-first UX. Use when asked to write, simplify, restructure, audit, or modernize tutorials, how-to guides, reference pages, explanations, pack pages, or journey pages so readers can start from a natural-language goal, see what to say, understand what happens next, and reach an outcome without learning internal skill names first. Do NOT use for feature contracts (use `new-spec`), cross-cutting proposals (use `new-rfc`), recording decisions (use `new-adr`), minor single-line edits (normal PR), contributor docs, docstrings, release notes, or blog posts.

  • Development estimation

    NickCrew/Claude-Cortex/skills/development-estimation Skill

    30★ repo

    Use when estimating time, effort, or complexity for features or projects - provides structured estimation workflows with breakdowns, risks, and confidence intervals.

  • Knowledge stack

    NickCrew/Claude-Cortex/skills/knowledge-stack Skill

    30★ repo

    Use this skill whenever working inside any of Nick's repos (under ~/Developer/) or whenever a conversation touches Nick's durable cross-cutting work — Atlas Crew product strategy/brand/planning, the Unanet job, job search, interviews, tax amendment, foreclosure/tenant situation, strategic positioning. Maps Nick's three Basic Memory projects (products, work, main) and the per-repo dev trackers, and says which layer owns which kind of question. Consult before reasoning from stored memory summaries about repo architecture, product decisions, active priorities, or ongoing personal/career state — stored memory is lossy; the trackers and the Basic Memory projects are the real artifacts and should be consulted first.

  • Openapi specification

    NickCrew/Claude-Cortex/skills/openapi-specification Skill

    30★ repo

    OpenAPI 3.x specification design, schema patterns, and validation for REST API contracts. Use when creating or maintaining API specifications, generating documentation, or validating API contracts.

  • Product manager

    NickCrew/Claude-Cortex/skills/product-manager Skill

    30★ repo

    Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.

  • Product strategy

    NickCrew/Claude-Cortex/skills/product-strategy Skill

    30★ repo

    Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.

  • Requirements discovery

    NickCrew/Claude-Cortex/skills/requirements-discovery Skill

    30★ repo

    Stakeholder interviews, PRD structure, and scope definition for software requirements elicitation. Use when gathering requirements, defining project scope, or structuring product requirement documents.

  • Entity resolution strategy selector

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/knowledge-representation/entity-resolution-strategy-selector Skill

    30★ repo

    Choose HOW to decide when two records are the same real-world entity — EVIDENCE-BASED resolution (deterministic feature-by-feature scoring with explainable evidence and culturally-robust rules) vs GENERALIZATION-BASED AI (LLM statistical similarity, nondeterministic, post-hoc rationalization) — per Ch3 "Entity Resolution: The Foundation of Agent Knowledge". Scores a six-factor requirement profile and picks evidence-based, generalization-AI, or a hybrid; ships a deterministic matcher that scores name/address/phone similarity into an explainable confidence, classifies the resulting graph edge, and flags the edge cases naive matching misses. Use when standing up entity resolution for an agent knowledge graph, justifying an evidence-vs-LLM choice for identity/compliance/fraud work, or auditing a proposed merge. NOT for the extraction stage that produces the records (that is upstream KG construction), NOT for picking a specific ER product, NOT for arity-2 relationship modeling (use graph-model-selector).

  • Constraint guided plan validator

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/constraint-guided-plan-validator Skill

    30★ repo

    Validate a generated plan against extracted domain constraints AND the agent's capability model before execution (Ch5 Constraint-guided planning, Example 5-14, plus the DevOps hypothesis-formation capability filter). Scores the plan 0..1, returns structured per-step feedback so a planning node can refine when the score falls below threshold, and filters steps the agent is not authorized to perform (e.g. a step needing write access when the agent holds read-only monitoring). Forbidden-action and capability violations are HARD — a plan the agent cannot legally execute does not pass regardless of score. Use in regulated or capability-bounded environments where plans must respect business rules and operational authority before any action runs. NOT for free-form creative tasks with no constraints, NOT for validating execution results after the fact (this gates the plan, not the outcome), NOT as the constraint extractor itself (it consumes extracted constraints).

  • Investigation dag planner

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/investigation-dag-planner Skill

    30★ repo

    Dynamic-DAG construction for a planning node (Ch5 Example 5-15 + the DevOps "Constructing the Investigation DAG" section). Given hypotheses/tasks with dependency constraints, compute a topological-level decomposition: each level is a phase of tasks that can run concurrently, ordered within-phase by priority. The estimated duration of a parallel phase is the MAX over its concurrent tests, and execution runs phase-by-phase with early termination once a hypothesis is confirmed. Detects dependency cycles as malformed plans. Use when a planning node must decide which work is parallel-safe and in what order — incident-investigation hypothesis testing, multi-track research, multi-party claim processing. NOT for purely linear pipelines (one task per level — annotation overhead exceeds benefit), NOT for runtime fault-isolation (that is event-driven orchestration), NOT for picking a model or pipeline shape (that is architecture selection).

  • To spec

    tt-a1i/matt-skills-with-to-goal/skills/to-spec Skill

    30★ repo

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    The same file is in 11 other repositories

  • To tickets

    tt-a1i/matt-skills-with-to-goal/skills/to-tickets Skill

    30★ repo

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    The same file is in 5 other repositories

  • Business analyst

    saeed-vayghan/gemini-agent-skills/.gemini/skills/business-analyst Skill

    30★ repo

    Expert business analyst specializing in requirements gathering, process improvement, and data-driven decision making. Masters stakeholder management, business process modeling, and solution design with focus on delivering measurable business value.

  • Product manager

    saeed-vayghan/gemini-agent-skills/.gemini/skills/product-manager Skill

    30★ repo

    Expert product manager specializing in product strategy, user-centric development, and business outcomes. Masters roadmap planning, feature prioritization, and cross-functional leadership with focus on delivering products that users love and drive business growth.

  • Documentation criteria

    shinpr/codex-workflows/.agents/skills/documentation-criteria Skill

    30★ repo

    Documentation creation criteria for PRD, ADR, Design Doc, UI Spec, and Work Plan with templates. Use when: creating or reviewing technical documents, determining which documents are required, or following document templates.

  • Recipe front plan

    shinpr/codex-workflows/.agents/skills/recipe-front-plan Skill

    30★ repo

    Create frontend work plan from design document with test skeleton generation.

  • Recipe plan

    shinpr/codex-workflows/.agents/skills/recipe-plan Skill

    30★ repo

    Creates a reviewed Work Plan with value-filtered integration/E2E test skeletons. Use when planning implementation from a Design Doc.

  • Recipe update doc

    shinpr/codex-workflows/.agents/skills/recipe-update-doc Skill

    30★ repo

    Update existing design documents (Design Doc / PRD / ADR) with review and consistency verification.

  • Planning and task breakdown

    pimenov/codex-first-skills-pack/skills/planning-and-task-breakdown Skill

    no license29★ repo

    Turns ambiguous, large, multi-step, or handoff-prone work into sequenced tasks with outcomes, dependencies, stop-lines, acceptance criteria, and the right durable layer. Use when planning a feature, bugfix campaign, refactor, migration, deploy prep, client/internal work packet, Linear issue set, or when the user asks to break down, plan, scope, make tasks, prepare execution, or decide the next safe steps before implementation.

  • Spec driven development

    pimenov/codex-first-skills-pack/skills/spec-driven-development Skill

    no license29★ repo

    Defines the implementation contract before planning or coding so work is built against explicit goals, users, scope, non-goals, assumptions, acceptance criteria, and verification. Use when creating or changing a feature, product workflow, API, integration, migration, user-facing behavior, cross-team handoff, or any task where Codex could implement the wrong thing correctly; when the user asks for a spec, requirements, PRD, contract, acceptance criteria, or "what exactly are we building".

  • Plan

    launchdarkly/ai-tooling/skills/onboarding/sdk-install/plan Skill

    no license29★ repo

    Generate a minimal LaunchDarkly SDK integration plan from detected stack: choose SDK type(s), dual-SDK server+client when required, files to change, env conventions. Nested under sdk-install; follows detect, precedes apply.

    The same file is in 1 other repository

  • Product photography

    sanky369/vibe-building-skills/skills/creative/product-photography Skill

    29★ repo

    Produces professional AI product photography — clean e-commerce shots, lifestyle scenes, hero images, macro detail shots, and flat lays — as generation-ready prompt specs, and generates the files via FAL.ai fal-ai/nano-banana-pro when the automation is configured. Use when the user says 'product photos', 'shots of my product', 'images for my store / listing / landing page', 'hero image for my product', 'lifestyle photos', or shares a product needing marketing imagery. Produces one prompt-spec block per shot (shot type, lighting, background, composition, aspect ratio, negative constraints) with a shot list, variant plan, and file-naming conventions; runs docs/creative_cli.py product when FAL_API_KEY is set.

  • Talking head

    sanky369/vibe-building-skills/skills/creative/talking-head Skill

    29★ repo

    Plan presenter-led and UGC-style videos: choose the presenter archetype, define styling, setting, lighting, and framing, write the hook/body/CTA script skeleton, and produce keyframe prompts for the repo's FAL.ai pipeline. Use whenever the user wants a talking-head video, presenter video, UGC ad, testimonial, founder video, explainer with a person on camera, spokesperson content, or 'someone talking about my product' — even if they just say 'I need a video of a person explaining this'. Produces a Talking Head Video Spec: presenter definition, look/setting/lighting/framing decisions, timed script skeleton, and generation-ready keyframe prompts for fal-ai/nano-banana-pro.

  • Seo content

    sanky369/vibe-building-skills/skills/marketing/seo-content Skill

    29★ repo

    Write a publish-ready, search-optimized article for a target keyword: SERP-validated brief, full draft matched to search intent, on-page metadata (title tag, meta description, URL slug), and schema markup. Use when the user says 'write a blog post about X', 'write an article that ranks', 'create SEO content', 'I need content for this keyword', or hands over a keyword/content brief from an SEO plan — even if they never say 'SEO'. Also use to rewrite or upgrade an existing article that isn't ranking. Produces the complete article plus a metadata block and an on-page checklist result.

  • Seo strategy

    sanky369/vibe-building-skills/skills/marketing/seo-strategy Skill

    29★ repo

    Build a complete, prioritized SEO strategy for a site: topical authority map, winnable-keyword shortlist, content production pipeline, link-building plan, and technical baseline. Use when the user wants to grow organic traffic, asks 'how do I rank on Google', 'why isn't my site getting traffic', 'build me an SEO plan/strategy', 'what keywords should I target', 'how do I get backlinks', or wants to audit or scale their SEO — even if they never say the word 'strategy'. Produces an SEO Strategy Document with a scored keyword shortlist, a phased action plan sequenced by dependency, and a measurement plan.

  • Fable like implementation

    sanky369/vibe-building-skills/skills/product-strategy/fable-like-implementation Skill

    29★ repo

    Use when the session model is Opus 4.8 (claude-opus-4-8) and the user asks to build, add, implement, refactor, migrate, or integrate something non-trivial — 3+ files, a new dependency or subsystem, an API contract or database schema change, or meaningful ambiguity or risk — or says "plan this out", "spec this", "how should we build", "create an implementation plan". Also use when the user says "just implement it" but the work is non-trivial. Do NOT use on Claude Fable 5 or any other model, nor for one-line fixes, typo corrections, single-function changes, or questions that require no code change.

  • Sol orchestrator

    sanky369/vibe-building-skills/skills/product-strategy/sol-orchestrator Skill

    29★ repo

    Orchestrates non-trivial software implementation with GPT-5.6 Sol as the decision-making root and bounded Sol Light/Medium, Terra, Luna, GPT-5.5, and Claude Sonnet 5 executors. Use when the user asks to build, implement, integrate, migrate, refactor, or fix work spanning multiple files or systems; requests parallel agents or an implementation plan; or needs evidence-backed execution with specialist routing, review gates, and end-to-end validation. Produces a grounded specification, dependency-aware task graph, implemented changes when authorized, and a verified completion report. Skip trivial one-file changes and explanation-only requests.