agentsclimarketplace

Plan & spec

10,724 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Resolve open questions

    anarefin/ai-agent-skills/resolve-open-questions Skill

    no license1★ repo

    Second-pass automation for an EARS specification file produced by /springboot-to-ears. Walks every `[NEEDS REVIEW]` item in the spec's `## Open Questions` section, executes the breadcrumb commands from the item's `*Hint for reviewer:*` footer, and either resolves the question (rewriting the entry and citing the resolution on every affected EARS statement) or leaves it open untouched. Trigger when the user types `/resolve-open-questions <path-to-EARS-file>`.

  • Springboot to ears

    anarefin/ai-agent-skills/springboot-to-ears Skill

    no license1★ repo

    Reverse engineer a Java Spring Boot project into a 100% complete EARS (Easy Approach to Requirements Syntax) specification file. Use this skill when the user wants to extract business requirements from an existing Spring Boot codebase — including single controllers, multiple controllers, or an entire project directory — and produce a standalone, code-free .md EARS file that can serve as a source of truth for regenerating the system in any architecture (DDD, CQRS, Event Sourcing, etc.). The skill also auto-resolves its own Open Questions on the first pass (Step 6.5): a fresh read-only subagent chases each question's breadcrumb footer and folds confident answers back into the spec as finalised statements, leaving only genuinely unresolvable items as [NEEDS REVIEW] — so a separate /resolve-open-questions run is usually unnecessary. Each module and content subsection is annotated with a `> **Source files:**` line listing the full project-relative paths it was extracted from, so a developer can cross-check the spec against the codebase (the EARS statements themselves stay code-free).

  • Estimation

    tdyzzsp47/claude-skills/skills/estimation Skill

    1★ repo

    ソフトウェア開発の工数・期間を見積もるスキル。要件定義・設計・実装・テスト各フェーズの着手前、またはステークホルダーへの計画提示時に使う。

  • Task breakdown

    tdyzzsp47/claude-skills/skills/task-breakdown Skill

    1★ repo

    機能要件をAIエージェント委譲・並列実装に適した粒度のタスクに分解するスキル。設計フェーズ後・実装着手前に使い、タスク票の作成と依存関係・クリティカルパスの整理を行う。

  • Platform prd reviewer

    linyindong/platform-product-skills/skills/platform-prd-reviewer Skill

    1★ repo

    Review PRDs, product requirement drafts, platform designs, prototypes, and requirement sections with PRD-quality-first judgment, document-specific findings, product-logic closure, and artifact-size calibration. Use when the user asks to check, review, validate, score, find gaps, help a PM improve the next PRD version, assess whether logic is closed-loop, compare small-feature vs 0-to-1 platform readiness, or decide whether a PRD is ready for product review, engineering review, RFC follow-up, or further scope clarification.

  • Stress test the plan

    k-anss/whetstone/skills/stress-test-the-plan Skill

    1★ repo

    Red-team a decision or plan: surface its fatal flaw, expose hidden assumptions, and trace how it fails over multiple rounds — deliberately pessimistic, no comfort, no rubber-stamping. Trigger when the user says "stress-test this plan", "red-team my decision", "find the holes", "what am I missing", or "argue against this". Do NOT trigger — and the skill must say so — when the user is in emotional distress, or has already decided and is executing (then only "how to die less", not "should you do it"). It also declares its own bias: it is deliberately pessimistic and can talk a good opportunity out of existence; the real call sits between this and a normal read.

  • Acceptance criteria

    roronoazoroshao369/vibe-coding-os/skills/core/acceptance-criteria Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Brownfield spec enhancement

    roronoazoroshao369/vibe-coding-os/skills/core/brownfield-spec-enhancement Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Crash proof planning

    roronoazoroshao369/vibe-coding-os/skills/core/crash-proof-planning Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Plan driven execution

    roronoazoroshao369/vibe-coding-os/skills/core/plan-driven-execution Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Plan from spec

    roronoazoroshao369/vibe-coding-os/skills/core/plan-from-spec Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Prd from context

    roronoazoroshao369/vibe-coding-os/skills/core/prd-from-context Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Spec first development

    roronoazoroshao369/vibe-coding-os/skills/core/spec-first-development Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Task breakdown from plan

    roronoazoroshao369/vibe-coding-os/skills/core/task-breakdown-from-plan Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Diet planner

    skillsmith-dev/ai-skills/skills/diet-planner Skill

    no license1★ repo

    科学减脂饮食规划助手根据你的体重目标和饮食偏好生成每日三餐加餐食谱计算热量和营养素配比提供采购清单和替代方案让减脂吃得饱还能瘦

  • Exam planner

    skillsmith-dev/ai-skills/skills/exam-planner Skill

    no license1★ repo

    考研备考定制规划助手根据目标院校专业和当前基础生成个性化复习计划包含科目时间分配每日任务模考节奏和冲刺策略覆盖政治英语数学专业课全科

  • Fitness planner

    skillsmith-dev/ai-skills/skills/fitness-planner Skill

    no license1★ repo

    个性化健身计划生成助手根据你的目标增肌减脂塑形和条件场地时间器械生成训练计划动作指导饮食建议和进度追踪方案支持家庭和健身房两种场景

  • Travel planner

    skillsmith-dev/ai-skills/skills/travel-planner Skill

    no license1★ repo

    个性化旅行行程定制助手——根据目的地、时间、预算、偏好生成详细行程方案,包含交通、住宿、餐饮、景点、费用预估。支持国内/国际旅行,实时搜索最新信息,提供避坑提醒和本地人建议。

  • Design doc

    quantum-box/agent-packages/plugins/quantum-box/skills/design-doc Skill

    no license1★ repo

    Create or update Tachyon Design Documents (DDs). Use proactively when: (1) API, DB, UI workflow, or cross-context behavior is being designed, (2) implementation needs a plan before code, (3) the user asks for DD/design doc, or (4) a taskdoc contains design details that should be separated.

  • Google ads forecast

    kastriasani/google-ads-skills/skills/google-ads-forecast Skill

    1★ repo

    Forecast Google Ads budget, clicks, conversions, revenue, ROAS and CPA with best, likely and worst scenarios before you commit spend. Use this whenever someone asks to forecast or project a Google Ads plan, model a budget, estimate results or ROAS, size the spend needed to hit a conversion or revenue goal, build a best/likely/worst or scenario forecast, check whether a plan clears break-even ROAS, run a what-if on CPC or conversion rate, plan a quarterly or seasonal budget, or decide where the next budget dollar should go across campaigns. Triggers include forecast, projection, budget plan, media budget, scenario planning, ROAS forecast, CPA target, results estimate, what-if, ramp, and goal coverage. Runs standalone on pasted numbers or a CSV; optional Google Ads API, Keyword Planner, GA4 and Sheets make it sharper.

  • Google ads media plan

    kastriasani/google-ads-skills/skills/google-ads-media-plan Skill

    1★ repo

    Build a quarterly Google Ads media plan, budget, and 90-day rollout roadmap. Allocates a monthly or quarterly budget across campaign types (Brand Search, Non-brand Search, Shopping, Performance Max, Demand Gen, Display, YouTube) by CAC, CPA, and ROAS efficiency, with conservative, moderate, and aggressive scenarios and a phased launch plan. Use when the user asks to plan a Google Ads budget, build a paid search media plan or roadmap, split spend across campaign types, forecast conversions or ROAS, decide brand vs non-brand allocation, size a quarterly or monthly PPC budget, or plan a phased campaign rollout. Triggers on phrases like media plan, budget allocation, campaign roadmap, paid search forecast, how much should I spend on Google Ads, and quarterly PPC plan.

  • Google ads presentation

    kastriasani/google-ads-skills/skills/google-ads-presentation Skill

    1★ repo

    Structure a client-ready Google Ads proposal or QBR deck outline that a slide generator can render. Use whenever someone needs a pitch deck, a sales proposal, a client-ready slide outline, a quarterly business review deck, a QBR presentation, or wants Google Ads results and a plan turned into slides. Trigger phrases include build a deck, proposal deck, pitch deck, QBR deck, slide outline, present these results, turn this report into slides, client presentation, and structure a Google Ads presentation. Pairs with google-ads-reporting, which produces the underlying numbers.

  • Google ads research

    kastriasani/google-ads-skills/skills/google-ads-research Skill

    1★ repo

    Structure market and advertiser research before building Google Ads campaigns. Produces a research brief with a prioritized web-search query list, an ICP and persona table, a demand and SERP-landscape checklist, audience-signal hypotheses mapped to Google audience types, and offer and angle hypotheses. Use this first, before keyword research or campaign setup, whenever you are planning paid search for a new brand, vertical, or market. Trigger when the user says research a market, research an advertiser, build a research brief, study the demand landscape, scope a Google Ads account, analyze the competitive landscape for paid search, define the ICP or audience, or asks what should I know before launching Google Ads.

  • Client deliverable templates

    scumunna/programmatic-skills/skills/client-deliverable-templates Skill

    1★ repo

    Fill-in templates for client-facing programmatic deliverables, with the honesty rules baked in. Use when the user asks for a "media plan template", a "QBR deck" or "business review", a "client proposal", how to "explain this to a client" or put it in "plain English", a "client glossary", how to "deliver bad news to a client", or a "client report template". Provides a media plan, a QBR slide spine, a proposal outline, a plain-language glossary, and a bad-news framing pattern.

  • Dv360 bid strategy

    scumunna/programmatic-skills/skills/dv360-bid-strategy Skill

    1★ repo

    Choose and configure the right Display & Video 360 bid strategy. Use when the user asks which bid strategy to use, fixed vs automated bidding, Target CPA, Target CPM, Target ROAS, maximize conversions or value, minimize CPA or CPC, target viewable CPM, custom bidding, learning periods, bid caps, or why a line item is not winning auctions.

  • Reach and frequency planning

    scumunna/programmatic-skills/skills/reach-and-frequency-planning Skill

    1★ repo

    Plan and read deduplicated reach and frequency across DSPs and channels. Use when the user asks about "reach and frequency", "effective frequency", "deduplicated reach", "cross-platform reach", "frequency cap planning", "the reach curve", "diminishing reach", "co-viewing", "1+ 2+ 3+ reach", "average frequency vs frequency distribution", or "how many people did we actually reach" across multiple platforms. Covers the math, why platform reach is non-additive and must never be summed, the identity fragmentation that makes cross-walled-garden frequency capping best-effort, and a triangulation method for one deduplicated number.

  • Trader onboarding

    scumunna/programmatic-skills/skills/trader-onboarding Skill

    1★ repo

    A structured ramp for a new programmatic trader, built on this library. A Week-1, Week-2, and Week-4 learning path that starts at the foundations, runs the read-only loops, shadows the media-planner agent on a real brief, and ends with a build specification graded by the qa-scrutinizer agent. Use when the user says "trader onboarding", "onboard a new trader", "learning path", "where do I start", "ramp a junior", "training plan", "new hire", or asks how to bring someone up to speed on the desk.

  • Opc strategy

    opcspace/opcstartup-skill/opc-strategy Skill

    no license1★ repo

    AI One-Person Company (OPC) strategy framework for niche selection, MVP validation, and business model design. Use when user is choosing an AI startup direction, validating a product idea, screening business opportunities, or designing pricing and revenue models for a solo AI business. Triggers include "AI创业选方向" "AI赛道" "MVP验证" "商业模式" "定价策略" "AI副业选什么" "一人公司做什么".

  • Office hours

    mtthsnc/tempest/plugins/tempest/skills/office-hours Skill

    1★ repo

    Use when you have a raw, vague, or unexamined idea or feature request and you want to pressure-test it with forcing questions BEFORE any planning or design — to make sure you build the right thing. Produces a sharpened problem statement and scope boundaries you can hand to the `plan` workflow. Skip when the problem is already crisp and well-bounded.

  • Plan

    mtthsnc/tempest/plugins/tempest/skills/plan Skill

    1★ repo

    Use when a coding task is non-trivial — a new feature, a multi-file change, a refactor, or anything with more than one reasonable approach — and you want a reviewed implementation plan before writing code. Produces a concrete, criticised plan you can hand to a build step. Skip for typo-level or single-obvious-line fixes.

  • Comment spec

    comment-hq/skills/skills/comment-spec Skill

    1★ repo

    Shape a rough product idea into a crisp, proportionate spec through a live Comment.io comm, then hand it to comment-feature when build authority exists. Makes goal, acceptance, delivery topology, key risks, and out-of-scope clear; uses analytics, instrumentation, dashboards, concept mapping, and critic review only when the size of the product bet warrants them. Invoke as `$comment-spec` / `/comment-spec`, or when asked to spec, shape, scope, or design a feature before building. Works identically under Codex and Claude Code.

  • Drive plan

    comment-hq/skills/skills/drive-plan Skill

    1★ repo

    Drive a multi-phase implementation plan to completion through a Comment.io Plan/worklog or local Markdown plan. Uses phases as execution organization, not automatic gates; validates focused deltas, invokes bounded risk-scaled review at delivery-slice or changed-invariant boundaries, keeps the plan current, and steers only on real decisions. Invoke as `$drive-plan` / `/drive-plan`, or when asked to execute a phased plan autonomously. Works identically under Codex and Claude Code.

  • End of day

    jdiazromeral/tars/skills/end-of-day Skill

    1★ repo

    End-of-day review — sync today's work in, then show what you did today (by concept) alongside what's open for tomorrow. A read-only planning pass, NOT the digest. Trigger on "end of day", "eod", "what did I do today", "wrap up my day", "plan my tomorrow", "daily review".

  • Growth engineering brief

    duandigi/duandigi-growth-marketing-skill/skills/growth-engineering-brief Skill

    1★ repo

    Use this skill when translating a growth hypothesis into an implementation-ready brief for a landing page, free tool, calculator, onboarding change, tracking event, CRM automation, referral mechanism, integration, or WordPress change.

  • Growth experiment prioritization

    duandigi/duandigi-growth-marketing-skill/skills/growth-experiment-prioritization Skill

    1★ repo

    Use this skill when scoring, ranking, sequencing, or selecting growth experiments and research tasks across one or many projects using impact, confidence, strategic fit, reusability, revenue relevance, effort, risk, and dependencies.

  • Llm wiki migration planner

    po4yka/llm-wiki-skills/skills/llm-wiki-migration-planner Skill

    1★ repo

    Create a no-write migration plan for turning existing notes, docs, Obsidian vaults, Notion exports, research archives, or repository documentation into an LLM-Wiki. Use when the user wants a dry-run plan before moving or editing files; route applying the approved plan to llm-wiki-refactor.

  • Llm wiki refactor

    po4yka/llm-wiki-skills/skills/llm-wiki-refactor Skill

    1★ repo

    Refactor an existing docs folder, Obsidian vault, or messy note collection into an LLM-Wiki structure. Use for applying an approved migration plan, with frontmatter normalization, raw/wiki separation, link repair, and review-safe restructuring; route no-write migration planning to llm-wiki-migration-planner.

  • Design brief

    yoelgal/better-dev/skills/design-brief Skill

    1★ repo

    Use when a work item has real UI surface and its visual direction isn't settled - a request to make something look good, design a landing page or a screen, pick an aesthetic or a design system, fix a UI that reads as generic AI slop, or turn a vague "looks nice" into visual done-criteria the loop can verify. This is the design front-end `/groundwork` composes to settle foundation tokens and `/plan-grill` composes for a UI feature. Composes the host's design skill and sources one on a gap; hardcodes no aesthetic or stack. Not for auditing existing UI code against accessibility or style guidelines - that is a host design-review skill (`/web-design-guidelines`) or `/review`.

  • Plan grill

    yoelgal/better-dev/skills/plan-grill Skill

    1★ repo

    Use when the user wants a new feature or capability built and it is not a one-to-two-step change - "I want to add X", "let's build a way to Y", "can we add", "new feature Z", a rough intent that needs a plan before code. When the input is somebody else's adjective rather than an intent the operator owns, /brief-to-problem decodes it into a measurable problem first and hands the result here. Checks the baseline, ideates and grills the design watertight, and pins the observable done-criteria the loop drives to. For a bug or "X is broken" reach for /diagnose; for a whole new app or epic, /groundwork; for a trivial one-to-two-step change, just make it - still in its own worktree branch, skipping only the planning. Chore-class work enters here too - "upgrade to React 19", clearing the CVE the audit gate flagged, a behavior-preserving refactor, test or docs debt - on the contract-lite path.

  • Marketing

    dy/skills/skills/marketing Skill

    no license1★ repo

    Craft high-converting marketing using the verified direct-response canon — building and pricing offers, writing copy (headlines, ads, emails, sales and landing pages, VSLs), positioning and messaging products, and planning content and distribution. Use when the user wants to write or critique sales copy, create/sharpen/name/price an offer, position or differentiate a product, write a headline/hook/CTA, plan a launch or content strategy, improve conversion, or name a marketing framework. Grounded in evidence-verified masters (Schwartz, Caples, Hopkins, Ogilvy, Hormozi, Dunford, Berger, Cialdini) — not guru hype.

  • Strategic advisor

    ggoosen/Digital-Workforce/.claude/skills/strategic-advisor Skill

    1★ repo

    Your Strategic Thought Partner — the advisor you couldn't hire at any price, available 24/7 with no ego and infinite patience. Convenes a board of named advisors that debate your decision, surfaces your blind spots and biases, and presents the call in your decision style. Use when you say "advise me", "think through", "should I", "strategic advisor", "board of advisors", or are processing a hard call alone at 11pm.

  • Course poster planning

    Ivor-NCUT/course-producer/skills/course-poster-planning Skill

    1★ repo

    从完整课程提炼购买逻辑、海报类型、信息顺序、文案与模块比例,并在飞书授权可用时调用 beautiful-feishu-whiteboard 生成可编辑画板原型。Use when the user says 课程海报、课程详情页、招生长图、课程 poster、课程系列图、飞书画板原型,或 Course Producer 进入 poster_planning 阶段。

  • Brief to blueprint

    wjlgatech/design-anything/skills/brief-to-blueprint Skill

    no license1★ repo

    Compile a messy design brief (text and/or picture) into a structured blueprint plan: target (print/construction/game), dimensions, constraints, applicable patterns, and the ready-gate it must pass. Trigger: "design me a ...", "turn this sketch into a model", "I want a 3D-printable ...". NOT for photoreal rendering or structural engineering sign-off.

  • Design anything

    wjlgatech/design-anything/skills/design-anything Skill

    no license1★ repo

    Turns any design intent — a text brief or a picture — into an execution-ready, gate-verified blueprint: 3D-printable models (STL), construction floor plans, garment sewing patterns, game/sim scenes. Discovers what the user wants to design, retrieves survival-tested principles and constraint tables, emits deterministic parametric source, and verifies with machine gates (watertight, clearances, egress, zero-waste, fit). Use when the user wants to design, redesign, or validate a physical or spatial thing: "design me a…", "is this printable / buildable / cuttable", "turn this sketch or photo into a plan", "redesign my room / house / garden / apron / game level", "make it 3D-print ready". NOT for graphic/UI/logo design, photoreal rendering, or engineering certification (a gate is never a permit or PE stamp).

  • Plan execute router

    fullREFIT/skills/skills/plan-execute-router Skill

    1★ repo

    Executes the plan/execute model routing pattern to cut AI-workflow cost by 50–75% on feature builds, refactors, and migrations. Claude plans the task at frontier capability and produces a detailed spec, then routes execution to a cheaper model — via Codex CLI subprocess if available, a Claude Code subagent scoped to a smaller model, or manual copy-paste instructions when neither path exists. Optionally invokes a frontier review pass on the executor's output. Includes fit-check to detect when a task does NOT fit the pattern and cost estimation for the specific split chosen. MANDATORY TRIGGERS: model routing, plan-execute, plan then execute, route to cheaper model, delegate execution, split planning from execution, cheaper executor, cost split, plan-execute-router, model split, use Codex for execution, use Sonnet for execution, spec-then-code, spec then code, save on this build, cost-optimize this task.

  • Prep project

    fullREFIT/skills/skills/prep-project Skill

    1★ repo

    Analyze a project folder and produce executor-ready specification packages. Auto-routes deliverables to Cowork (content, research, docs, analysis) or the Claude Code task-orchestrator (bash, MCP tools, deployment, Git), and produces both packages when a project spans surfaces. Outputs a single COWORK-BATCH.md (Cowork) or a 5-file spec — README.md, 00-PROJECT-INDEX.md, CLAUDE-TASKS.md, SPECS.md, DEPENDENCIES.md (orchestrator). Every task is self-contained with an absolute output path and verifiable acceptance criteria. Use when decomposing a project into autonomous-execution-ready tasks. MANDATORY TRIGGERS: prep project, prepare project, prep for cowork, prep for orchestrator, prep for execution, project spec, execution spec, batch execution prep, task decomposition, cowork batch, orchestrator spec.

  • Project orchestrator

    fullREFIT/skills/skills/project-orchestrator Skill

    1★ repo

    Multi-platform AI project orchestrator that decomposes projects into routed task plans across Claude Cowork, Claude Code, Cursor, Warp.dev, n8n, and other AI tools. Use when the user provides project details (website build, brand identity, HR campaign, product launch, etc.) and needs an execution plan distributed across multiple AI platforms. Triggers on phrases like "orchestrate this project", "plan this across tools", "break this down", "create a task plan", "route this project", or any multi-phase project that would benefit from cross-platform execution. Also triggers when user provides a project brief, PRD, or scope document and wants it turned into actionable task files.

  • Entalpa implement

    entalpa/entalpa-mcp/skills/entalpa-implement Skill

    1★ repo

    Use this skill when working with Entalpa through its MCP server to implement stories and requirements that were authored on the Entalpa website, inspect the project/stakeholder/story/requirement/subsystem hierarchy, record code references, implementation status, and test coverage back onto requirements, or otherwise perform requirements-engineering work that should preserve traceability and avoid destructive MCP tool calls.

  • Entalpa prd

    entalpa/entalpa-mcp/skills/entalpa-prd Skill

    1★ repo

    Use this skill to generate a human-readable PRD/BRD document artefact from an Entalpa project over its MCP server — a stakeholder-facing spec (business-requirements narrative, per-subsystem functional and non-functional requirements with stable codes, data & storage and Definition-of-Done tables, and story/requirement traceability) exported as Markdown and, optionally, PDF. Covers the whole project or a selected subset of subsystems/stories. It reads project data and writes a document; it does not modify the project unless the user explicitly asks.

  • Thesis requirements planning

    lihongqing2001-gif/chinese-thesis-production-skills/skills/thesis-requirements-planning Skill

    1★ repo

    Convert official school rules, degree requirements, supervisor instructions, accepted local exemplars, and an author's research scope into a traceable Chinese thesis profile, outline, chapter contracts, material inventory, and staged production plan. Use at thesis startup, after a structural change, or whenever formatting and chapter expectations are unclear.

  • Red team technical plan

    ImYourBoyRoy/agent-continuity-stack/skills/red-team-technical-plan Skill

    1★ repo

    Stress-test a material technical plan, architecture, migration, integration, release, or automation proposal before implementation. Use for explicit red-team review, hidden assumptions, failure modes, alternatives, and rollback—not trivial edits.

  • Planning

    Aiweline/WelineFramework/.codex/skills/planning Skill

    1★ repo

    Create implementation-ready engineering plans for WelineFramework. Use in Plan mode, or when the user requests detailed requirements, code modification points, task cards, test cases, acceptance criteria, risk and rollback design, or a handoff package for execution-oriented AI agents.

  • Planning

    Aiweline/WelineFramework/dev/ai/skills/planning Skill

    1★ repo

    Repository-wide engineering planning skill for converting software requirements into implementation-ready plans that execution agents can follow mechanically and acceptance agents can verify independently. Use in Plan mode, or whenever the user asks for a detailed development plan, modification matrix, task decomposition, test cases, acceptance criteria, risks, rollback, or a handoff package for execution-oriented AI agents.

  • Prd shaping

    authenticfake/clike/extensions/vscode/templates/harper-init/.clike/skills/vendor/bmad/prd-shaping Skill

    1★ repo

    Clike is an AI-native developer experience layer AI Native Pipeline principles and from some visionar on internet

  • NioPD PD acceptance criteria

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-acceptance-criteria Skill

    1★ repo

    Creates detailed acceptance criteria for user stories. Use for sprint planning, QA preparation, or developer handoff.

  • NioPD PD draft prd

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-draft-prd Skill

    1★ repo

    Drafts or converts documents into Product Requirements Documents (PRD). Supports two modes - (1) Create new PRD from initiative documents and research, or (2) Convert existing documents to PRD format using standard or daily iteration templates.

  • NioPD PD draft psd

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-draft-psd Skill

    1★ repo

    Creates Product Strategy Document. Use for strategic product planning.

  • NioPD PD roadmap

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-roadmap Skill

    1★ repo

    Creates product roadmaps with Mermaid Gantt diagrams showing feature timelines. Use for release planning, stakeholder communication, or team alignment on delivery schedule.

  • NioPD PD stories

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PD-stories Skill

    1★ repo

    Generates user stories from PRD or initiative documents following agile best practices. Use for sprint planning, backlog creation, requirements decomposition, or development handoff.

  • NioPD PM agile planning

    8421bit/NioPD-Skills/plugins/niopd/skills/NioPD-PM-agile-planning Skill

    1★ repo

    Creates agile sprint planning. Use for sprint ceremonies.