Product & Planning

eoash Skill

4명의 에이전트 팀(PM → 아키텍트 → 개발자 → 리뷰어)이 순차적으로 기능을 자동 개발한다. 기획서(PRD) → 설계(ARCH) → 코드 → 리뷰까지 완전 자동 파이프라인. "/dev-team", "개발팀으로 만들어줘", "에이전트팀으로 만들어줘", "자동 개발해줘" 요청에 사용.

krzysztofsurdy Bundle

Interactive tool to generate tailored rules and instruction files for any AI coding agent. Use when the user asks to set up agent rules, configure Claude Code instructions, create Cursor rules, write Windsurf rules, generate Copilot instructions, or establish consistent AI coding standards for a team. Supports 13+ agents (Claude Code, Cursor, Windsurf, Copilot, Gemini, Codex, Cline, OpenCode, Continue, Trae, Roo Code, Amp) with global, team-shared, and dev-specific scopes. Defers to the `using-ecosystem` meta-skill for ecosystem discovery (skills, agents, recommendations) and runs an interactive questionnaire for workflow preferences.

krzysztofsurdy Skill

Write a stakeholder Slack/email update message. Use when the user wants to communicate project status, blockers, decisions, or release readiness to stakeholders.

lovstudio Bundle

Maintain the LovStudio website's partners section AND align partner logo rows on event posters / hero strips: reuse sgc-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets cropped), strip embedded background rects from icon-style SVGs, composite icon + wordmark when only an icon is available (using brand fonts), wrap logos in a fixed-size grid box (96×30 with subtle border) for stable matrix layouts, replace existing logos with user-provided files, append new partners to the PARTNERS array with i18n taglines across zh-CN/en/ja/th, and audit the section for dead URLs / missing files / missing translations. Also handles cross-asset visual height parity (multi-logo strips on dark backgrounds, "logo 不等高", unified-color filter recipe). Trigger when the user mentions "合作伙伴", "partners", "trusted by", "新增 logo", "标准化 logo", "替换 logo", "审计合作伙伴", "维护合作伙伴", "logo 不一样高", "logo 对齐", "lo

lovstudio Skill

识别电影或剧集并从多个独立渠道收集、去重、归一化可下载候选；适用于“帮我找这部片的不同版本”、"search releases for this title"，输出可审计的候选清单。

fellowship-dev Bundle

Use when converting a new GitHub issue into a structured PRD, or posting clarifying questions when the issue is underspecified.

fellowship-dev Skill

Use when creating a PRD, writing requirements, or transforming a feature request into an implementation-ready GitHub issue.

fellowship-dev Skill

Use when stress-testing a plan, getting grilled on a design, or before writing a PRD.

iblai Bundle

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see iblai-marketing-analytics-tracking. For page-level conversion optimization, see iblai-marketing-page-cro.

iblai Bundle

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 iblai-marketing-copywriting. For SEO-specific audits, see iblai-marketing-seo-audit. For social media content specifically, see iblai-marketing-social-content.

iblai Bundle

When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see iblai-marketing-launch-strategy. For programmatic SEO pages that should live behind these backlinks, see iblai-marketing-programmatic-seo. For AI citation optimization, see iblai-marketing-ai-seo.

iii-hq Bundle

Discovery entry point for the engine — search the live function catalog, read the skills, system prompts, and agent profiles that installed workers ship off local disk, browse the public iii workers registry over HTTP, and install new worker bundles. Reach for it first to find out which workers exist and how to call them.

thinkyou0714 Skill

技術的な実装内容・判断・リスクを、非エンジニアのステークホルダーが理解できる言葉に変換する。「何が起きているか」「何が必要か」「何を決めてほしいか」を明確に伝える。非エンジニアへ報告・説明するときに使う。

viknesh20-20 Skill

Fetches a GitHub issue by number, analyzes the requirements, finds the relevant code, implements a fix, and optionally creates a PR. Use when working through your issue backlog.

arendon1 Skill

Break a PRD/ARD/SPEC into an implementation plan of vertical-slice tasks. Each task cites the invariants and interfaces it touches, names the test that proves it, and has a status cell. Sole mutator of PLAN.md in the active plan. Use when ready to break requirements into tasks, after grill/design/spec and before build, or when the user says "plan this", "break this down", "tasks", "what's the plan".

arendon1 Skill

Detailed technical specification. Turn a PRD/ARD into a precise SPEC.md: exact schemas, algorithms, data shapes, edge cases, acceptance criteria. Sole mutator of SPEC.md in the active plan. Has NEW / AMEND / DISTILL modes. Use when the objective needs more detail than the ARD before planning, after design, or when the user says "spec this", "detailed spec", "specify the behavior".

arendon1 Skill

Sharpen a fuzzy idea into requirements before spec. Calibrated interrogation via the grilling discipline: frontier rounds, recommended answers, facts are the agent's job, land each decision in PRD.md or CONTEXT.md. Creates the plan folder. The cheapest place to kill a bad idea is before a task exists. Use when the user has a vague idea, says "grill me", "stress-test this", "challenge my plan", "interview me", or before designing anything non-trivial.

arendon1 Skill

Architecture design pass. Turn a PRD into an ARD: components, interfaces, invariants, data flow, error handling. Propose 2-3 structural approaches with trade-offs. Recommend one. Behavior preserved. Use when the objective is non-trivial or high-blast-radius, after grill and before spec, or when the user says "design this", "architecture", "how should we structure this".

arendon1 Skill

Move issues through a triage state machine: from raw inbox to labeled, scoped, and ready for planning. Define triage roles/labels, apply them consistently, and surface what is ready to become a plan. Use when managing a backlog of issues or tickets before they become plans, or when the user says "triage", "go through issues", "organize the backlog", "what should I work on", "prioritize issues".

arendon1 Skill

Compressed English encoding for plan artifacts and spec-adjacent prose. Cuts tokens ~75% vs prose while staying readable. Applies to PRD.md, ARD.md, SPEC.md, PLAN.md, LESSONS.md, RESEARCH.md, CONTEXT.md. Use when writing to a plan artifact, spec-adjacent prose, or when the user says "caveman", "compress this", "be brief", "write to PLAN.md".

arendon1 Bundle

Constitution enforcer for the agent-skills repo: scaffolds new skills with compliant frontmatter (init), validates any skill against AGENTS.md (audit — frontmatter schema, layers, triggering contracts, agnosticism, size), and regenerates or verifies the harness-discovery manifest (manifest). Use when creating a new skill, auditing a skill for compliance, migrating a skill to the new frontmatter schema, or checking that the manifest is fresh.

arendon1 Bundle

Turn a decision the user cannot answer alone into a questionnaire for someone else to fill in. The inverse of grilling: interview the user about the SEND (who it goes to, what they need back), then write questions that target the gap between what the recipient knows and what the user needs. Use when the blocker is knowledge in another person's head — a stakeholder, client, expert, or colleague — and the user needs them to answer async or in a meeting.

joris887 Bundle

Use when the user has an idea or requirement to decompose into backlog stories.

joris887 Skill

Natural language skill discovery — describe what you want to do and get matched to the right skill.

joris887 Bundle

Deep guided elicitation for new projects. Archetype-aware, research-backed, multi-phase discovery with assumption tracking and Phase Transition Stories.

joris887 Bundle

Use when the user wants to implement a single story or deliver a backlog item.

joris887 Skill

Execute comprehensive backlog review. Analyzes story quality, Definition of Ready compliance, dependencies, zombie stories, and generates a backlog health report.

amadeus-dlc Bundle

Cross-review a GitHub Issue with two fresh, independent reviewers and evidence from the current repository, issue text, history, tests, and local norm files. Use when the user asks to cross-review, independently verify, or obtain two-reviewer confirmation of an already-filed GitHub Issue, including invocations where the target should be inferred from conversation, linked work, or an unambiguous pending-review signal. Produce two blind review verdicts and a fail-closed convergence result; prepare or, when explicitly authorized, post GitHub Issue comments. Do not use for backlog triage, ordinary single-reviewer issue analysis, PR code review, implementing a fix, closing an issue, or deciding which issue to start.

aneja5 Skill

Use when user wants to write a spec, create a PRD, or plan a new feature before implementation begins, when .forge/idea-brief.md exists and is ready to formalize, when requirements need to be captured before architecture or planning, or when a feature's scope and acceptance criteria need to be documented.

aneja5 Skill

Use when .forge/prd.md exists and the system needs a structural design before task breakdown, when modules will be implemented in parallel and need interface contracts to prevent integration failures, or when non-obvious technical decisions need to be recorded for future reference.

aneja5 Skill

Use when .forge/prd.md and .forge/architecture.md exist and the work needs to be decomposed before implementation, when sizing tasks for a sprint, when mapping dependencies between modules, or when a critical path needs to be identified before parallel work begins.

jsonlee12138 Skill

生成产品级 PRD。用户明确要独立做产品脑暴或写 PRD 时采用访谈模式；由 pre-development 调用时采用内部综合模式，根据已确认的 Intake 自动判断范围、用户故事与优先级，不重复询问老板。不创建 Linear Milestone / Issue。

data-wise Skill

This skill should be used when the user asks to "plan a project", "estimate effort", or needs help with task breakdown and project management strategy — NOT for producing a committed planning artifact (feature breakdown, sprint backlog, roadmap file); see `plan-orchestrator` for that. Provides expert guidance on feature planning, estimation, and delivery management.

data-wise Skill

This skill should be used when the user asks to "generate an ORCHESTRATE file", "turn a spec into a plan", "scaffold a feature breakdown", "scaffold a sprint backlog", "plan a sprint" (when a committed backlog/artifact is wanted, not just strategy advice), "generate roadmap artifacts", "create an implementation plan from SPEC", or needs to produce concrete planning artifacts (ORCHESTRATE-*.md, feature breakdowns with task estimates, sprint backlogs, milestone roadmaps). Differs from `project-planner` (high-level strategy/advice) by producing committed, actionable artifacts tied to specs and worktrees.

htlin222 Bundle

Curate a GitHub repository's wiki (the separate repo.wiki.git) into a coherent, tightly written set of pages: Home, Introduction (project + features), Roadmap, Gotchas/Lessons, Tech Debt, and an Architecture page taught through the book *Head First Software Architecture* — with mermaid diagrams, in the repo's own language and style, then commit and push. Use when the user wants to create, update, curate, or document a GitHub repo's wiki; write or refresh wiki pages; add an architecture / design page to a wiki; enable a wiki; or asks for "/wiki-git". Handles both first-time wikis and updates to existing ones, and can fan out across many repos.

lev-os Skill

[WHAT] Semantic search and discovery of skills for CDO workflow nodes [HOW] Uses lev-catalog CLI to browse, search, and load skills from axioms/hidden-gems [WHEN] Before building Deep/Epic workflows - discover skills to attach to graph nodes [WHY] Don't reinvent patterns - reuse existing decision frameworks and mental models Triggers: Called before Deep/Epic workflow construction