Product & Planning

kirkruglov Bundle

Compile weekly status digests from multiple .md/.txt files. Extracts project updates, action items, and blockers into a structured report. Use when aggregating team status notes into a weekly summary. Triggers: 'compile weekly digest', 'weekly digest', 'составь дайджест', 'скомпилируй статусы'.

kirkruglov Bundle

Transform raw weekly notes into two reports in one pass: detailed Manager Report and 3-point Skip-Level Brief. Use when sending your weekly update. Triggers: 'write my weekly status report', 'weekly status report', 'напиши мой статус-отчёт', 'еженедельный статус-отчёт', 'преобразуй заметки в отчёт'.

kirkruglov Bundle

Build a comparative feature matrix and gap analysis from a folder of competitor notes (md/txt). Works fully offline — no web access needed. Use when preparing roadmap reviews, competitive analysis sessions, or feature prioritization. Triggers: 'build feature matrix', 'competitive feature matrix', 'compare competitors from notes', 'составь feature matrix', 'матрица фич конкурентов'.

kirkruglov Bundle

Compile local notes, tasks, and project files into a structured standup brief — no connectors required. Use when preparing for morning standup, daily sync, or team check-in. Triggers: 'morning standup brief', 'daily brief', 'prepare me for standup', 'подготовь меня к стендапу', 'дейли бриф', 'утренний бриф'.

search-atlas-group Bundle

Reflect on recent engineering work across repos, reconstruct what happened, extract reusable engineering lessons, generate research questions, and produce a morning HTML report. Use after project execution, coding sessions, long agent runs, failed loops, multi-repo work, or before starting the next day with a clearer backlog of questions and compounding insights.

search-atlas-group Skill

Create a standalone HTML report, decision memo, audit, comparison, or analysis for a stakeholder audience.

search-atlas-group Bundle

This skill orchestrates autonomous discovery of brand materials across enterprise platforms (Notion, Confluence, Google Drive, Box, SharePoint, Figma, Gong, Granola, Slack). It should be used when the user asks to "discover brand materials", "find brand documents", "search for brand guidelines", "audit brand content", "what brand materials do we have", "find our style guide", "where are our brand docs", "do we have a style guide", "discover brand voice", "brand content audit", or "find brand assets". When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.

search-atlas-group Skill

Produce a prioritized 90-day AEO/SEO content roadmap by consuming outputs from LLM Citation Audit (#4), Entity & Topical Authority Mapper (#5), and Competitor Content Gap Analysis (#12), deduplicating and merging related opportunities, identifying dependencies between work items, and sequencing the resulting deliverables across a calendar that respects team capacity. The output is a single integrated view that replaces three or four separate opportunity lists with no shared timeline. Use this skill whenever a user asks for a content calendar, content roadmap, quarterly content plan, 90-day plan, Q1/Q2/Q3/Q4 planning, content strategy sequencing, how to prioritize AEO work, or when multiple audit skills have been run and the user needs a unified execution plan. Chains with brand-kit.md (team, capacity, tone), llm-citation-audit.md (failure-mode-classified prompts), entity-topical-map.md (topic tree and Publish/Earn/Integrate actions), competitor-content-gap.md (content/quality/intent opportunities), and option

xonovex Bundle

Use when driving software from concrete agreed examples of behaviour: running three-amigos discovery and example mapping before coding, formulating Given-When-Then scenarios in feature files, and treating them as living documentation that tests the team their shared understanding. ATDD and BDD are one practice here. Triggers on BDD, ATDD, Gherkin, Given-When-Then, Cucumber, feature file, scenario / scenario outline, three amigos, example mapping, specification by example, living documentation, acceptance-test-driven, even when the user doesn't say 'BDD'.

xonovex Bundle

Use when writing, evaluating, splitting, or refining user stories: applying INVEST, the 3 Cs (Card / Conversation / Confirmation), the 'As a / I want / so that' template, writing acceptance criteria, slicing vertically into a walking skeleton, splitting with SPIDR or the splitting-pattern flowchart, and refining the backlog into ready items. Triggers on user story, INVEST, story splitting, SPIDR, vertical slice, walking skeleton, acceptance criteria, 'As a... I want... so that...', 3 Cs, backlog refinement / grooming, SMART tasks, even when the user doesn't say 'user story'.

liberty91ltd Skill

Use when the user asks "who are our customers?" / "how do we tailor for X stakeholder?" / "who should this report go to?", or wants to map / re-map stakeholder needs. Ensures intelligence reaches the right people in the right format.

lingtai-ai Skill

Developer reference for opting one tool family into bounded, read-only settings discovery without changing other families.

xoai Skill

Structures elicitation output into a formal specification defining WHAT to build and WHY. Use after quick-elicit or deep-elicit completes, or when the user provides requirements and says "write a spec", "define requirements", "create a PRD", or "specify this feature".

vs4vijay Skill

CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases

vs4vijay Skill

Review and promote backlog items to active milestone

alecs5am Skill

Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open `notes/issues/`, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before moving to the next. Sequential by default (one agent at a time) so changes never collide on shared files. Default scope is ALL open issues with a safety limit of 25; the user can widen the scope or raise the limit in their prompt. Pauses for the user only at genuine decision forks and before any paid generation or irreversible/outward-facing action. USE WHEN the user types `/dev-loop`, says "work through the issues", "run the dev loop", "grind the backlog", "implement all the open issues", "keep going through notes/issues until done", or after `/dev-issues` has filed a batch they now want executed. DO NOT FIRE for a single issue (just implement it), for content/video production, or when there are no open issues to exec

alecs5am Skill

Manage Ralphy's `notes/` capture inbox (`ideas/`, `issues/`, `decisions/`) — the only dev tracker for Ralphy itself; there is no separate roadmap board. Two jobs: (1) CAPTURE — turn a tagged thought into a correctly-shaped, correctly-placed note (an idea, an issue, or a decision); (2) COLLISION-CHECK — before filing anything new, search the inbox for an existing entity that already covers it, and update that instead of spawning a duplicate. For the `notes/issues/` backlog itself — decomposing a brain-dump into issues, executing them, moving them across `done/`/`deprecated/` — defer to the `dev-issues` skill (filing/shaping) and `dev-loop` (execution); this skill keeps `ideas/` + `decisions/` capture plus the cross-inbox collision check. USE WHEN the user types `/dev-tasks`, says "log this idea", "file a note", "capture this", "record this decision", "what's in the inbox", "is there already a note/idea for X", "promote this note", or drops a half-formed idea mid-dev-session for safekeeping. See body for ALSO F

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

kwakseongjae Bundle

사용자와 단계별로 검토하는 guided design harness. Discovery→Wireframe→Components→Microcopy→Validation을 omd-master가 실행하고 journey/system/validation의 필수 체크포인트에서 멈춘다. '/omd-harness', '체크포인트마다 검토', '나와 단계별로 디자인', 'guided design' 요청에 사용. 질문 없이 원샷으로 새 제품을 자율 구축하는 요청은 omd:autopilot, 단일 컴포넌트 수정은 omd:apply.

codealive-ai Bundle

Generate enriched lead lists using Exa deep search. Finds companies matching an ICP, enriches with signals/news/scores, and outputs CSV. Use when generating leads, building prospect lists, finding companies to sell to, doing outbound research, or ICP-based company discovery.

codealive-ai Bundle

Prepare intelligence briefings before sales meetings. Pulls company context, contact background, pipeline history, and generates talking points, objection prep, and demo customization. Run as cron (30min scan) or on-demand. For post-meeting processing, see discovery-debrief.

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

codealive-ai Bundle

Structured debrief AFTER a customer conversation — extract learnings, update hypotheses, track demand signals. Use when the founder says "talked to a customer". For preparing and planning interviews beforehand, use conducting-user-interviews.

codealive-ai Bundle

Build targeted prospect lists with verified contacts matching your ICP. Use when asked to find leads, build a prospect list, or identify target accounts. For signal-based prospect discovery, see signal-scanner. For enriching a single known lead, see lead-enrichment. For writing outreach, see cold-email.

codealive-ai Bundle

Help users qualify sales leads effectively. Use when someone is wasting time on bad leads, struggling with low conversion rates, needs to build a qualification framework, or wants to improve their discovery process.

codealive-ai Bundle

Help plan and run customer interviews — question design, interview structure, research planning. Use BEFORE interviews to prepare. For debriefing AFTER a conversation, use discovery-debrief instead.

farmountain Bundle

Skill: User Research Agent (Discovery & Insights)

nearai Skill

Guided YouTube competitor analysis: interviews the user first, then runs a fixed 5-phase workflow (competitor discovery, channel profiling, outlier detection, comment mining, content-gap report) using the youtube tool with a strict quota budget.

nearai Bundle

For a given deal, partnership, proposal, or initiative, identifies the right stakeholders on the other side and the right people internally to loop in, then produces a per-person messaging strategy covering what each person cares about, what tone works for them, and the specific action you want from each one. Turns "we should reach out" into a concrete list of who, what, and why.

qarium Skill

Orchestrate the product definition pipeline and generate the PRD

qarium Skill

Generate the final PRD from the validated product definition

wyattowalsh Bundle

Extract clean article text and metadata from URLs or HTML with trafilatura CLI. Use for single-page extraction, piped/local HTML, bounded discovery. NOT for research synthesis (research), PDFs (docling), raw fetch (fetch), video (yt-dlp).

dragoon0x Skill

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.

dragoon0x Skill

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.

dragoon0x Skill

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.

dragoon0x Skill

Identify and prioritize feature gaps between your product and competitors. Not just what's missing but which gaps matter, which don't, and which you should intentionally keep. Use when losing deals to missing features, planning roadmap with competitive context, or evaluating build-buy-partner decisions.