'systematic' 검색 결과

Write a literature review. Use when the user says "literature review", "lit review", "review the literature", "summarize prior research", "what does the research say about", "synthesize research on", "background section", "related work section", "what has been studied on this topic", or needs to systematically identify, synthesize, and critically evaluate existing research on a topic - even if they don't explicitly say "literature review".

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

Write a threat model document. Use when the user says "threat model", "threat modeling", "STRIDE analysis", "attack surface analysis", "security design review", "what are the threats to this system", "adversarial analysis", "identify threats", "security threat assessment", or needs to systematically identify and document threats to a system or feature - even if they don't explicitly say "threat model".

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

Debug a bug or unexpected behavior systematically. Use when the user says "there's a bug", "this isn't working", "I'm getting an error", "help me debug", "why is this failing", "unexpected behavior", "test is failing", "something is broken", or describes behavior that doesn't match expectations - even if they don't say "debug".

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

Design and document a marketing growth experiment. Use when the user says "run a growth experiment", "test this channel", "growth test", "I want to experiment with [channel]", "traction experiment", "acquisition experiment", "let's test if [channel] works for us", "bullseye framework", "which channels should we try", "run a traction test", or wants to systematically test a marketing or acquisition channel before committing budget. For page-level conversion hypotheses, see page-cro. For copy variants to test, see ab-copy-writer. For recording the result, see retro.

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

Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.

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

Facilitate structured requirements gathering. Use when the user says "gather requirements", "elicitation session", "stakeholder interview", "requirements workshop", "what do the users need", "discover requirements", "trawl for requirements", "understand the business need", "conduct interviews", or needs to systematically extract requirements from stakeholders - even if they don't explicitly say "elicitation".

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

Iterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.

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

Systematic technical debt analysis across architecture, testing, documentation, and infrastructure. Investigates the codebase, scores findings by impact and effort, and generates a prioritized TECH_DEBT.md remediation plan. Delegates to specialized skills for code quality (scout) and linting (lint-fix). Use when assessing overall project health, planning cleanup sprints, or onboarding to an unfamiliar codebase.

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

Safe systematic dependency upgrade with vulnerability scanning and rollback capability. Detects project ecosystem, audits outdated and vulnerable packages, presents a prioritized upgrade plan, and executes upgrades one at a time with test verification after each. Use when updating dependencies, fixing vulnerability alerts, or performing periodic dependency maintenance.

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

Use when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other LLM-introduced architectural decay — over a specified duration

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

Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues, and edge cases. Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks) for every issue.

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

Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.

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

Mutation testing workflow. Systematically mutates source code to verify tests actually catch bugs. Multi-session with progress tracking.

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

Analysis of Competing Hypotheses. Operationalizes Richards Heuer's CIA-tradition technique for systematically narrowing among multiple hypotheses against evidence. Builds an explicit hypothesis-vs-evidence matrix and focuses on disconfirmation rather than confirmation — the central insight: hypotheses cannot be proven, only disconfirmed; the surviving hypothesis is the one with the least disconfirming evidence. Spawns parallel hypothesizers (in isolation, across hypothesis-generation angles) and parallel evidence-gatherers (across evidence classes), then synthesizes into a matrix, diagnosticity analysis, sensitivity analysis, and falsification milestones. Produces feedback only — no code, no tickets, no artifacts.

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

Iterative development workflow that coordinates implementation, refactoring, QA, and documentation agents to complete features systematically. Use when the user wants a full development workflow with quality checks.

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

Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.

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

Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished or premium, review design consistency, fix visual hierarchy, or refine spacing/typography/color. Also trigger when the user says "design review", "make it look better", "UI polish", "visual refinement", "design pass", "audit the design", or references making an app feel more professional. This skill is purely visual — it does not touch functionality, logic, or features. It elevates what exists.

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Systematic QA testing for web applications, desktop apps, and workflows. Three tiers: QUICK (critical/high severity only — 5 min), STANDARD (+ medium severity — 15 min), EXHAUSTIVE (+ cosmetic — 30+ min). Tests user flows, finds bugs, reports with severity classification, and optionally auto-fixes with atomic commits. Produces before/after health scores and ship-readiness summary. Use when user says "test this", "QA", "find bugs", "does this work?", or "is it ready to ship?". Voice triggers: "quality check", "run QA", "test the app". For report-only (no fixes), use with --report-only flag.

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

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

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

Debug React hooks infinite loops, stale closures, and missing dependencies. Systematic approach.

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

Systematically document research findings, competitive analysis, market trends, and user insights in Notion. Build searchable research repository for data-driven decisions.

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