「improvement」の検索結果

Data-driven sprint retrospectives from git history — velocity, cycle/lead time, contributor insights, and churn hotspots. Use to run a retrospective, analyze team velocity or throughput, or generate a retro report from commit history.

日本語の概要は準備中です。原文の説明を表示しています。

Operations management across process optimization, efficiency, and continuous improvement. Use when designing workflows, building capacity plans, evaluating vendors, running Lean Six Sigma DMAIC projects, or optimizing cost-per-unit.

日本語の概要は準備中です。原文の説明を表示しています。

Patterns for AI agents that learn from their own execution, detect failure modes, and improve autonomously. Use when building agents that get better over time, managing auto- memory, or designing self-correcting feedback loops.

日本語の概要は準備中です。原文の説明を表示しています。

Panel health assessment, firm exit management, coverage gap analysis, and panel refresh brief for in-house legal ops teams. Produce an annual Panel Health Report synthesising scorecard data, billing compliance, and step-out patterns into per-firm recommendations — Retain, Watch, Improvement Plan, or Exit Review. Produce a firm exit pack: formal exit notice with active matter transition plan, plus an internal exit record. Identify practice area, geographic, or tier gaps and produce a structured Coverage Gap Report with remediation options. Produce a Panel Refresh Brief as a scoped input to the RFP process. Trigger on: 'review our panel', 'annual panel review', 'is our panel working', 'which firms should we exit', 'write the exit notice', 'coverage gap', 'we don't have anyone for restructuring', 'refresh the panel', 'panel rationalisation', 'too many firms', 'step-out problem', 'do we have the right firms'.

日本語の概要は準備中です。原文の説明を表示しています。

Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Capture, structure, and recycle lessons from active and closed legal matters. Three modes: in-flight capture (triggered by scope changes, risk events, status updates — highest value), mid-matter review (phase gates or quarterly), and matter close retrospective (full structured findings). Lessons are formatted for immediate reuse, not filed and forgotten. Use when a risk materialises, a scope change lands, a phase completes, or a matter closes and you want to convert what happened into something useful for the next matter. Trigger on: 'capture a lesson', 'what did we learn', 'matter close', 'retrospective', 'lessons learned', 'what went wrong', 'what worked', 'phase gate review', 'debrief', 'extract the learning', 'close the matter', 'what should we do differently', 'pattern from this matter', 'improve the next one'.

日本語の概要は準備中です。原文の説明を表示しています。

Analyse a learning task for cognitive load problems and recommend specific design improvements. Use when tasks overwhelm students, instructions feel complex, or materials need simplifying.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze the current session and propose improvements to skills. **Proactively invoke this skill** when you notice user corrections after skill usage, or at the end of skill-heavy sessions. Also use when user says "reflect", "improve skill", or "learn from this".

日本語の概要は準備中です。原文の説明を表示しています。

Triage improvement work and run or resume accepted measured loops in a local project. Architecture, documentation, UX, product study, open research, taste, and one-shot fixes stay direct unless the user explicitly requests repeated measurement with a complete experiment contract.

日本語の概要は準備中です。原文の説明を表示しています。

Implement adaptive learning with ReasoningBank for pattern recognition, strategy optimization, and continuous improvement. Use when building self-learning agents, optimizing workflows, or implementing meta-cognitive systems.

日本語の概要は準備中です。原文の説明を表示しています。

Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).

日本語の概要は準備中です。原文の説明を表示しています。

Achieve aggressive v3 performance targets: 2.49x-7.47x Flash Attention speedup, 150x-12,500x search improvements, 50-75% memory reduction. Comprehensive benchmarking and optimization suite.

日本語の概要は準備中です。原文の説明を表示しています。

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

日本語の概要は準備中です。原文の説明を表示しています。

Guides you through comprehensive iOS/Swift app planning and analysis. Use for new apps (concept to architecture) or existing apps (audit current state, plan improvements, evaluate tech stack). Covers product planning, technical decisions, UI/UX design, and distribution strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user asks to "analyze my content", "learn my writing style", "research competitors", "find content angles", "improve my blog", "write like me", "embody my brand voice", or mentions content strategy, voice analysis, competitive research, or iterative content improvement.

日本語の概要は準備中です。原文の説明を表示しています。

Amazon keyword rank tracking and performance analysis. Comprehensive ranking factor analysis, change diagnosis, improvement strategy development, and competitive position monitoring. Use when the user asks about keyword rankings, position tracking, ranking changes, or competitive analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Deep Amazon review analysis for competitive intelligence and product improvement. Extract sentiment patterns, recurring complaints, feature requests, and competitive insights from customer feedback. Turn reviews into actionable product development and marketing strategies. Use when the user asks about review analysis, customer feedback, product complaints, sentiment analysis, or what customers think about products.

日本語の概要は準備中です。原文の説明を表示しています。

Amazon search ranking optimization and A9 algorithm mastery. Comprehensive SEO strategy, indexing optimization, keyword ranking improvement, and search visibility enhancement. Use when the user asks about Amazon SEO, A9 algorithm, search ranking, or product discoverability.

日本語の概要は準備中です。原文の説明を表示しています。

Return rate reduction — root cause analysis, listing accuracy, packaging improvements, size guides

日本語の概要は準備中です。原文の説明を表示しています。

Line-by-line copy editing and improvement for marketing content. Polish existing copy for clarity, conciseness, impact, and conversion. Trigger phrases: "edit my copy", "improve this copy", "polish this text", "copy edit", "make this clearer", "tighten this up", "proofread", "review my copy", "make this more persuasive", "fix my writing".

日本語の概要は準備中です。原文の説明を表示しています。

Review affiliate campaign results and improve strategy. Triggers on: "review my results", "what went wrong", "how to improve conversions", "analyze my campaign", "affiliate retrospective", "why am I not converting", "improve my strategy", "what should I change", "campaign review", "optimize my approach", "learn from my results", "post-mortem on my campaign".

日本語の概要は準備中です。原文の説明を表示しています。

Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.

日本語の概要は準備中です。原文の説明を表示しています。