'ideas' 검색 결과

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Discover keyword opportunities with MEASURED volume, keyword difficulty, CPC, and intent from OpenSEO, then write them into brand/keyword-plan.md. Use this skill whenever someone asks for keyword difficulty, KD, search volume, keyword ideas with metrics, striking-distance opportunities from Search Console, or SERP-validated keyword priorities. For qualitative research without an OpenSEO connection, use mktg's keyword-research instead (metrics will be unknown). Triggers: "keyword difficulty", "search volume", "keyword opportunities", "striking distance keywords", "measured keyword research".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structured marketing brainstorming when direction is unclear. Use when the agent doesn't know which skill to run, the user is vague about what they need, there are multiple valid marketing paths, or someone says 'I don't know where to start', 'what should we market', 'explore approaches', 'help me think through this', 'marketing ideas', 'what campaign should I run', 'where do I start with marketing', 'what's our marketing plan', or 'I have no idea how to promote this'. Explores 2-3 approaches and recommends the best path forward with a specific next-skill handoff. Even vague frustration like 'nobody knows about my product' or 'how do I get users' should trigger this when no specific channel or tactic is mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Malware reverse engineering and suspicious artifact analysis skill for defensive triage, static analysis, dynamic analysis planning, unpacking strategy, indicators of compromise, behavior summaries, YARA/Sigma ideas, and remediation guidance. Use for suspicious binaries, scripts, documents, logs, memory artifacts, sandbox reports, and malware family analysis in isolated environments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Digital Garden & Visual Architect. Use this agent to manage the Obsidian Knowledge Base, create visual logic maps via JSON Canvas, and maintain the automated development journal. It bridges the gap between abstract ideas and structured documentation. When the host supports them, use the Obsidian-focused skills and integrations for CLI, Bases, Markdown, Canvas, and defuddling workflows. When the host supports them, use the Obsidian-focused skills and integrations for CLI, Bases, Markdown, Canvas, and defuddling workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply the devil's advocate technique: structured critical thinking that stress-tests ideas, plans, and decisions. Use when you need honest critique before committing to something important.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structure presentations, pitch decks, and internal slide decks from rough ideas into clear outlines with slide-by-slide content guidance, key messages, and data callouts. Use when the work is organizing thoughts into a presentation structure. Do not use for visual design, slide layout, or graphic creation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create content draft from ideas using the Shipping Bible

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when absorbing ideas, capabilities, workflows, architecture, quality systems, ecosystem extensions, or engineering practices from any reference system into the current project through original, project-native redesign rather than copying.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess whether your leadership behaviors amplify or diminish your team using Liz Wiseman's Multipliers framework. Use when a leader asks "am I a good manager", "why isn't my team performing at their potential", "I feel like I'm doing all the thinking for my team", "my team seems dependent on me", "I want to be a better leader", "how do I empower my people", or "my team is smart but underperforming". Also trigger when someone describes always having the best ideas in the room, team members not taking initiative, reports waiting for direction before acting, or a leader who feels exhausted from carrying the team. Diminisher patterns are often invisible to the leader exhibiting them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transform ideas, outlines, or documents into structured slide content with clear titles, bullet points, and speaker notes. Adapts to presentation type (pitch decks, business reviews, technical workshops, educational talks). Use when user says "create slides", "build a deck", "pitch deck", "presentation structure", "talk structure", "keynote", "slide deck", "conference talk", or needs slide content for any format. Also trigger when user has content they want to present to an audience - even if they don't explicitly say "presentation" or "slides". To produce a branded .pptx file, see ppt-maker.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Strategic roadmap management for GitHub repositories. Syncs ROADMAP.md with GitHub Issues and labels, bootstraps roadmap files from scratch, runs brainstorming sessions with boundary checking, and provides quick status summaries. Use when managing project planning, syncing roadmap state, or exploring feature ideas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a full retrospective and dev cycle analysis. Chains /recall → /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings. Triggers: retrospective, retro, dev cycle analysis, what went wrong, lessons learned, postmortem, sprint retro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a content brief for ONE planned post: target and secondary keywords, search intent, template choice, competitor gaps from the live SERP, sourced statistics to include, section plan, internal-link targets, and distribution ideas. Use when the user says "content brief", "blog brief", "SEO brief", "article brief". Not a skeleton only (blog-outline), a multi-post plan (blog-strategy, blog-calendar, blog-cluster), or the article itself (blog-write).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.