agentsclimarketplace

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

  • Bmad create prd

    mannnrachman/pi-bmad/skills/bmad-create-prd Skill

    no license3★ repo

    DEPRECATED — consolidated into bmad-prd create intent - this skill will be removed in v7 in favor of `bmad-prd`.

  • Bmad dev story

    mannnrachman/pi-bmad/skills/bmad-dev-story Skill

    no license3★ repo

    Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

  • Bmad edit prd

    mannnrachman/pi-bmad/skills/bmad-edit-prd Skill

    no license3★ repo

    DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of `bmad-prd`.

  • Bmad prd

    mannnrachman/pi-bmad/skills/bmad-prd Skill

    no license3★ repo

    Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

  • Bmad product brief

    mannnrachman/pi-bmad/skills/bmad-product-brief Skill

    no license3★ repo

    Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

  • Bmad spec

    mannnrachman/pi-bmad/skills/bmad-spec Skill

    no license3★ repo

    Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec".

  • Bmad sprint planning

    mannnrachman/pi-bmad/skills/bmad-sprint-planning Skill

    no license3★ repo

    Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

  • Bmad validate prd

    mannnrachman/pi-bmad/skills/bmad-validate-prd Skill

    no license3★ repo

    DEPRECATED — consolidated into bmad-prd validate intent - this skill will be removed in v7 in favor of `bmad-prd`.

  • Pipa huddle beta

    lunchpaillola/pipa-skills/skills/pipa-huddle-beta Skill

    3★ repo

    Operational skills for the agents people already use.

  • Research plan implement

    wchen02/cursor-agent-learning/.cursor/skills/research-plan-implement Skill

    no license3★ repo

    Research codebase first, then plan, then implement. Use when the user has an unclear or large task and wants research before planning and implementation.

  • Depression screening

    rhavekost/clinical-toolkit/dist/consumer/claude/depression-screening Skill

    no license3★ repo

    Use when screening for depression symptoms (low mood, anhedonia, fatigue, sleep changes, appetite changes), assessing severity for treatment planning, tracking treatment response, or patient has positive PHQ-9 Item 9 (suicidal ideation). Provides PHQ-9 (comprehensive) and PHQ-2 (brief) assessments.

  • Motivation assessment

    rhavekost/clinical-toolkit/dist/consumer/claude/motivation-assessment Skill

    no license3★ repo

    Use when assessing readiness to change, planning behavioral interventions, or matching treatment approach to patient motivation. Provides URICA access guidance and a brief readiness ruler with stage-based guidance.

  • Suicide screening

    rhavekost/clinical-toolkit/dist/consumer/claude/suicide-screening Skill

    no license3★ repo

    Use when screening for suicide risk (suicidal thoughts, self-harm urges, hopelessness, plans or intent to die), patient has positive PHQ-9 Item 9, recent suicide attempt, psychiatric crisis, or establishing safety planning. Provides ASQ (brief) and C-SSRS Columbia Protocol (comprehensive risk assessment). Critical safety-focused.

  • Treatment planning

    rhavekost/clinical-toolkit/dist/consumer/claude/treatment-planning Skill

    no license3★ repo

    Use when developing treatment plans, writing SMART goals, determining appropriate level of care, implementing measurement-based care protocols, or adapting treatment based on patient progress. Provides SMART goals framework, ASAM/LOCUS criteria guidance, and treatment monitoring strategies.

  • Ultra brief screening

    rhavekost/clinical-toolkit/dist/consumer/claude/ultra-brief-screening Skill

    no license3★ repo

    Use when time is limited and you need a rapid combined depression and anxiety screen. Provides PHQ-4 (PHQ-2 + GAD-2) with interpretation and triage guidance.

  • Depression screening

    rhavekost/clinical-toolkit/skills/depression-screening Skill

    no license3★ repo

    Use when screening for depression symptoms (low mood, anhedonia, fatigue, sleep changes, appetite changes), assessing severity for treatment planning, tracking treatment response, or patient has positive PHQ-9 Item 9 (suicidal ideation). Provides PHQ-9 (comprehensive) and PHQ-2 (brief) assessments.

    The same file is in 2 other repositories

  • Motivation assessment

    rhavekost/clinical-toolkit/skills/motivation-assessment Skill

    no license3★ repo

    Use when assessing readiness to change, planning behavioral interventions, or matching treatment approach to patient motivation. Provides URICA access guidance and a brief readiness ruler with stage-based guidance.

    The same file is in 2 other repositories

  • Suicide screening

    rhavekost/clinical-toolkit/skills/suicide-screening Skill

    no license3★ repo

    Use when screening for suicide risk (suicidal thoughts, self-harm urges, hopelessness, plans or intent to die), patient has positive PHQ-9 Item 9, recent suicide attempt, psychiatric crisis, or establishing safety planning. Provides ASQ (brief) and C-SSRS Columbia Protocol (comprehensive risk assessment). Critical safety-focused.

    The same file is in 2 other repositories

  • Treatment planning

    rhavekost/clinical-toolkit/skills/treatment-planning Skill

    no license3★ repo

    Use when developing treatment plans, writing SMART goals, determining appropriate level of care, implementing measurement-based care protocols, or adapting treatment based on patient progress. Provides SMART goals framework, ASAM/LOCUS criteria guidance, and treatment monitoring strategies.

    The same file is in 2 other repositories

  • Ultra brief screening

    rhavekost/clinical-toolkit/skills/ultra-brief-screening Skill

    no license3★ repo

    Use when time is limited and you need a rapid combined depression and anxiety screen. Provides PHQ-4 (PHQ-2 + GAD-2) with interpretation and triage guidance.

    The same file is in 2 other repositories

  • Validate implementation plan

    b-mendoza/agent-skills/skills/validate-implementation-plan Skill

    no license3★ repo

    A collection of reusable skills for AI-assisted development workflows

    The same file is in 2 other repositories

  • Planning codebase restructuring

    b-mendoza/agent-skills/skills/planning-codebase-restructuring Skill

    no license3★ repo

    A collection of reusable skills for AI-assisted development workflows

    The same file is in 2 other repositories

  • Planning task execution

    b-mendoza/agent-skills/skills/planning-task-execution Skill

    no license3★ repo

    A collection of reusable skills for AI-assisted development workflows

    The same file is in 1 other repository

  • Planning work item tasks

    b-mendoza/agent-skills/skills/planning-work-item-tasks Skill

    no license3★ repo

    A collection of reusable skills for AI-assisted development workflows

    The same file is in 1 other repository

  • Plan grill

    i-stack/ai-coding-kit/skills-engineering/plan-grill Skill

    3★ repo

    需求对齐/盘问锁定计划。收到非平凡构建、修改或方案请求时,先评估是否存在无法从代码或上下文确定、且会实质改变结果的阻塞性决策;有则自动进入逐问盘问,无则直接回复或执行。显式 grill/锁定计划触发语始终强制进入。确认前不执行,产出 PLAN.md 供 cross-model-review 接力。基于 Matt Pocock 的 grilling(MIT)。

  • Customer research

    dirknicol/pmm-skills/skills/customer-research Skill

    3★ repo

    Use this skill when the user wants to plan, conduct, or synthesize customer research — interviews, surveys, win/loss, voice-of-customer, support ticket analysis, sales call mining, review analysis, or community listening. Triggers include any mention of 'customer research', 'customer interviews', 'voice of customer', 'VoC', 'win-loss', 'JTBD', 'jobs to be done', 'interview synthesis', 'research synthesis', 'review analysis', 'support ticket analysis', or 'qualitative research'. Implements a three-stage workflow: inputs (multi-source data) → AI processing + structure (transcribe, tag, cluster) → human synthesis (themes, decisions, recommendations). Reads `pmm-context.md` first. Outputs themed insight clusters with supporting quotes, a synthesis brief, and downstream recommendations. Do NOT use for quantitative-only market sizing or for persona artifact creation — `personas` skill handles persona output.

  • Launch

    dirknicol/pmm-skills/skills/launch Skill

    3★ repo

    Use this skill when the user is planning, scoping, or executing a product launch, feature announcement, or go-to-market moment. Triggers include any mention of 'launch', 'launching', 'GTM', 'go-to-market', 'release', 'product announcement', 'launch plan', 'launch tier', 'launch brief', 'launch checklist', 'Tier 1 launch', 'Tier 2 launch', 'Tier 3 launch', or 'rollout'. Determines launch tier based on market impact, novelty, and strategic importance — then builds a tier-appropriate plan covering messaging, audiences, channels, assets, timeline, internal alignment, and success metrics. Reads `pmm-context.md` and (if available) positioning and persona artifacts first. Outputs a launch brief, asset checklist, and 30/60/90-day measurement plan. Do NOT use for ongoing marketing campaigns or feature releases that aren't a launch moment — those are different workflows.

  • Askit migrate

    product-on-purpose/agent-skills-toolkit/skills/askit-migrate Skill

    3★ repo

    Assesses an existing skills repository against the Advanced Skill Library Standard, produces a staged bring-to-conformance plan, and writes the minimal canonical manifest so the repo becomes gradeable. Use when adopting a foreign or ad-hoc skills repo, migrating a Claude-only plugin toward cross-agent conformance, or planning a Bronze-to-Silver upgrade path.

  • Metrics instrumentation

    nemanli/ux-metrics-skills/skills/metrics-instrumentation Skill

    3★ repo

    Designs the tracking plan that captures the events behind a UX metric — event names, properties, naming conventions, taxonomy, PII rules, tool-agnostic schema. Triggers on "tracking plan", "event taxonomy", "what should we log", "event naming convention", "instrumentation", "how do I capture this metric". Skip for picking which metric to track (use metrics-ux), for the broader measurement plan (use metrics-spec), for tool-specific config (the analytics vendor's docs).

  • Metrics spec

    nemanli/ux-metrics-skills/skills/metrics-spec Skill

    3★ repo

    Writes a measurement plan **before** the work ships — hypothesis, primary metric, counter-metric, guardrails, decision rule, sample size — so the team agrees on what "success" means before any number exists. Triggers on "measurement plan", "what counts as success?", "how will we know if this worked?", "PRD for metrics", "pre-register the analysis". Skip after data exists (use metrics-diagnose), for picking which metric to track without committing to a decision (use metrics-ux), for tracking-plan design (use metrics-instrumentation), for stakeholder communication (use metrics-present).

  • Problem framing

    alwyndsouza/agile-story-skills/.github/skills/problem-framing Skill

    no license3★ repo

    Frame the right problem before writing stories or epics, using the MITRE Problem Framing Canvas. Use when a feature request is vague, teams disagree on what the real problem is, or discovery is needed before backlog grooming. Triggers on: problem framing, what problem are we solving, problem statement, how might we, HMW, reframe this requirement, frame the problem, is this the right problem, discovery framing, before we write stories, root cause framing, solution-first.

  • Ultraplan

    DobroslavRadosavljevic/skills/skills/ultraplan Skill

    3★ repo

    Exhaustive planning interrogation for turning vague or complex requests into precise, implementation-ready plans. Use when the user invokes $ultraplan, says "ultraplan", "ultra plan", "deep plan", "plan mode", "ask me everything", "interrogate this", or asks the agent to resolve all requirements, use cases, edge cases, tradeoffs, and open questions before implementation.

  • Spec evaluator

    nguyenvanphituoc/shapeup-sdlc-plugin/skills/spec-evaluator Skill

    3★ repo

    Use this skill whenever the user wants to evaluate, QA, or verify that an implemented task actually matches its spec and acceptance criteria — the judge in a planner→generator→evaluator harness. Trigger on: "evaluate task TASK-NNN", "QA TASK-NNN", "verify against spec", "check acceptance criteria", "does this match the spec", "grade this build", "run evaluator", or a tech-lead --order dispatch. Skeptical by default — absence of evidence is a FAIL; probes the running app and files file:line bugs.

  • Tech lead

    nguyenvanphituoc/shapeup-sdlc-plugin/skills/tech-lead Skill

    3★ repo

    Use this skill whenever the user wants to orchestrate a whole feature end-to-end across the harness skills — ba-pitch-analyzer (planner), task-executor (generator), spec-evaluator (judge) — acting as the tech lead that owns the run and reports to the PO at round boundaries. Trigger on: "run the full harness", "act as tech lead", "ship this feature end to end", "from pitch to ship", "orchestrate the build", "plan build evaluate". Use it even when the user describes a multi-step build flow without naming the skills.

  • Translator

    nguyenvanphituoc/shapeup-sdlc-plugin/skills/translator Skill

    3★ repo

    Use this skill whenever intake for the harness (pitch, PRD, requirement, transcript, or any spec input) is in a non-English language and must be normalized to English BEFORE planning/building. The single language gate for the planner→generator→judge harness. Triggers on: "translate this pitch", "normalize to English", "this requirement is in Vietnamese", "prepare intake for the harness", "make the spec English", "check if this is English", and Vietnamese "dịch sang tiếng Anh", "chuẩn hoá tiếng Anh", "dịch pitch", "chuyển yêu cầu sang tiếng Anh". Produces faithful English copies (original never overwritten) plus a glossary and verification report. tech-lead auto-invokes it at GATE L0 when intake is non-English; also runs standalone.

  • Phase plan

    davidlee/doctrine/plugins/doctrine/skills/phase-plan Skill

    3★ repo

    Use just before executing a specific phase — expand its authored plan entry (objective + EN/EX/VT) into the disposable runtime phase sheet with a concrete task breakdown, assumptions, and verification steps. Routed to from /plan or /execute.

  • Plan

    davidlee/doctrine/plugins/doctrine/skills/plan Skill

    3★ repo

    Use when a slice's design is locked and it needs an executable phase plan — refine each phase's objective and entry/exit/verification criteria, author plan.toml + plan.md, and materialise the runtime phase sheets. Routed to from /design.

  • Reconcile

    davidlee/doctrine/plugins/doctrine/skills/reconcile Skill

    3★ repo

    Use after /audit resolved the RV ledger and wrote the reconciliation brief — you are the sole explicit writer of reconciled truth. Consume the RV + brief, write changes through two surfaces (direct edit for per-slice artefacts, REV for governance/spec), and hand off a resolved outcome to /close. Routed to from /audit.

  • Spec coverage assessment

    davidlee/doctrine/plugins/doctrine/skills/spec-coverage-assessment Skill

    3★ repo

    Use when a named subsystem, capability, or code surface needs governance coverage assessed before authoring a spec — deciding what is already governed by an existing PRD / tech spec / ADR, what is dark, and where new spec boundaries should fall by product altitude and C4 level. Use before creating or scoping a product or technical spec for an unfamiliar or partially-governed surface. Use when a request asks to "assess coverage", "find governance gaps", "what's already specified", "where should this spec's boundary sit", "one spec or several", "what needs a PRD vs a tech spec", or "is this subsystem properly documented". Produces a reviewable coverage-map artifact that feeds `/spec-product` and `/spec-tech`. Do not use when the target spec and its boundary are already known and unambiguous — go straight to `/spec-product` or `/spec-tech`. Do not confuse with `doctrine coverage` — unrelated CLI verb for requirement verification.

  • Spec product

    davidlee/doctrine/plugins/doctrine/skills/spec-product Skill

    3★ repo

    Use when authoring, revising, normalising, or reviewing a doctrine product specification/PRD - the durable product intent, requirements, success measures, behaviours, and verification basis for an evergreen capability. use before creating or scoping slices that descend from shared product intent. use when a request asks for product requirements, functional requirements, non-functional requirements, product scope, acceptance gates, out-of-scope boundaries, success measures, or agent-readable product context. do not use for one-off change planning, implementation design, technical architecture, or phase execution.

  • Spec tech

    davidlee/doctrine/plugins/doctrine/skills/spec-tech Skill

    3★ repo

    Use when authoring or revising the technical specification — the how of a capability, downstream of the product spec and upstream of per-slice design. Use to record durable architecture and mechanism, not a single change's design.

  • Fieldops prompt decorators

    download4you/n2-fieldops/fieldops-prompt-decorators Skill

    3★ repo

    Interprets and executes Prompt Decorators written with +++Name(key=value) syntax, handling message vs. chat scope, parameter validation, decorator composition, conflict resolution, retained-state inspection (ActiveDecs and AvailableDecs), selective clearing, and conversation export or dump. Use when a message contains a supported +++ token (for example +++Planning, +++StepByStep, +++Reasoning, +++Interactive, +++Refine, +++Export, +++Dump, +++ChatScope, or +++MessageScope) or when the user asks to create, validate, debug, or explain decorator behavior. Do not trigger for ordinary tone, plan, or formatting requests that contain no +++ decorator syntax or discussion.

  • Auto plan

    ulpi-io/autonomous-engineering/auto-plan Skill

    no license3★ repo

    Turn a spec into a self-reviewed DAG of atomic build tasks: each task gets acceptance criteria, a disjoint write scope (≤3 files), and a slice-scoped validate; dependencies are wired and layered topologically so nothing builds on a missing base. Adversarial critics then attack the graph (cycles, phantom paths, coverage vs spec, task independence) until it is clean. Writes .ulpi/plans/<name>.json. Use when a spec needs an implementable, ordered breakdown before building.

  • Auto spec

    ulpi-io/autonomous-engineering/auto-spec Skill

    no license3★ repo

    Turn a raw feature request into a grounded, TESTABLE spec — autonomously. It recons the real repo and domain to ground every claim, drafts a spec (objectives, user-visible behavior, acceptance criteria, explicit non-goals, constraints, interfaces, risks), then runs a completeness-critic loop that adversarially hunts for gaps, ambiguity, and untestable criteria and fixes them until the spec is stable. Every acceptance criterion it emits is measurable (you could write a test for it); every requirement is grounded in the repo or flagged as an assumption — no invented requirements, no phantom paths. It writes `.ulpi/spec/<name>.md` and is the DEFINE phase that feeds auto-plan. Composes fan-out-work (recon), adversarial-verify (the critic), converge-loop (until-stable), and checkpoint-resume.

  • Autonomous pipeline

    ulpi-io/autonomous-engineering/autonomous-pipeline Skill

    no license3★ repo

    Run the whole engineering lifecycle end-to-end from one request — spec → plan → build → simplify → test → review → performance → ship — as a single autonomous pass with ONE human approval (the plan) and hard-gated escalation for anything irreversible. It chains the auto-* phase skills, carries a durable pipeline checkpoint so a stop/crash resumes at the exact phase and task it left off, watches the signal between phases (a phase that misses its gate is recorded blocked and surfaces in the register — fail closed, no false-green downstream), and returns a verified findings register at the end. Autonomous: it AUTO-FIXES the confirmed findings in a bounded converge-loop (never asking permission to fix), returning only the residual it can't converge within budget or a fix needing an irreversible/ambiguous decision. This is the top-level "maximise autonomous agents" entry point. Composes every auto-* phase plus checkpoint-resume, budget-guard, watch-and-act, and adversarial-verify.

  • Remotion creative

    phamthanhnghia/remotion-agent-skills/skills/remotion-creative Skill

    no license3★ repo

    Non-animation creative direction for Remotion videos. Use for design spec handling, palettes, typography, narration, beat planning, and composition patterns.

  • Planning with files

    Xuan0629/shared-skills/planning-with-files Skill

    no license3★ repo

    One source. Every agent. Zero drift. | 跨 Agent 共享 Skill 管理系统 — 单一数据源,同步到 Claude Code / Codex / Hermes / OpenClaw

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/product-prd Skill

    no license3★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec driven development

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/spec-driven-development Skill

    no license3★ repo

    An "AI-Spec-Driven" workflow for complex tasks, triggered ONLY when explicitly requested. It aligns agent execution with rigorous planning (Spec -> Implementation -> Task Tracking) to mimic Antigravity planning mode.

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/examples/.agents/skills/spec-writer Skill

    no license3★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/product-prd Skill

    no license3★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec driven development

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/spec-driven-development Skill

    no license3★ repo

    An "AI-Spec-Driven" workflow for complex tasks, triggered ONLY when explicitly requested. It aligns agent execution with rigorous planning (Spec -> Implementation -> Task Tracking) to mimic Antigravity planning mode.

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/examples/.claude/skills/spec-writer Skill

    no license3★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

  • Product prd

    Bosh-Kuo/awesome-agent-toolkit/skills/product-prd Skill

    no license3★ repo

    Generate or update a project-level Product Requirements Document (PRD.md) after the user and AI have already discussed requirements, target users, product goals, implementation approach, workflow, and key technical decisions. Focuses on product overview, vision, core objectives, user personas, high-level feature groups, tech stack, system architecture key components, and phased roadmap / future work. Use when the user asks to create a PRD, write a product PRD, document project requirements, summarize the whole project direction, or produce a global project context file for future AI implementation work. Do not use for single-feature specs, acceptance criteria, detailed technical design, or implementation tasks.

  • Spec driven development

    Bosh-Kuo/awesome-agent-toolkit/skills/spec-driven-development Skill

    no license3★ repo

    An "AI-Spec-Driven" workflow for complex tasks, triggered ONLY when explicitly requested. It aligns agent execution with rigorous planning (Spec -> Implementation -> Task Tracking) to mimic Antigravity planning mode.

    The same file is in 2 other repositories

  • Spec writer

    Bosh-Kuo/awesome-agent-toolkit/skills/spec-writer Skill

    no license3★ repo

    Generates feature specification documents based on provided code and functional descriptions. Focuses on system analysis and product logic rather than implementation details. Code is treated as the single source of truth.

    The same file is in 3 other repositories

  • Knowledge injection strategy

    MedocMay/ai-native-builder-consultant-skills/ai-native-builder-consultant-skills/skills/agent-design/knowledge-injection-strategy Skill

    no license3★ repo

    Choose between RAG, fine-tuning, and context engineering for domain knowledge. Use when deciding how your agent will 'know' things, when responses feel generic despite good prompting, or scaling from MVP to production.

  • Dl data strategy

    MedocMay/ai-native-builder-consultant-skills/ai-native-builder-consultant-skills/skills/dl-skills/dl-data-strategy Skill

    no license3★ repo

    为深度学习项目设计数据收集、标注、清洗和增强策略。在确认任务类型(CV/OCR/TS/Speech)后使用,解决"数据从哪里来、怎么标注、标多少够用"的问题。基于 PaddleX 全链条开发范式设计。

  • Prd lite

    MedocMay/ai-native-builder-consultant-skills/ai-native-builder-consultant-skills/skills/requirement-definition/prd-lite Skill

    no license3★ repo

    把项目定义升级成可以继续流转的最小产品文档(PRD Lite)。包含项目背景、目标用户、核心任务流、输入输出、MVP 范围、技术路径初判和风险边界。在项目定义(ai-project-definition)通过后使用,是进入技术设计阶段的正式输入文档。

  • Spec delta checker

    Yue-Zhou1/zkcrypto-audit/.codex/skills/spec-delta-checker Skill

    3★ repo

    Compare cryptographic code against a reference specification or paper. Use when implementation details look close to a standard but may have drifted in validation, transcript binding, parameter negotiation, or caller obligations.