Product & Planning

starforall Skill

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

tdwhere123 Skill

Compatibility alias for earlier do-it skill discovery; select relevant skills directly from their descriptions.

zuozh11 Bundle

将当前对话上下文转化为 PRD。适用于用户要求产出 PRD、需求文档，或说「写个 PRD」「出需求文档」「to-prd」等场景。

45ck Skill

backlog-groomer

45ck Skill

cloud-asset-discovery-planner

45ck Skill

Audit a signup, onboarding, and activation flow to identify friction, missing value discovery, and concrete product/growth fixes.

45ck Skill

Turn interview notes, assumptions, or market context into customer discovery findings, jobs-to-be-done synthesis, and actionable product/GTM recommendations.

cristhianzl Bundle

Author product requirements — PRDs, product specs, one-pagers, PR-FAQs, product briefs — that lead with the problem, define testable success metrics and acceptance criteria, and make non-goals explicit. Use when the user asks to write a PRD, write/define product requirements, write a product spec, write a one-pager, write a PR-FAQ, "write a spec", "define requirements", scope a feature, or draft a product brief. Also use when the request is a half-baked feature idea that needs a problem framed before any solution. Not for engineering design docs / the technical "how" — that is a separate design doc (the PRD owns the what/why, the design doc owns the how).

idkwhatimd0ing Skill

Orchestrate a new project from idea to running scaffold by chaining `domain-to-spec`, `scaffold-frontend`, and optional `scaffold-backend`. Use this skill when the user wants a one-shot setup, full-stack bootstrap, empty-repo starter, or guided path from rough idea to `AGENTS.md`, `PRD.md`, `client/`, and optionally `server/`.

idkwhatimd0ing Skill

Turn a non-coder's domain expertise into `AGENTS.md` and `PRD.md` at the repo root before scaffolding. Use this skill first for new projects, idea-to-spec work, PRD creation, app planning, or when the user describes a profession, workflow, constraint, or outcome and needs a buildable software blueprint.

idkwhatimd0ing Skill

Create a PRD-driven FastAPI backend in `server/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after frontend scaffolding only when `PRD.md` says `Backend Needed?` is Yes, especially for API routes, Pydantic models, health checks, optional Supabase wiring, and type-safe placeholder data.

idkwhatimd0ing Skill

Create a PRD-driven Next.js frontend in `client/` from repo-root `AGENTS.md` and `PRD.md`. Use this skill after `domain-to-spec` when the user wants the initial UI scaffold, pages, navigation, types, and optional API client generated from the confirmed PRD.

idkwhatimd0ing Skill

Turn a PRD, product idea, app description, screenshot brief, or rough UI concept into a high-signal Vercel v0 prompt. Use this skill whenever the user wants a v0 prompt, landing page prompt, app UI generation prompt, visual direction, shadcn/Magic UI/Aceternity guidance, or a more distinctive interface than generic AI output.

conorluddy Bundle

Convert any subject matter — rough feature ideas, brain-dumps, meeting notes, loose PRDs, existing docs — into a rigorous, testable spec written to industry requirements standards (EARS templates, RFC 2119 keywords, INCOSE/ISO 29148 rules, Gherkin acceptance criteria). Use this skill whenever the user wants to write, rewrite, tighten, or formalize a PRD, technical spec, requirements document, or acceptance criteria, or says things like "spec this out", "formalize this", "turn these notes into a spec", "write requirements for", "make this testable", "tighten this doc", or shares loose product thinking that needs to become an unambiguous document. Also use it to audit an existing spec for ambiguity, weak words, and untestable requirements.

cslawyer1985 Skill

将合同审查转化为业务利益方实际会阅读的摘要。不是法律备忘录——是对 "能签吗？需要知道什么？"的两分钟回答。当用户说"给业务部门总结一下" "写给[利益方]"解释给采购""非法务摘要"或审查完成后需要发送给法务以外的人时使用。

futurediffusion Skill

Explicitly save important knowledge to auto-memory with timestamp and context. Use when a discovery is too important to rely on auto-capture.

gastownhall Bundle

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

growilabs Skill

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

growilabs Skill

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.

growilabs Bundle

Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.

lintendo Bundle

Use when the user asks to establish a traceable PRD planning workflow from product links, screenshots, files, spoken requirements, current-product reconstruction, feature additions, redesigns, future requirements, or phased reconstruction-then-expansion work before document scope or count is settled in an Axhub Make client project.

lintendo Bundle

Use when the user explicitly asks to write, draft, create, update, or synthesize a PRD for an Axhub Make client project, especially when the PRD may aggregate multiple prototypes, resources, canvas notes, or existing product context.

lintendo Bundle

原型标注替代 PRD 时使用：把页面目录、组件说明、状态说明和补充文档接入可运行原型，供评审、交付和后续需求说明使用。

jrittelmeyer Bundle

Commit and push pending work, then either continue to the next backlog step (context still healthy) or emit a paste-ready resume prompt plus a recommended relaunch model + reasoning effort for a fresh session (context tight). Use when the user says "checkpoint", "commit and continue", "wrap this step up", or asks whether to keep going vs. clear context.

jrittelmeyer Bundle

Initialize a new product — ingest plan docs or a raw idea, run discovery and competitive research, converge on a product brief, and regenerate the living docs into a build program targeting a 100 audit score. Use on a fresh scaffold from a template, when the user says "init this project" / "here's my idea for an app", or when they hand over plan documents.

jrittelmeyer Bundle

Deep audit of the whole repo — verify docs ↔ code alignment, score each feature group out of 100 against a best-available bar, and emit an exhaustive prioritized backlog that would bring every group to 100. Use when the user asks for a project audit, quality scores, "how good is this really", or "what's missing to make this perfect".

nanmicoder Bundle

Coordinate the complete DeepSeek Harness plugin lifecycle across inspection, host compatibility upgrades, tests, naming and central registry checks, packaging, release, and rollback. Use when a user wants one guided workflow, asks which plugin capabilities to run, requests a pre-run feature menu, or needs several DSH plugin Skills chained with a unified status report. Default to read-only discovery and require separate confirmation before repository writes, dependency or runtime execution, and external publication.

lufigir Bundle

Senior-level architecture for a product, in two modes. **Bootstrap** starts a project from zero (discovery, ERD, layered folders, data access layer, lint guardrails, design tokens) instead of shipping whatever the framework CLI left behind. **Convention** answers architecture questions mid-build so the rules set in week one still hold in week six: where does this file go, may this layer import that one, how do I model this table, does this query stay inside the tenant, is this endpoint safe, why is this route slow. Use when starting/creating/bootstrapping/scaffolding a project, and whenever work touches folder structure, layer boundaries, data access, schema design, migrations, multi-tenancy, API contracts, background jobs, file uploads, security, performance or observability. Use it too for the screens most products are made of — any list, table or feed with filters, sorting, search, pagination or shareable URLs, and any form or mutation (validation errors, pending and optimistic states, cache invalidation a

luisdomarco Skill

Structured interview technique for process discovery using BPM/BPA methods, inverse engineering on vague descriptions, and organized question blocks. Use when age-spe-process-discovery needs to elicit complete, unambiguous process information from the user through a structured dialogue.

maddhruv Bundle

Dependency upgrades: outdated/vulnerable deps planned into semver waves (patch/minor batched, majors gated and changelog-read), applied incrementally with lockfiles regenerated and tests green after each. Runs on green main. Triggers on "absolute upgrade", "upgrade our dependencies", "bump deps", "update packages", "move off the deprecated X", "clear the Dependabot backlog".

mj-deving Skill

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

iabstergo1 Skill

Work the Review-Queue and review_proposals items one by one (lint failure lists, cross-domain promotion candidates, overwrite-protection-rejected change proposals), giving analysis and fix suggestions; the final accept/reject is the user's. Use when the user says "work the review queue / look at the pending items / what's in the Review-Queue / walk me through the review backlog".

iabstergo1 Skill

Distill a recurring ingest/lint failure into a bounded improvement to one skill — read the skill-mine backlog → write a bounded SKILL.md edit on an isolated branch → run skill-gate (pytest + dual-tree parity + gate-integrity) → skill-stage the candidate, leaving skill-adopt to a human. Use when the user says "distill this failure into the skill / evolve a skill / let a skill self-improve / handle skill backlog item N". Only for improving this project's own skills; "summarize this / explain this / translate this / add this book to the KB (that is ingest)" must never trigger it.

nafisrayan Bundle

Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.

bartolli Skill

This skill should be used to write wiki stories — Gherkin scenarios plus a first slice list — from either input: the current conversation, synthesized into a thin `plan/plan-{name}.md` with one `plan/{name}/story-N-{slug}.md` per story; or a promoted intent, elaborated into one story under the active plan with the intent linked and `promoted_to` reported back. Default `triage_state: needs-triage`. Does NOT interview — if intent is unclear it suggests `$intent` and stops. Use when the user says "turn this into a plan", "draft a PRD", "$to-stories", "write up what we discussed", "synthesize this into stories", "write the story for intent X", or "elaborate intent X". Reads `glossary.md` and existing ADRs to use the project's vocabulary correctly.

perhapsspy Bundle

Use when product meaning or implementation-planning direction is materially open before solution structure is settled, including early direction for a new feature, reuse choices, temporary implementations, or another materially consequential product or implementation-planning choice. Choose a bounded provisional direction from user/domain purpose, locked decisions, explicit constraints, authority, current evidence, and observable success. Do not use for settled code structure, implementation execution, source discovery, or document editing.