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
OpenSIN-AI/OpenSIN-Skills/c-level-advisor/ciso-advisor Skill
no license2★ repoSecurity leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/c-level-advisor/cpo-advisor Skill
no license2★ repoProduct leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/c-level-advisor/strategic-alignment Skill
no license2★ repoCascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, or strategy communication.
The same file is in 4 other repositories
OpenSIN-AI/OpenSIN-Skills/engineering/spec-driven-workflow Skill
no license2★ repoUse when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
The same file is in 5 other repositories
OpenSIN-AI/OpenSIN-Skills/marketing-skill/content-creator Skill
no license2★ repoDeprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.
The same file is in 4 other repositories
OpenSIN-AI/OpenSIN-Skills/marketing-skill/content-strategy Skill
no license2★ repoWhen 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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/marketing-skill/free-tool-strategy Skill
no license2★ repoWhen the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness. Use when they mention 'engineering as marketing,' 'free tool,' 'calculator,' 'generator,' 'checker,' 'grader,' 'marketing tool,' 'lead gen tool,' 'build something for traffic,' 'interactive tool,' or 'free resource.' Covers idea evaluation, tool design, and launch strategy. For pure SEO content strategy (no tool), use seo-audit or content-strategy instead.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/marketing-skill/launch-strategy Skill
no license2★ repoWhen the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
The same file is in 2 other repositories
OpenSIN-AI/OpenSIN-Skills/marketing-skill/marketing-strategy-pmm Skill
no license2★ repoProduct marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
The same file is in 5 other repositories
OpenSIN-AI/OpenSIN-Skills/marketing-skill/pricing-strategy Skill
no license2★ repoDesign, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy. Use when building a pricing model from scratch, redesigning existing pricing, planning a price increase, or improving a pricing page. Trigger keywords: pricing tiers, pricing page, price increase, packaging, value metric, per seat pricing, usage-based pricing, freemium, good-better-best, pricing strategy, monetization, pricing page conversion, Van Westendorp. NOT for broader product strategy — use product-strategist for that. NOT for customer success or renewals — use customer-success-manager for expansion revenue.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/operations/planning/check-plan-done Skill
no license2★ repoDEPRECATED — Use /plan instead. Unified plan-and-execute workflow merged into /plan.
OpenSIN-AI/OpenSIN-Skills/operations/planning/omoc-plan-swarm Skill
no license2★ repoDEPRECATED — Use /plan instead. OMOC Plan Swarm merged into ultimate /plan skill.
OpenSIN-AI/OpenSIN-Skills/operations/planning/plan Skill
no license2★ repoUltimate plan-and-execute skill v2. 13 stages: Check, Research, Dependency Analysis, Plan Draft, Estimation & Risk, Critical Review, Quality Score, Approval & Decision Register, GitHub Sync, What-If Simulation, Execute, Auto Re-Plan, Verify, Post-Mortem & Learn. Adds: Plan JSON Schema, Dependency DAG, 3-Point Estimation (PERT), Monte Carlo, Risk Scoring (0-100), OKR Framework, Decision Register, Assumptions Log, Plan Quality Score (0-100), Auto Re-Plan Triggers, Plan Templates, Multi-Stage Approval, What-If Simulation, Post-Mortem Learning Loop, Blocker Detection, Plan Versioning, Continuous Planning Mode. Replaces /check-plan-done, /omoc-plan-swarm, /biometrics-plan.
OpenSIN-AI/OpenSIN-Skills/product-team/agile-product-owner Skill
no license2★ repoAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/product-team/code-to-prd Skill
no license2★ repoReverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.
The same file is in 2 other repositories
OpenSIN-AI/OpenSIN-Skills/product-team/competitive-teardown Skill
no license2★ repoAnalyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.
The same file is in 4 other repositories
OpenSIN-AI/OpenSIN-Skills/product-team/product-manager-toolkit Skill
no license2★ repoComprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
The same file is in 1 other repository
OpenSIN-AI/OpenSIN-Skills/product-team/product-strategist Skill
no license2★ repoStrategic product leadership toolkit for Head of Product covering OKR cascade generation, quarterly planning, competitive landscape analysis, product vision documents, and team scaling proposals. Use when creating quarterly OKR documents, defining product goals or KPIs, building product roadmaps, running competitive analysis, drafting team structure or hiring plans, aligning product strategy across engineering and design, or generating cascaded goal hierarchies from company to team level.
The same file is in 4 other repositories
OpenSIN-AI/OpenSIN-Skills/product-team/roadmap-communicator Skill
no license2★ repoUse when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
The same file is in 4 other repositories
OpenSIN-AI/OpenSIN-Skills/product-team/spec-to-repo Skill
no license2★ repoUse when the user says 'build me an app', 'create a project from this spec', 'scaffold a new repo', 'generate a starter', 'turn this idea into code', 'bootstrap a project', 'I have requirements and need a codebase', or provides a natural-language project specification and expects a complete, runnable repository. Stack-agnostic: Next.js, FastAPI, Rails, Go, Rust, Flutter, and more.
The same file is in 5 other repositories
OpenSIN-AI/OpenSIN-Skills/project-management/senior-pm Skill
no license2★ repoSenior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring. Use when a user needs help with project plans, project status reports, risk assessments, resource allocation, project roadmaps, milestone tracking, team capacity planning, portfolio health reviews, program management, or executive-level project reporting — especially for enterprise-scale initiatives with multiple workstreams, complex dependencies, or multi-million dollar budgets.
The same file is in 6 other repositories
imamirezaei/Product-Team-Claude-Skills/policy/product-manager/skills/feature-prioritization Skill
no license2★ repoUse this skill when the PM needs to prioritize features, compare options against the roadmap, or build a defensible argument for or against a feature request. Triggers: 'which one should we build first', 'this conflicts with our roadmap', 'management wants this feature but I don't think it's a priority', 'how do I justify not doing this', 'if we add this what do we drop', or any situation where the PM needs to make a prioritization decision or defend one.
imamirezaei/Product-Team-Claude-Skills/policy/product-manager/skills/feature-spec Skill
no license2★ repoUse this skill when the PM needs a complete feature spec to align the entire team: engineering, design, QA, and stakeholders. Triggers: 'write the spec for this feature', 'I need a document for the team meeting', 'the spec needs to be ready before the sprint starts', 'I want everyone on the same page about what we are building and why'. Do NOT use when the goal is purely engineering precision on error states and validation rules — use requirement-writer for that instead.
imamirezaei/Product-Team-Claude-Skills/policy/product-manager/skills/requirement-writer Skill
no license2★ repoUse this skill when the PM needs a precise, engineering-focused requirement document — not the broader team spec. This is the document engineering reads to implement without asking follow-up questions. Triggers: 'I need engineering to have all the details', 'write the technical requirements for this', 'engineering said the requirements are incomplete', 'I need to specify every error state', 'I need validation rules and business rules documented'. Do NOT use for team-facing feature alignment — use feature-spec for that instead.
huangyun111/planflow/skills/plan Skill
2★ repoUse when you have a goal or spec for a multi-step task and want to break it into an ordered PLAN.md task list before any coding. Sets up PLAN.md; does not implement.
huangyun111/planflow/skills/using-planflow Skill
2★ repoUse when starting any substantial, multi-step task, or when the user mentions planning, a PLAN.md, breaking work into tasks, or short focused sessions, or when a PLAN.md/HANDOFF.md already exists in the project — establishes the plan-driven, short-session workflow and points to the plan, next, and handover skills.
felipecabargas/gambit/skills/verify-acceptance-criteria Skill
2★ repoVerify acceptance criteria quality and identify gaps. Use this skill whenever you need to evaluate acceptance criteria (ACs) to ensure they meet quality standards. Trigger on: "review these ACs", "check if these acceptance criteria are good", "validate my user story criteria", "improve our acceptance criteria", "audit these requirements", "do these ACs pass review", or similar requests. Also use proactively when someone shares acceptance criteria that look hastily written or vague. The skill analyzes criteria against five key dimensions (clarity, testability, outcome-focus, measurability, independence), scores issues by severity (critical/major/minor), and generates a structured report. It can also rewrite poor criteria into better ones or convert them to user story format.
felipecabargas/gambit/skills/write-feature-request Skill
2★ repoGuided Feature Request (FR) authoring. Assists the user in writing a high-quality FR by collecting structured inputs (problem, solution, outcomes, requirements), then auto-generates Acceptance Criteria for every requirement. If any AC cannot be written due to missing information, the skill identifies the gaps and prompts the user. Returns a polished FR in Markdown with nested ACs, open questions, and risks. Use this skill whenever a user needs to author or improve a feature request. Trigger on: "write a feature request", "help me write an FR", "create a feature spec", "draft a feature proposal", "I want to define a new feature", "turn this idea into a feature request", or similar requests.
felipecabargas/gambit/skills/write-okrs Skill
2★ repoGenerate well-structured OKRs from a product strategy. Derives Objectives and Key Results from strategy pillars, challenges vague KRs, distinguishes outputs from outcomes, and links each OKR back to the strategy pillar it serves. Trigger on: "write our OKRs", "help me set OKRs for this quarter", "turn this strategy into OKRs", "what should our key results be", "draft Q[N] OKRs", or after completing write-product-strategy.
felipecabargas/gambit/skills/write-product-strategy Skill
2★ repoGenerate comprehensive product strategy documents aligned with business goals. Use this when defining or updating your product's strategic direction, aligning teams on where to play and how to win, or creating a STRATEGY.md that bridges vision and execution. Triggers include: clarifying product strategy, articulating competitive positioning, defining strategic pillars, creating alignment documents, or answering 'what are we betting on as a company?' This skill scans existing project docs (roadmaps, market research, competitive analyses) to inform strategy, then either creates a new STRATEGY.md or updates an existing one.
felipecabargas/gambit/skills/write-roadmap Skill
2★ repoCreate a horizon-based product roadmap from strategy and OKRs. Organises work into Now/Next/Later themes derived from strategy pillars, marks items as committed vs. directional, and avoids fake precision (no hard dates unless explicitly provided). Trigger on: "write a roadmap", "create our ROADMAP.md", "help me plan the next few quarters", "what should we build and when", "turn this strategy into a roadmap", "build a Now/Next/Later plan", or after write-okrs.
felipecabargas/gambit/skills/write-stakeholder-update Skill
2★ repoWrite a concise, data-led PM status update for leadership. Leads with a clear status signal (on track / at risk / blocked), surfaces concrete impact with numbers, shows OKR progress, flags decisions needed, and fits on one page. Trigger on: "write a stakeholder update", "draft my weekly PM update", "write a status update for leadership", "what should I tell leadership this week", "write my monthly PM report", or after a sprint-review session.
felipecabargas/gambit/skills/write-technical-brief Skill
2★ repoWrite an engineering handoff document from a verified Feature Request. Covers scope boundaries, technical constraints, edge cases with recommended handling, open questions engineering needs answered, and integration points. Bridges PM spec and engineering without designing the solution. Trigger on: "write a technical brief", "help me hand this off to engineering", "what does eng need to know to build this", "create a technical handoff doc", "make this FR ready for the engineering team", or at the end of a feature request authoring session.
trycomp-io/comp-skills/skills/people-strategy-okr-builder Skill
2★ repoConstrói a estratégia de People + OKRs amarrados à estratégia de negócio. Coleta conversacionalmente prioridades de negócio, dores de people, contexto de headcount/crescimento, horizonte e restrições, e gera um one-pager: 3-5 prioridades estratégicas, cada uma ligada a um objetivo de negócio, com Objective, 2-4 Key Results mensuráveis, iniciativas, owner e métrica, mais riscos e dependências e um roadmap trimestral. Output HTML one-pager + markdown. Dual-mode: works in Claude Code (Python script renderiza HTML rico) AND Claude Cowork (coleta conversacional + markdown output, plus a self-contained HTML artifact when artifacts are available). Trigger em "estratégia de people", "people strategy", "construir OKRs de RH", "OKRs de people", "estratégia de RH na uma página", "people strategy on a page", "amarrar RH à estratégia". Mantida pela Comp.
trycomp-io/comp-skills/skills/workforce-headcount-plan Skill
2★ repoPlano de headcount forward-looking amarrado ao crescimento, o artefato estratégico de workforce planning pra CHRO/Head de People/RH. A partir do headcount atual (total ou por função) + um driver de crescimento (receita-alvo OU % de crescimento OU headcount-alvo) + ratios opcionais (receita por colaborador, função:função, span de gestão), projeta o headcount necessário por função por trimestre, net new hires (incluindo backfill por attrition), custo incremental de folha, e 3 cenários (Conservador/Base/Agressivo). Mantida pela Comp. Dual-mode: works in Claude Code (Python script + rich HTML) AND Claude Cowork (inline calculation + markdown, plus HTML artifact when available). Trigger em "plano de headcount", "workforce planning", "planejamento de quadro", "quantas pessoas preciso contratar", "headcount plan", "hiring plan", "plano de contratação", "dimensionar equipe", "headcount por função", "quanto vai custar crescer o time".
rampstackco/claude-skills-starter/skills/content-strategy Skill
2★ repoDevelop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.
The same file is in 2 other repositories
rampstackco/claude-skills-starter/skills/pm-spec-writing Skill
2★ repoTranslate ideas, feature requests, or vague concepts into specific, actionable dev briefs. Use this skill whenever the user has an idea they want to build, a feature to spec out, a bug to file, a project to scope, or needs to convert a half-formed idea into a clear implementation brief. Triggers on I want to add, we should build, can we make, what is the plan for, how do we implement, dev brief, feature spec, PRD, user story, acceptance criteria, scope this, prioritize. Also triggers when the user has a list of things they want to build and needs help converting them into well-formed tasks.
The same file is in 2 other repositories
rampstackco/claude-skills-starter/skills/seo-keyword Skill
2★ repoRun keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I write about, target keyword, primary keyword, secondary keyword, long-tail. Also triggers when planning a content calendar or new site without keywords yet defined.
The same file is in 2 other repositories
raja21068/AutoResearch/skills/aris/experiment-plan Skill
2★ repoTurn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `research-refine`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/figure-spec Skill
2★ repoGenerate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says "架构图", "workflow 图", "pipeline 图", "确定性矢量图", "figure spec", "draw architecture", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture/workflow figures.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/grant-proposal Skill
2★ repoDraft a structured grant proposal from research ideas and literature. Supports KAKENHI (Japan), NSF (US), NSFC (China, including 面上/青年/优青/杰青/海外优青/重点), ERC (EU), DFG (Germany), SNSF (Switzerland), ARC (Australia), NWO (Netherlands), and generic formats. Use when user says "write grant", "grant proposal", "申請書", "write KAKENHI", "科研費", "基金申请", "写基金", "NSF proposal", or wants to turn research ideas into a funding application.
raja21068/AutoResearch/skills/aris/paper-plan Skill
2★ repoGenerate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
raja21068/AutoResearch/skills/aris/paper-writing Skill
2★ repoWorkflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → figure-spec/paper-illustration/mermaid-diagram → paper-write → paper-compile → auto-paper-improvement-loop to go from a narrative report to a polished PDF. At `— effort: max | beast` (or explicit `— assurance: submission`), Phase 6 gates the Final Report on `tools/verify_paper_audits.sh`; the PDF is labelled `submission-ready` only when the external verifier is green. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.
raja21068/AutoResearch/skills/aris/research-refine-pipeline Skill
2★ repoRun an end-to-end workflow that chains `research-refine` and `experiment-plan`. Use when the user wants a one-shot pipeline from vague research direction to focused final proposal plus detailed experiment roadmap, or asks to "串起来", build a pipeline, do it end-to-end, or generate both the method and experiment plan together.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex-claude-review/paper-plan Skill
2★ repoGenerate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex-gemini-review/grant-proposal Skill
2★ repoDraft a structured grant proposal from research ideas and literature. Supports KAKENHI (Japan), NSF (US), NSFC (China, including 面上/青年/优青/杰青/海外优青/重点), ERC (EU), DFG (Germany), SNSF (Switzerland), ARC (Australia), NWO (Netherlands), and generic formats. Use when user says "write grant", "grant proposal", "申請書", "write KAKENHI", "科研費", "基金申请", "写基金", "NSF proposal", or wants to turn research ideas into a funding application.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex-gemini-review/paper-plan Skill
2★ repoGenerate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex/ablation-planner Skill
2★ repoUse when main results pass result-to-claim (`claim_supported = yes` or `partial`) and ablation studies are needed for paper submission. A secondary Codex agent designs ablations from a reviewer's perspective; the local executor reviews feasibility and implements.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex/experiment-plan Skill
2★ repoTurn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `research-refine`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.
The same file is in 2 other repositories
raja21068/AutoResearch/skills/aris/skills-codex/figure-spec Skill
2★ repoGenerate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says "架构图", "workflow 图", "pipeline 图", "确定性矢量图", "figure spec", "draw architecture", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture/workflow figures.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex/grant-proposal Skill
2★ repoDraft a structured grant proposal from research ideas and literature. Supports KAKENHI (Japan), NSF (US), NSFC (China, including 面上/青年/优青/杰青/海外优青/重点), ERC (EU), DFG (Germany), SNSF (Switzerland), ARC (Australia), NWO (Netherlands), and generic formats. Use when user says "write grant", "grant proposal", "申請書", "write KAKENHI", "科研費", "基金申请", "写基金", "NSF proposal", or wants to turn research ideas into a funding application.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex/paper-plan Skill
2★ repoGenerate a structured paper outline from review conclusions and experiment results. Use when user says \"\u5199\u5927\u7eb2\", \"paper outline\", \"plan the paper\", \"\u8bba\u6587\u89c4\u5212\", or wants to create a paper plan before writing.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/skills-codex/paper-writing Skill
2★ repoWorkflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → figure-spec/paper-illustration/mermaid-diagram → paper-write → paper-compile → auto-paper-improvement-loop to go from a narrative report to a polished PDF. At `— effort: max | beast` (or explicit `— assurance: submission`), Phase 6 gates the Final Report on `tools/verify_paper_audits.sh`; the PDF is labelled `submission-ready` only when the external verifier is green. Use when user says "写论文全流程", "write paper pipeline", "从报告到PDF", "paper writing", or wants the complete paper generation workflow.
raja21068/AutoResearch/skills/aris/skills-codex/research-refine-pipeline Skill
2★ repoRun an end-to-end workflow that chains `research-refine` and `experiment-plan`. Use when the user wants a one-shot pipeline from vague research direction to focused final proposal plus detailed experiment roadmap, or asks to "\u4e32\u8d77\u6765", build a pipeline, do it end-to-end, or generate both the method and experiment plan together.
The same file is in 2 other repositories
raja21068/AutoResearch/skills/aris/skills-codex/specification-writing Skill
2★ repoWrite the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
The same file is in 1 other repository
raja21068/AutoResearch/skills/aris/specification-writing Skill
2★ repoWrite the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
The same file is in 1 other repository
ShreyasBh02/AI-Skills-Collection/daily-planner-prioritizer Skill
no license2★ repoCreates a smart, time-blocked daily plan from a user's task dump, meetings, errands, habits, and goals — then outputs BOTH a clean text summary in chat AND a formatted Excel (.xlsx) schedule file. Covers work tasks, meetings, personal errands, health/exercise reminders, and QA-specific tasks (test runs, bug triage, reviews). Use this skill whenever the user mentions: "plan my day", "prioritize my tasks", "make a schedule", "I have too much to do", "help me organize today", "daily planner", "time block my day", "what should I do first", "morning routine", "task list for today", or dumps a list of things to do. Always trigger even for partial inputs — a rough list of tasks is enough to generate a useful plan. The more context given, the better, but never require it.
ShreyasBh02/AI-Skills-Collection/test-case-generator Skill
no license2★ repoGenerates comprehensive, structured test cases from feature descriptions, user stories, requirements, or acceptance criteria — and exports them as a formatted Excel (.xlsx) file ready for use in Excel or Google Sheets. Use this skill whenever the user mentions: "write test cases", "generate test cases", "create test scenarios", "test coverage", "QA testing", "test a feature", "test this requirement", "positive/negative test cases", "edge cases", "boundary value testing", or shares a user story / requirement and wants it tested. Also trigger when user says "I need to test X" or pastes a Jira story, BRD, or PRD excerpt expecting test output. Always use this skill for test case creation — even if the request seems simple, a structured Excel output is almost always more useful.
CookiesHaha/ash-claude-skills/plugins/ash-workflow/skills/lark-workflow-prd-sync Skill
2★ repoPRD 文档工作流:从飞书下载 PRD → 本地 .md 落盘(含 YAML frontmatter)→ 提取评论为 Open Questions → 依据 §4 需求详细设计更新 §3.1 整体变更与 §5 功能清单 → 将三个章节增量同步回飞书(严禁覆盖 §4 需求详细设计)。支持增量同步:识别评论 is_solved 状态,删除本地已解决评论标记并更新 OQ 状态;按变更大小自动维护版本号(小版本 +0.1 / 大版本 +1.0)。触发关键词:prd sync / prd同步 / 从飞书下载PRD / 更新PRD
Lark workflow prd to userstory
CookiesHaha/ash-claude-skills/plugins/ash-workflow/skills/lark-workflow-prd-to-userstory Skill
2★ repoPRD 转 User Story 工作流:把 PRD §5 功能清单生成 P0 User Story、写入飞书需求矩阵 Base 表,并同步到飞书项目对应版本中。当用户需要从 PRD 同步需求到飞书需求矩阵和飞书项目、prd-to-userstory、把功能清单转成 user story、按版本批量创建需求、对齐需求矩阵与需求管理时使用。