477건 · 관련도순
When scoring a roadmap, PR review, ADR, or ticket for completeness — risk, tests, migration, maintainability. Dispatched by /refine-ticket, /adr-create, /review-changes; never auto-gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says "plan a feature", "brainstorm", "explore this idea", or wants to go from idea to structured plan and roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when polling external AIs (OpenAI, Anthropic) outside the host session for a neutral second opinion on a roadmap, diff, prompt, or file set — or 'cross-check with another model'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a professional PDF report from a GEO audit using pandoc plus a Chrome/Chromium-compatible headless browser. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and a 90-day roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Aggregate findings and generate multi-format pentest reports with remediation roadmap and risk scoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an interactive, drag-and-drop user story map so the user can re-slice work across release phases. Use when the user wants a story map, a phased roadmap, release slicing, a backbone/activities journey map, or to decide "which stories go in which phase" and move them around.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts. Use when planning an IoT or Smart City platform on Azure (traffic, lighting, waste, sensors) from requirements to a delivery roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Use when analyzing competitors, building sales battlecards, tracking market moves, positioning against alternatives, or when user mentions competitive intelligence, competitive analysis, competitor research, battlecards, win/loss, or market positioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when structuring a multi-session learning roadmap with milestones, gates, and pacing calibrated to learner level and goal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auri: assistente de voz inteligente (Alexa + Claude claude-opus-4-20250805). Visao do produto, persona Vitoria Neural, stack AWS, modelo Free/Pro/Business/Enterprise, roadmap 4 fases, GTM, north star WAC e analise competitiva.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open-source one slice of a private system: take a component, sanitize it, run a leak-scan as a hard gate, publish to GitHub, then changelog, roadmap and tag on cadence, then the content wave. Publishing without passing the leak-scan is forbidden. Triggers: "/release-slice <piece>", "ship the next slice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a codebase as a read-only senior advisor, prioritize evidence-backed improvements, and write self-contained implementation plans. Use for codebase audits, improvement roadmaps, focused planning, plan review, plan reconciliation, or executing an existing improve plan through an isolated Codex worktree. The advisor never edits source code; execution uses codex-improve and returns to the main agent for review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate AI-powered BPO service proposals for Japanese companies in the US market. Use when creating outsourcing proposals with AI service menus, ROI estimation, implementation roadmaps, and bilingual (JA/EN) proposal documents for 在米日系企業向けAI実装.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when advising, planning, reviewing, reporting, operating, or improving CTO and technology leadership work across strategy, cybersecurity management, SME/COE, functional and technical requirements, framework selection, people, organization, delivery, risk, KPI, roadmap, budgeting, governance, audit, R&D, stakeholder communication, culture, politics, and sector-specific leadership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-of-life detection for runtimes (Node, Python, Java, Go, .NET) and key packages — surfaces past-EOL items, items reaching EOL within 90 days, and EOL base images for containers. Use when planning a runtime upgrade, auditing for unsupported versions, gating a deploy against EOL deps, or producing a remediation roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.