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

  • Kimi ui agent

    BjornMelin/dev-skills/skills/kimi-ui-agent Skill

    no license5★ repo

    Explicit-only Kimi-powered frontend/UI orchestration skill and CLI for repo profiling, design-system context generation, Codex/Kimi Code/Claude Code adapter setup, plan-first git worktree runs, status/reply/finalize lifecycle control, and review artifacts. Use only when the user explicitly invokes `$kimi-ui-agent` or asks to use Kimi UI Agent for frontend/UI audits, redesigns, components, screenshots, implementation planning, or worktree orchestration.

  • Research plan implement

    kevinlin/skills/research-plan-implement Skill

    5★ repo

    Complete Research \u2192 Plan \u2192 Implement workflow for complex tasks. Use this skill whenever the user faces: complex features spanning multiple files, bug investigations requiring root cause analysis, refactoring with architectural implications, or any non-trivial work where understanding the codebase first will prevent wasted effort. Also use when the user says things like 'help me figure out how to...', 'I need to understand before building...', or 'let\u2019s research this before coding'. Skip for simple bug fixes, typos, or single-file changes.

  • Spec coding

    kevinlin/skills/spec-coding Skill

    5★ repo

    Guide users through spec-driven development — from goal clarification through requirements, design, task planning, and incremental execution. Use this skill whenever a user wants to build a new feature with upfront planning, asks for a structured development workflow, mentions "spec-driven", wants to create requirements or a design doc before coding, or invokes /spec-coding. Also trigger when a user has existing spec files (requirements.md, design.md, tasks.md) and wants to continue or execute tasks from them.

  • Spec compact

    kevinlin/skills/spec-compact Skill

    5★ repo

    Compact a spec plan (or design doc) markdown file after the implementation has shipped: strip the transient how — code snippets, step-by-step walkthroughs, file-by-file diffs — that the codebase now owns, keep the why — design decisions, key file references, changelog. Use when the user wants to compact, shrink, or trim a plan/spec file post-implementation, says the plan is bloated or too long now that the feature shipped, or invokes `/spec-compact`. Renaming files, fixing dead links, and index updates belong to `spec-lint`.

  • Spec lint

    kevinlin/skills/spec-lint Skill

    5★ repo

    Lint the project's specification docs (requirements / design / plan / task markdown): orphan specs, dead cross-doc links, index and naming drift, empty sections, stale TODOs, and — most importantly — reverse consistency between layers (design must cover its requirements, plans must cover their design). Auto-detects which spec-driven framework is in use — Kiro IDE, Superpowers, OpenSpec, GitHub spec-kit, BMad Method, GSD, or a generic default profile — and applies that profile's rules. Use when the user asks to lint, audit, or health-check spec docs ("/spec-lint", "check the specs", "spec health check"), asks whether design covers requirements or plans match the design, reports orphan specs or broken spec links, or names a supported framework in a context that implies auditing its spec artefacts.

  • Launch campaign planning

    0xF4ng/aether-growth-fieldwork/growth/launch-campaign-planning Skill

    no license5★ repo

    Select the right launch format (blitz / launch-week / full-week) and produce a structured phase plan for a discrete product or feature launch.

  • North star metrics

    0xF4ng/aether-growth-fieldwork/growth/north-star-metrics Skill

    no license5★ repo

    Selects and validates the North Star Metric (NSM), builds the input metric tree beneath it, defines guardrail metrics that cannot be sacrificed, and designs the review cadence. The NSM is the single metric that most accurately captures the value the product delivers to users — not the value the business extracts from users. Prevents the most common failure mode: optimizing for revenue metrics that move up while the product quietly loses product-market fit.

  • Signal prioritization

    0xF4ng/aether-growth-fieldwork/growth/signal-prioritization Skill

    no license5★ repo

    Decides which intent signals, firmographic triggers, and behavioral indicators to buy, monitor, or build — and how to weight them in account scoring. Use before investing in signal data subscriptions, or when the current signal stack is generating noisy or low-quality pipeline. NOT a signal scraper — a decision framework for signal investment.

  • Channel strategy

    0xF4ng/aether-growth-fieldwork/hardware-gtm/channel-strategy Skill

    no license5★ repo

    Designs the hardware GTM channel strategy: selects the right channel type (SI / OEM / VAR / distributor / DTC), qualifies partners, defines co-sell mechanics, and sets MDF allocation rules. Runs the three-pillar check (Pillar 3) as a gate before channel decisions. Required upstream input for hardware-gtm/launch. Run this skill whenever the go-to-market channel is undefined or when a channel is underperforming.

  • Demo strategy

    0xF4ng/aether-growth-fieldwork/hardware-gtm/demo-strategy Skill

    no license5★ repo

    Designs and scripts hardware product demonstrations: live demos, 60-second distribution videos, and application library content. Applies the five-step demo sequence and no-narration rule. Outputs a demo script, video brief, or application library structure depending on the context. For hardware and robotics products, the demo IS the sales pitch — this skill prevents the most common demo failure modes.

  • Gtm brief

    0xF4ng/aether-growth-fieldwork/pmm/gtm-brief Skill

    no license5★ repo

    Produces a time-bound GTM brief artifact from ICP research, competitive intelligence, product truth, and a defined time horizon. Invoke when turning research, launch context, competitive signals, or founder/PM intent into a structured, actionable plan. This is not OKR planning — it is a decision-ready brief for a named window (day / week / month). Output is a complete brief artifact with verdict on motion fit, near-term moves, open risks, and explicit decision owners. Feeds downstream into campaign execution and experiment design.

  • Seo content strategy

    0xF4ng/aether-growth-fieldwork/pmm/seo-content-strategy Skill

    no license5★ repo

    Plans SEO as a GTM acquisition motion — keyword strategy, content architecture, and distribution plan grounded in ICP demand signals. Produces a content strategy that compounds over time rather than single-post tactics. Use when organic search is a viable acquisition channel for the ICP and team has capacity for sustained content. NOT a technical SEO audit.

  • To spec

    chinkan/RustFox/.agents/skills/to-spec Skill

    5★ 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

    chinkan/RustFox/.agents/skills/to-tickets Skill

    5★ 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

  • Sup coding

    chinkan/RustFox/skills/sup-coding Skill

    5★ repo

    Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish)

  • Keyword cluster architect

    Gingg7260/affiliate-skills/skills/blog/keyword-cluster-architect Skill

    5★ repo

    Map 50-200+ keywords into topical clusters for SEO domination. Build content roadmaps for topical authority. Triggers on: "keyword research", "keyword clustering", "topical authority", "keyword map", "keyword strategy", "content roadmap for SEO", "keyword grouping", "topic clusters", "SEO keyword plan", "map my keywords", "keyword cluster", "hub and spoke content", "build topical authority", "SEO content plan", "keyword universe".

    The same file is in 1 other repository

  • Category designer

    Gingg7260/affiliate-skills/skills/meta/category-designer Skill

    5★ repo

    Define a new category where your product wins by default. Reframe the buying decision. Triggers on: "create a category", "category design", "define my category", "category of one", "reframe the market", "position as category king", "new category", "category creation", "own a category", "category strategy", "competitive positioning", "strategic positioning", "market reframing", "be the only option", "change the buying criteria", "category king".

    The same file is in 1 other repository

  • Funnel planner

    Gingg7260/affiliate-skills/skills/meta/funnel-planner Skill

    5★ repo

    Plan a complete affiliate funnel from research to revenue. Triggers on: "plan my affiliate funnel", "create a funnel strategy", "affiliate business plan", "how to start affiliate marketing", "full funnel roadmap", "plan from scratch", "week by week affiliate plan", "chain skills together", "build my funnel", "affiliate marketing roadmap", "step by step affiliate plan", "onboarding plan".

    The same file is in 1 other repository

  • Process automation audit

    disco-trooper/skills/process-automation-audit Skill

    5★ repo

    Scope, sell, run, and package paid audits for manual business process automation. Use when Codex needs to help with discovery, scoping, pricing, stakeholder questions, process maps, audit deliverables, pilot proposals, or negotiation boundaries for automating operational workflows such as invoices, price lists, ERP/SAP handoffs, warehouse/inventory, approvals, spreadsheets, OCR, AI-assisted document handling, or other repetitive administrative processes. Also use when deciding what is free discovery versus paid audit work.

  • Inventory demand planning

    khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/business-ops/inventory-demand-planning Skill

    no license5★ repo

    Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.

    The same file is in 3 other repositories

  • Strategic compact

    khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/business-ops/strategic-compact Skill

    no license5★ repo

    Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

    The same file is in 4 other repositories

  • Ralphinho rfc pipeline

    khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/devtools/ralphinho-rfc-pipeline Skill

    no license5★ repo

    RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

    The same file is in 7 other repositories

  • Blueprint

    khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/research-utility/blueprint Skill

    no license5★ repo

    Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

    The same file is in 4 other repositories

  • Brief parser

    khanhhuyenngo985-sys/character-scene-design-skills/skills/brief-parser Skill

    no license5★ repo

    解析混乱客户Brief,输出2-3个创意方向选项和完整创作简报。触发词:「解析Brief」「分析客户需求」「帮我看看这个Brief」「客户发来了需求」「整理创意方向」「生成创作简报」。

  • Task breakdown

    lteawoo/skills/skills/task-breakdown Skill

    no license5★ repo

    Break requirements or design ideas into implementable work items. Use it when you need execution order, prerequisites, parallelism, and completion criteria.

  • Test plan writer

    lteawoo/skills/skills/test-plan-writer Skill

    no license5★ repo

    Write a validation plan for a change, including automated tests, manual checks, regression coverage, and exploratory testing. Use it when you need to scope verification quickly before a PR.

  • Campaign brief

    thaolst/ai-growth-agents-for-marketers/skills/campaign-brief Skill

    5★ repo

    Write a complete campaign brief for growth marketing campaigns. Use when the user needs to create a campaign brief, plan a promotion, design a voucher campaign, or structure a marketing campaign. Works for fintech, e-commerce, super apps, and mobile payment platforms. Input: target segment, objective, budget, mechanic type, timeline. Output: complete brief with mechanic design, user journey, budget breakdown, metrics, risks, and pre-launch checklist.

  • Campaign planning

    thaolst/ai-growth-agents-for-marketers/skills/campaign-planning Skill

    5★ repo

    Build a monthly or quarterly campaign plan from a growth target. Use when the user has a target (MEU, transactions, revenue, retention) and needs a full campaign plan: how many campaigns, what type, in what order, with what budget. Higher-level than campaign-brief (which covers a single campaign in detail). Input: target metric, budget, timeline, available channels, constraints. Output: situation analysis, strategy, campaign breakdown, budget allocation, timeline, risks.

  • Meu planning

    thaolst/ai-growth-agents-for-marketers/skills/meu-planning Skill

    5★ repo

    Build a campaign plan backward from a MEU (Monthly Engaging Users) target. Use when the user has a MEU target and needs to know what campaigns to run, what mechanics to use, how to allocate budget, and what the realistic outcome is. Works for fintech apps, super apps, and mobile payment platforms in Southeast Asia. Input: MEU target, current baseline, budget, available channels, user segments, constraints. Output: gap analysis, campaign recommendations, budget allocation, confidence level, Plan B.

  • Multi agent research

    thaolst/ai-growth-agents-for-marketers/skills/multi-agent-research Skill

    5★ repo

    Run multi-agent research-to-planning pipeline using two sequential agents. Use when the user has campaign data and needs a structured plan without code. Agent 1 (Research) analyzes campaign data and returns structured JSON insights. Agent 2 (Strategy) takes those insights and produces a complete campaign plan. Input: campaign data, target, budget, timeline. Output: research findings as JSON → executable campaign plan.

  • Research brief writer

    puristajs/harness/examples/living-wiki-jaeger/skills/research-brief-writer Skill

    5★ repo

    Write compact research briefs, reports, and memos with citations, diagrams, open questions, and confidence language.

  • Content strategy

    TommyBez/skillsboard/.agents/skills/content-strategy Skill

    5★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

    The same file is in 5 other repositories

  • Lead magnets

    TommyBez/skillsboard/.agents/skills/lead-magnets Skill

    5★ repo

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.

    The same file is in 5 other repositories

  • Marketing plan

    TommyBez/skillsboard/.agents/skills/marketing-plan Skill

    5★ repo

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.

    The same file is in 3 other repositories

  • Site architecture

    TommyBez/skillsboard/.agents/skills/site-architecture Skill

    5★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

    The same file is in 5 other repositories

  • Work batch

    christopherlouet/claude-base/.claude/skills/work-batch Skill

    5★ repo

    Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.

  • Work plan

    christopherlouet/claude-base/.claude/skills/work-plan Skill

    5★ repo

    Plan the implementation of a feature. Use when the user wants to plan, architect, define an approach, or before coding a complex feature.

  • Only plan

    Bruno-Cunha-Souza/ValarMindSkills/skills/only-plan Skill

    5★ repo

    Read-only planning: analyze and design without changing project files. Writes one step-by-step plan at project root (default IMPLEMENTATION_PLAN.md). Composable with other skills (e.g. /code-security-review /only-plan). Triggers: /only-plan, 'only plan', 'apenas planejar', 'não altere os arquivos'.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/.agents/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/.agents/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/.kimi-code/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/.kimi-code/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/dist/claude/.claude/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/dist/claude/.claude/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/dist/kimi/.kimi-code/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/dist/kimi/.kimi-code/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/dist/kiro-ide/.kiro/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/dist/kiro-ide/.kiro/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus delivery planning

    amadeus-dlc/amadeus/dist/kiro/.kiro/skills/amadeus-delivery-planning Skill

    5★ repo

    Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Amadeus user stories

    amadeus-dlc/amadeus/dist/kiro/.kiro/skills/amadeus-user-stories Skill

    5★ repo

    Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

  • Plan backlog

    mataeil/OODA-loop/skills/plan-backlog Skill

    5★ repo

    Score GitHub Issues using the RICE framework and propose a priority ordering. Strategize phase skill — turns raw issues into a ranked action plan written to agent/state/backlog.json.

  • Writing product docs

    minorcell/skills/skills/writing-product-docs Skill

    5★ repo

    Use when drafting, rewriting, or reviewing a product definition or product design document — the artifact that states what a product is, what problem it solves, who it is for, and its core concepts and information structure. Applies when the user asks for a product definition, product design doc, or "PRD-lite", or pushes back that a draft reads like a technical proposal, RFC, or data-model spec. Enforces user-perspective wording, information-structure over schemas, problem-before-solution ordering, and mental-model-first concept writing.

  • Writing proposals

    minorcell/skills/skills/writing-proposals Skill

    5★ repo

    A collection of skills distilled from minorcell's own workflows and useful practices from others.

  • Cli forge hld

    Destynova2/cli-code-skills/cli-forge-hld Skill

    5★ repo

    Generate a High-Level Design (HLD) document for a software system. Use when the user mentions 'HLD', 'system design', 'architecture document', 'design doc', 'ADR', 'C4 diagram', 'back-of-envelope', 'capacity planning', 'ATAM', 'arc42', 'design proposal', 'Gate review', or says 'design X', 'architect Y'. Produces C4 L1-L2 diagrams, capacity estimations, ADRs, tradeoff analysis, and deployment architecture. Do NOT use for low-level/detailed design (class diagrams, DB schemas, API specs) — use cli-forge-lld instead.

  • Pipeline spec reviewer protocol

    gustavo-meilus/superpipelines/plugins/superpipelines/skills/pipeline-spec-reviewer-protocol Skill

    5★ repo

    Loaded by the pipeline-spec-reviewer agent to perform Stage 1 spec-compliance review.

  • Sk spec driven development

    gustavo-meilus/superpipelines/plugins/superpipelines/skills/sk-spec-driven-development Skill

    5★ repo

    Establishes a formal spec→plan→tasks→implement contract for multi-step feature work. Use when authoring multi-step pipelines, building new features, refactoring systems, or when a request is too ambiguous for direct execution and a verified specification must precede implementation.

  • Sk write review isolation

    gustavo-meilus/superpipelines/plugins/superpipelines/skills/sk-write-review-isolation Skill

    5★ repo

    Enforces structural separation between the writing agent and the reviewing agent, with Stage 1 (spec compliance) hard-gating Stage 2 (code quality). Use when dispatching a reviewer after a pipeline worker has produced output, when authoring any pipeline step that requires formal verification against a specification, or when implementing a two-stage review loop.

  • Pipeline spec reviewer protocol

    gustavo-meilus/superpipelines/skills/pipeline-spec-reviewer-protocol Skill

    5★ repo

    Loaded by the pipeline-spec-reviewer agent to perform Stage 1 spec-compliance review.