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

  • Story implementation planner

    n-n-code/n-n-code-skills/.agents/skills/story-implementation-planner Skill

    4★ repo

    Model-aware implementation planning workflow for turning a clarified story card plus repo context into an actionable plan for a human or coding agent. Use after user-story-clarifier and story-repo-scout when a story needs ordered implementation steps; avoid for story drafting, repo scouting alone, or direct code implementation.

  • Thinking

    n-n-code/n-n-code-skills/.agents/skills/thinking Skill

    4★ repo

    Structured thinking skill. Merges ideation, systems analysis, critical reasoning, and convergent planning. Use when a user needs to explore and narrow a vague idea, challenge assumptions, compare approaches, or converge on a practical next move in the same pass. Do not use when sustained divergence alone is the goal or when a candidate plan already exists and needs adversarial stress-testing.

  • User story clarifier

    n-n-code/n-n-code-skills/.agents/skills/user-story-clarifier Skill

    4★ repo

    Workflow for drafting, rewriting, splitting, and auditing story-level requirements, user stories, feature definitions, definitions of done, and acceptance criteria into unambiguous story cards for humans and coding agents. Use for rough tickets, broad epics, or unclear product behavior; avoid for full PRDs, glossary definitions, and code implementation.

  • Seo content brief

    01clauding/claude-seo-skill/skills/seo-content-brief Skill

    4★ repo

    Generate comprehensive, SERP-driven content briefs for writers. Analyzes top-ranking competitors, identifies content gaps, specifies structure, word count, keywords, E-E-A-T requirements, AI citation readiness, and schema recommendations. Use when user says "content brief", "writing brief", "content outline", "article brief", or "create brief for".

  • Seo keyword research

    01clauding/claude-seo-skill/skills/seo-keyword-research Skill

    4★ repo

    Comprehensive keyword research methodology covering seed keyword expansion, search volume and difficulty analysis, competitor keyword gap discovery, topic clustering, search intent classification, and keyword prioritization. Use when user says "keyword research", "find keywords", "keyword analysis", "keyword strategy", "topic clusters", or "keyword gap".

  • Seo plan

    01clauding/claude-seo-skill/skills/seo-plan Skill

    4★ repo

    Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", or "SEO roadmap".

  • Doccraft story

    alexpialetski/doccraft/.claude/skills/doccraft-story Skill

    4★ repo

    Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under docs/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under docs/stories/ — even if they call it a spec, ticket, backlog row, or planning doc.

  • Doccraft story

    alexpialetski/doccraft/templates/skills/doccraft-story Skill

    4★ repo

    Author or update product stories (a.k.a. planning docs, backlog items, tickets, specs) as Markdown under {{DOCS_DIR}}/stories/ with a YAML frontmatter contract (id, status, impact, urgency, depends_on, tags, openspec). Use this whenever the user is creating a story, reprioritising work, writing acceptance criteria, linking a story to OpenSpec or an ADR, or editing anything under {{DOCS_DIR}}/stories/ — even if they call it a spec, ticket, backlog row, or planning doc.

  • Proposal design

    Amalia6767/curator-skills/skills/proposal-design Skill

    4★ repo

    基于 tender-analysis 输出与答疑/会议纪要/新增需求等增量材料,遵循“策展五力”模型生成可投标的方案设计(Word/PPT/网页)。

  • Proposal interpretation

    Amalia6767/curator-skills/skills/proposal-interpretation Skill

    4★ repo

    将策划方案转化为内部讲解文档,用于向团队内部其他人员快速传达核心理念与思路。简洁有力、理念清晰、创意明确,避免冗长解释。

  • Postkit new

    Trystan-SA/postkit/templates/project/.claude/skills/postkit-new Skill

    4★ repo

    Draft a new post (single image, carousel, or a series) from a brief. Reads the brand profile from memory/brand_*.md plus theme.css, interviews the user, proposes the best format, then writes posts/<slug>/ with post.json, caption files, and slide HTML. Use when the user wants to create content, draft an image post, make a carousel, or plan a multi-post campaign.

  • Wikispec plan

    christianb93/WikiSpec/skills/wikispec-plan Skill

    4★ repo

    Create a tasks list to prepare for the implementation of a change. Use this before implementation to understand what needs to be done

  • Couchbase backup restore

    celticht32/Couchbase-Skills-for-Claude.ai/skills/couchbase/couchbase-backup-restore Skill

    4★ repo

    Plan and execute Couchbase backup and restore operations. Use whenever the user asks about backup, restore, cbbackupmgr, backup repository, backup archive, full backup, incremental backup, differential backup, backup schedule, retention policy, backup verification, Capella managed backup, backup to S3, backup to filesystem, restoring a bucket, restoring specific documents, admin_backup_* tools, or 'how do I back up / restore Couchbase.' Distinct from couchbase-migration-execution (one-time data migration to a new cluster) and couchbase-mcp (operating the tools). Use proactively for DR planning, RPO/RTO requirements, backup verification workflows, and pre-upgrade snapshots.

  • Couchbase sizing

    celticht32/Couchbase-Skills-for-Claude.ai/skills/couchbase/couchbase-sizing Skill

    4★ repo

    Size Couchbase clusters, plan capacity, and pick the right Capella tier. Use whenever the user asks about sizing, capacity planning, RAM quota, working set, replicas, node count, scale up vs scale out, how much memory / disk / network is needed, Capella tier selection, GSI / FTS / vector index memory, eventing memory budget, or 'will this fit.' Triggers on numerical planning questions distinct from the couchbase-mcp skill (which operates an existing cluster) and the couchbase-data-modeling skill (which designs document shape). Use proactively for: planning a new deployment, deciding whether to scale up or out, right-sizing a Capella tier, estimating storage growth, planning for burst load, sizing for vector search, calculating XDCR bandwidth, deciding replica count, planning multi-service node mix, estimating eventing memory footprint, and any question that starts with 'how much' or 'how many nodes.'

  • Couchbase upgrade

    celticht32/Couchbase-Skills-for-Claude.ai/skills/couchbase/couchbase-upgrade Skill

    4★ repo

    Plan and execute Couchbase Server version upgrades, including rolling upgrades and the specific considerations for upgrading to 8.0. Use whenever the user asks about upgrading Couchbase, rolling upgrade, upgrade path, upgrade from 7.x to 8.0, upgrade checklist, cluster compatibility version, Magma storage engine default change in 8.0, 128 vBucket change in 8.0, EE features required for 8.0 defaults, pre-upgrade backup, post-upgrade verification, or 'how do I upgrade Couchbase without downtime.' Distinct from couchbase-mcp (which has an operational-runbooks reference covering rolling upgrade mechanics via MCP tools). This skill covers the planning, compatibility, and 8.0-specific breaking changes that require attention before and after the MCP-level upgrade steps.

  • Planning with files

    sefaertunc/Worclaude/.claude/skills/planning-with-files Skill

    4★ repo

    How to structure implementation plans as files, progressive implementation, plan review process

  • Decision toolkit

    DjordjeMojsilovic/Djordjes-Claude-Setup/decision-toolkit Skill

    no license4★ repo

    Structured decision-making frameworks for complex, high-stakes, or ambiguous choices. Use when the user needs to make a significant decision and would benefit from a formal framework — business strategy, tech architecture, career moves, startup pivots, build-vs-buy, prioritization. Activate on: "how should I decide", "help me think through", "what framework", "prioritize these", "should we build or buy", "is this worth it". Provides: RICE scoring, decision matrices, pre-mortem analysis, second-order thinking prompts, and synthesis into a clear recommendation.

  • Spec flow main

    medalsoftchina/workcopilot/embedded-skills/spec-flow-main Skill

    4★ repo

    Interactive spec-driven development workflow with phase-by-phase confirmation. Each phase waits for user confirmation before proceeding. Trigger phrases include "spec-flow", "spec mode", "need a plan", or "structured development". Creates .spec-flow/ directory with proposal, requirements, design, and tasks documents.

  • Plan content

    warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/plan-content Skill

    no license4★ repo

    Use when user wants to think strategically about LinkedIn content rather than post-by-post: starting a LinkedIn presence from scratch, posting feels scattered or unfocused, or before committing to a consistent posting routine. Trigger phrases include "help me plan my LinkedIn content," "what should I be posting about regularly," "define my content pillars," "build a content calendar," "I post randomly and it's not working."

  • Build

    kborovik/pilot-skills/pilot-spec/skills/build Skill

    no license4★ repo

    Plan-then-execute impl vs SPEC.md. Triggers when user asks to build, implement, or execute spec or specific §T task. Phrasings: "build §T.<n>", "build --next", "implement next task", "run the build", "does the implementation run?", "is §T.<n> done?".

  • Glyph

    kborovik/pilot-skills/pilot-spec/skills/glyph Skill

    no license4★ repo

    Math-glyph encoding — LLM-facing compression for SPEC.md and spec-adjacent writes. Loaded by /sdd:spec, /sdd:build, /sdd:check. Triggers on any write to SPEC.md or user says "math-glyph", "glyph", "compress this", "be brief".

  • Spec

    kborovik/pilot-skills/pilot-spec/skills/spec Skill

    no license4★ repo

    Sole mutator of SPEC.md @ repo root — create, amend, or backprop bugs. Triggers when user asks to write spec, start new spec, distill spec from code, add invariants, amend a section, or record a bug. Common phrasings: "write the spec for...", "new spec", "distill spec from code", "spec this idea", "import existing repo", "pull invariants out of code", "this bug keeps biting", "post-mortem on Y".

  • Vr planner

    mpagot/os-autoinst-distri-opensuse-skills/skills/vr-planner Skill

    no license4★ repo

    Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML schedules, and openqa-clone-job commands.

  • Career gap planner

    agentsope/career-skills/skills/career-gap-planner Skill

    4★ repo

    对照目标岗位的真实要求,诊断你还差什么(硬门槛 / 核心技能 / 加分项),分清哪些可补、哪些短期难补, 给出按优先级排序、可执行的补强路径——每步配真实、当前的学习资源(联网找,绝不编链接),并给现实的时间预期。 诚实:短期补不上的(如学历 / 年限)如实说 + 给绕过策略,不灌鸡汤、不画饼。补成的技能 / 项目可回流写进简历。 承接 career-jd-analyzer 的能力模型 + 你的现状。默认结果优先。 Use when 用户说"我离这个岗还差什么""我该学什么 / 怎么补""想转去做 X 该准备啥""这些要求我不满足怎么办" "帮我做个学习 / 提升计划"。 触发词:差什么、该学什么、怎么补、学习计划、提升计划、能力差距、转行准备、技能提升、gap、零基础怎么学。 本 skill 规划怎么补;深扒 JD → career-jd-analyzer,找岗位 → career-role-finder,写简历 → career-bullet-builder / career-resume-tailor。

  • Writing plans

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/engineering/skills/writing-plans Skill

    4★ repo

    Turn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context. Breaks work into bite-sized steps with exact file paths, real code, and verification commands. Use before starting a multi-step build, once you know what you're building.

  • Brainstorming

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/productivity/skills/brainstorming Skill

    4★ repo

    Turn a rough idea into a fully formed, written design through collaborative dialogue — exploring intent, requirements, and trade-offs one question at a time, then proposing approaches and capturing the agreed design in a spec before any code is written. Use at the start of any creative or feature work, when the idea isn't yet concrete enough to plan or build.

  • Writing plans

    KhaledSaeed18/dotclaude/skills/engineering/writing-plans Skill

    4★ repo

    Turn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context. Breaks work into bite-sized steps with exact file paths, real code, and verification commands. Use before starting a multi-step build, once you know what you're building.

  • Brainstorming

    KhaledSaeed18/dotclaude/skills/productivity/brainstorming Skill

    4★ repo

    Turn a rough idea into a fully formed, written design through collaborative dialogue — exploring intent, requirements, and trade-offs one question at a time, then proposing approaches and capturing the agreed design in a spec before any code is written. Use at the start of any creative or feature work, when the idea isn't yet concrete enough to plan or build.

  • Writing plans

    izyanrajwani/agent-skills-library/skills/writing-plans Skill

    no license4★ repo

    Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.

    The same file is in 8 other repositories

  • Content patterns

    openEHR/ai-plugins/plugins/openehr-specs/skills/content-patterns Skill

    4★ repo

    Patterns for writing production-quality openEHR specification prose — overviews, class/concept semantics, design rationale, and clinical examples — in `specifications-XX` repos. This skill should be used when the user asks how to phrase or improve spec prose, draft a package/class description, write a design-rationale or semantics section, or asks about openEHR spec writing style. Not for creating or scaffolding the document or its structure (use authoring), amendment records (use amendment-record), or non-openEHR writing.

  • Governance

    openEHR/ai-plugins/plugins/openehr-specs/skills/governance Skill

    4★ repo

    Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's status, or discuss the openEHR change process or Jira workflow. Not for clinical/archetype governance, amendment-record authoring (use amendment-record), or non-openEHR release management.

  • Review

    openEHR/ai-plugins/plugins/openehr-specs/skills/review Skill

    4★ repo

    Review an openEHR specification document for quality, completeness, and convention compliance in `specifications-XX` repos. This skill should be used when the user asks to review, lint, or quality-check an openEHR spec, validate its conventions, or run a pre-release review. Not for archetype/template review (openehr-assistant plugin), the governance process (use governance), or non-openEHR documents.

  • Feature retirement comms planner

    akhilkannur/marketing-agent-blueprints/skills/feature-retirement-comms-planner Skill

    no license4★ repo

    Identifies users dependent on a feature being removed. Drafts a timeline of 3 emails: 'Heads up', 'Alternative Workflows', and 'Final Reminder'.

  • Spec writing

    Lion-1209/Lion-Skills/skills/spec-writing Skill

    4★ repo

    需为非平凡功能/重构写设计文档(spec/design doc/RFC)时。

  • Task breakdown

    Lion-1209/Lion-Skills/skills/task-breakdown Skill

    4★ repo

    需把需求拆成可执行任务并排依赖时。

  • Strategy

    Epistates/sparX/.claude/skills/strategy Skill

    4★ repo

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

  • Abm campaign builder

    matellez/claude-skills/revops/abm-campaign-builder Skill

    4★ repo

    AUTO-TRIGGER: Apply this skill when the user wants to build, plan, or improve an account-based marketing program. Trigger phrases include: "ABM campaign," "named account targeting," "target account list," "account-based," "we want to go after specific accounts," "enterprise accounts," "1:1 or 1:few marketing," or any request to build a coordinated sales and marketing program around a defined account list rather than broad demand generation. Also trigger when the user asks how to align sales and marketing around specific accounts or how to measure account penetration rather than lead volume. Do NOT trigger for general demand gen, inbound, or broad campaign planning that is not account-specific.

    The same file is in 1 other repository

  • Gtm ai adoption rollout

    matellez/claude-skills/revops/gtm-ai-adoption-rollout Skill

    4★ repo

    AUTO-TRIGGER: Apply this skill when the user is planning, executing, or troubleshooting an AI tool rollout for a sales or marketing team. Trigger phrases include: "rolling out AI to our team," "getting our reps to use," "nobody is using the tool," "AI adoption is low," "how do I get buy-in," "rolling out HubSpot," "Salesloft rollout," "ZoomInfo training," "tool adoption," "change management," or any request about getting a GTM team to actually use a new tool or workflow. Also trigger when the user is evaluating which AI tools to roll out, or when they have been given responsibility for a company-wide AI initiative without a clear implementation plan. Do NOT trigger for general AI tool comparisons, software procurement questions, or requests to learn how a specific tool works. This skill is about the organizational adoption problem, not the tool itself.

    The same file is in 1 other repository

  • Intent data activation

    matellez/claude-skills/revops/intent-data-activation Skill

    4★ repo

    AUTO-TRIGGER: Apply this skill when the user is working with intent data signals from ZoomInfo, Bombora, G2, 6sense, Demandbase, or any similar platform, and needs to operationalize those signals into CRM workflows, campaign enrollment, rep alerts, or account prioritization. Trigger phrases include: "intent data," "ZoomInfo intent," "Bombora signals," "G2 buyer intent," "in-market accounts," "activating intent," "intent signals aren't doing anything," "we're paying for intent data but not using it," "how do I route intent accounts," "intent-based campaigns," or any situation where the user has intent data and needs to turn it into action. Also trigger when the user is evaluating which intent signals to act on, designing CRM workflows to handle signal ingestion, or trying to measure whether their intent activation is producing results. Do NOT trigger for general ABM strategy, ZoomInfo data enrichment questions, or lead scoring without intent signals. This skill is specifically about the workflow layer between receiving an intent signal and taking an action.

    The same file is in 1 other repository

  • Supreme council

    davccavalcante/supreme-coding-guidelines-skill.ah/skills/supreme-council Skill

    no license4★ repo

    Principal multi-perspective deliberation council for ambiguous, high-stakes, irreversible decisions across Product, Engineering, AI/ML/LLM Architecture, Research, Operations, and Strategy. Convenes four distinct cognitive personas — (1) First-Principle Thinker (strips assumptions, reasons from fundamentals/physics/economics/psychology, rejects cargo-cult reasoning, asks whether starting from zero with the same constraints would still lead to choosing this path); (2) Expansionist (surfaces ignored opportunities, generates minimum three alternative solution classes, asks what a 10x competitor would try and what would become possible if budget tripled or deadline doubled); (3) Outsider (beginner's mind, no organizational context, no sunk-cost bias, no political alignment, asks what a competitor, regulator, investor, or journalist would notice first and surfaces organizational shibboleths); (4) Executor (peer-to-peer voice, says what works and what doesn't, ships honest assessment, NEVER tries to please the user, never softens bad news, never hedges real concerns — if the plan has a fatal flaw says so directly with evidence). Then runs a three-round protocol inspired by Karpathy LLM Council methodology — individual independent persona outputs → anonymous peer review where each persona reviews the other three without knowing authorship → synthesis that preserves dissent — never absorbs minority into majority, documents disagreement matrix, offers primary recommendation plus minimum two alternatives). Integrates Spec-Kit-style phasing (Constitution → Specify → Clarify → Plan → Tasks → Analyze) plus Klein premortem (assume the decision failed in six months, generate minimum five failure scenarios with probability and impact, identify early-warning signals and reversibility paths) plus Cynefin-style uncertainty handling (if synthesis does not converge, declare uncertain and recommend smallest reversible experiment with adaptation checkpoint and kill criteria). Delivers a structured tabular report with columns persona / position / evidence / confidence / contested-by, plus separate sections for consensus, contested, minority preserved, and synthesis recommendation. Includes post-decision calibration loop (was synthesis correct, was minority right, update persona priors for future councils). Requires ah-parser. Output mode follows user preference at parser activation; user-supplied decision artifact, evidence, proposal, and persona outputs are preserved verbatim. Honest assessment over comfortable answer — non-negotiable.

  • Feature launch playbook

    rampstackco/claude-skills-pm/skills/feature-launch-playbook Skill

    4★ repo

    The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.

    The same file is in 1 other repository

  • Jtbd framing

    rampstackco/claude-skills-pm/skills/jtbd-framing Skill

    4★ repo

    The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.

    The same file is in 1 other repository

  • Okr design

    rampstackco/claude-skills-pm/skills/okr-design Skill

    4★ repo

    OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition with quarterly accountability). Triggers on OKR design, OKR setting, key result design, OKR scoring, mid-quarter recalibration, OKR cascading, outcomes vs outputs, quarterly planning, goal setting. Also triggers when a team's OKRs are always hit and producing no learning, when OKRs are demoralizing because they were set as fantasy, or when the team uses OKR vocabulary but the practice has decayed.

    The same file is in 1 other repository

  • Pm spec writing

    rampstackco/claude-skills-pm/skills/pm-spec-writing Skill

    4★ repo

    Translate 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

  • Roadmap planning

    rampstackco/claude-skills-pm/skills/roadmap-planning Skill

    4★ repo

    Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.

    The same file is in 1 other repository

  • Stakeholder communication

    rampstackco/claude-skills-pm/skills/stakeholder-communication Skill

    4★ repo

    Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on stakeholder update, status report, executive summary, exec review, manage up, communicate bad news, project comms, status meeting, weekly update. Also triggers when a project is going off track and the team needs to communicate it.

    The same file is in 1 other repository

  • Plan execute

    erhwenkuo/stock_skills/.claude/skills/plan-execute Skill

    no license4★ repo

    Plan Mode — Orchestrator oversees workflow design, execution, autonomous loop, and review. Activated when told "in plan mode."

  • Spec

    ananthanandanan/skills/skills/engineering/spec Skill

    4★ repo

    Turn a rough product idea (or the output of /ank:third-degree) into a single, opinionated SPEC.md that serves as the source of truth for an entire product or feature. Use whenever the user invokes /ank:spec, says "let's design this", "draft a spec", "write the design doc", "turn this into a tech spec", or otherwise signals they want the idea crystallised into a reviewable document before tasks or code. The skill produces ONE file (SPEC.md at repo root for product-level specs, or docs/spec/<slug>.md for feature-level) and then HARD STOPS, waiting for explicit approval before any downstream skill (/ank:tasks) runs.

  • Third degree

    ananthanandanan/skills/skills/engineering/third-degree Skill

    4★ repo

    Interview the user to converge on a shared, concrete understanding of a feature before any planning or implementation — the front of the ank pipeline (third-degree → visualise-plan → review-board). Use whenever the user invokes /ank:third-degree, says they have a "rough idea", asks you to "flush out the requirements", "interview me", "interrogate me", or otherwise signals the spec is fuzzy and needs pinning down before code or a plan is written.

  • Visualise plan

    ananthanandanan/skills/skills/engineering/visualise-plan Skill

    4★ repo

    Produce a visual HTML implementation plan for a feature BEFORE writing any code. Use this skill whenever the user invokes /ank:visualise-plan, asks for an "implementation plan", says "plan this out before you build it", asks you to "visualise the plan", or otherwise signals they want to review the approach as a document before code is written. The skill assumes all clarifying questions about the feature have already been answered in this conversation — its job is to crystallise that context into a single reviewable HTML file at docs/plan/<feature-slug>.html and then HARD STOP, waiting for the user to type "approved" (or send edits) before any implementation begins.

  • Launch planning

    Dragoon0x/product-skills/skills/execution-discipline/launch-planning Skill

    no license4★ repo

    Plan and execute product launches that actually drive adoption, not just announcements. Covers launch tiers, cross-functional coordination, rollout strategy, and post-launch monitoring. Use when preparing a feature or product launch, coordinating across teams, or when past launches haven't moved the needle.

  • Prioritization frameworks

    Dragoon0x/product-skills/skills/organisation-prioritization/prioritization-frameworks Skill

    no license4★ repo

    Apply structured prioritization methods to decide what to build and what to cut. Covers RICE, ICE, MoSCoW, and knowing when each framework fits. Use when the backlog is overwhelming, stakeholders disagree on priorities, or when everything feels like P0.

  • Time energy management

    Dragoon0x/product-skills/skills/organisation-prioritization/time-energy-management Skill

    no license4★ repo

    Manage PM time and energy across competing demands without burning out or dropping critical work. Covers prioritization of PM activities, calendar discipline, and sustainable pace. Use when overwhelmed by meetings, losing time to reactive work, or when important strategic work keeps getting pushed.

  • Prd writing

    Dragoon0x/product-skills/skills/pm-communication/prd-writing Skill

    no license4★ repo

    Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.

  • Stakeholder updates

    Dragoon0x/product-skills/skills/pm-communication/stakeholder-updates Skill

    no license4★ repo

    Write status updates that executives actually read and act on. Covers structure, signal-to-noise ratio, and knowing what to escalate versus what to summarize. Use when writing weekly updates, project status reports, or board-level summaries.

  • North star setting

    Dragoon0x/product-skills/skills/pm-strategy-vision/north-star-setting Skill

    no license4★ repo

    Define a north star metric and product vision that aligns the team and guides daily decisions. Covers metric selection, vision articulation, and connecting daily work to long-term direction. Use when the team lacks clear direction, metrics feel arbitrary, or people can't explain what success looks like.

  • Roadmap planning

    Dragoon0x/product-skills/skills/pm-strategy-vision/roadmap-planning Skill

    no license4★ repo

    Build and communicate a product roadmap that balances customer needs, business goals, and team capacity. Covers outcome-driven planning, stakeholder communication, and roadmap hygiene. Use when planning quarters, aligning stakeholders on direction, or when the roadmap feels like a feature wishlist.

  • Packaging strategy

    Dragoon0x/product-skills/skills/pricing-monetization/packaging-strategy Skill

    no license4★ repo

    Bundle features into plans that feel natural for each customer segment. Covers feature classification, tier design, upgrade triggers, and avoiding common packaging mistakes. Use when designing tier structure, adding major features, or when upgrade rates are stagnant.

  • Prioritization frameworks

    Dragoon0x/product-skills/skills/prioritization-roadmapping/prioritization-frameworks Skill

    no license4★ repo

    Score and rank product initiatives using RICE, ICE, and value-effort frameworks. Makes prioritization transparent and defensible while acknowledging that math doesn't remove all judgment. Use when the backlog is growing, stakeholders disagree on priorities, or you need to justify decisions to leadership.

  • Roadmap planning

    Dragoon0x/product-skills/skills/prioritization-roadmapping/roadmap-planning Skill

    no license4★ repo

    Build a product roadmap that balances customer needs, business goals, and technical reality. A roadmap is a strategy communicated through planned work, not a feature list with dates. Use when building quarterly or annual plans, when stakeholders pull in different directions, or when the current roadmap feels reactive.