「progress」の検索結果

Builds a new Claude Code skill from scratch through a relentless, evidence-based interview that walks the skill's design tree decision-by-decision — entity fit, use cases, name, description, workflow steps, tools, and progressive-disclosure layout — then reviews the finished skill against the plugin-building guidance and applies every fix it finds. Use when creating, authoring, scaffolding, designing, or drafting a new skill or slash command. Does not build an agent or subagent — use agent-builder. Does not serve, vendor, or refresh the authoring guidance itself — use guidance.

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

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

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

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

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

Fix Flutter home feed / main screen stuck on loading spinner after login when using Riverpod StreamProvider that watches GoRouter location changes. Use when: (1) Screen shows BrandedLoadingIndicator or CircularProgressIndicator permanently after successful auth redirect, (2) Widget watches a route-type-gating provider that returns AsyncValue.loading() intermittently, (3) Logs show route location oscillating between stale and current paths during post-login transition (e.g., /welcome/* after /home/0), (4) Provider chain has double-gate: widget gates on pageContext AND data provider also gates on pageContext. Distinct from riverpod-infinite-rebuild-loop (rapid rebuilds) — this causes permanent loading state, not infinite rebuilds.

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

Use when implementing show completion status of an operation.

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

Analyze proof states in Isabelle or Coq and suggest applicable tactics to make progress. Use when users need help with: (1) Choosing the next tactic in an interactive proof, (2) Understanding what tactics apply to their current goal, (3) Getting unstuck in a proof, (4) Learning which tactics work for specific goal structures (conjunctions, implications, induction, etc.). Provides 3-5 ranked tactic suggestions with explanations for intermediate-level proofs in both Isabelle/Isar and Coq.

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

Create, update, or validate a game's Game Design Document. Use when the user wants help producing, editing, or validating a GDD — the primary design artifact covering pillars, mechanics, progression, levels, art, audio, and development epics.

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

ACTIVATE when building executive dashboards, tracking business metrics, creating executive scorecards, monitoring organizational KPIs, setting up health metrics, building dashboards for real-time monitoring, or establishing systems to track and measure business performance. Critical for any executive who needs to monitor company health, make data-driven decisions, or track progress toward strategic goals.

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

Find web sources with query-relevant page excerpts and optional full-page content, and discover workflows, data APIs, and indexes. Use for web research or finding structured records, listings, transcripts, and datasets. Supports semantic tool discovery, domain matching, and progressive catalogue browsing.

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

Designs responsive interfaces starting from mobile screens with progressive enhancement for larger devices. Use when building responsive websites, optimizing for mobile users, or implementing adaptive layouts.

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

Dynamic MCP server discovery and code-mode execution via central registry. Use for multiple MCP integrations, tool discovery, progressive disclosure, or encountering MCP context bloat, changing server sets, large tool sets.

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

Сводит статус итерации, оценивает прогресс milestones, фиксирует изменения приоритетов, отслеживает зависимости и выдаёт roadmap в формате Now/Next/Later с атрибуцией задержек по 5 причинам, health score и фреймворком обрезки scope при нехватке ресурсов. User-invoked only — do NOT auto-trigger. Triggers on /pm-roadmap, "обнови roadmap", "статус спринта", "анализ задержек", "update roadmap", "sprint status", "milestone progress", "delay analysis".

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

Delegate bounded investigation, review, or implementation tasks to Antigravity CLI from a supervising agent. Includes a background client for task progress, follow-up prompts, conversation recovery, cancellation, and visible failures.

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

Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and cancellation.

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

Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and Trello. Use when the user requests project management or provides relevant inputs for this workflow.

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

Think and work like an expert Immunotherapy Scientist. Use when a task calls for Immunotherapy Scientist judgment. Reasons from antigen recognition and checkpoint circuits through CAR-T/bispecific design, ASTCT CRS/ICANS grading, flow cytometry release CQAs, iRECIST response assessment, COMPASS/TIDE biomarker modeling, and JACIE/FACT IEC accreditation while treating antigen escape, pseudoprogression, tonic signaling, and step-up CRS as first-class failure modes.

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

Track real-time events, announcements, and breaking developments across Twitter, Reddit, news outlets, and web search. Monitors event progression, public reaction, key moments, and aftermath coverage for crisis response and opportunity detection.

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

Grounded in first principles, rigorously examine and refine a user's plan, task, decision, goal, strategy, proposal, or idea through structured, progressively deeper questioning, in order to bridge the gap between the User and the Agent. Use when the user explicitly requests grilling, challenge, pressure-testing, cross-examination, red-team review, pre-mortem analysis, or a decision audit. The goal is to uncover unclear objectives, hidden assumptions, contradictions, weak evidence, missing information, overlooked constraints, dependencies, risks, trade-offs, failure modes, and misalignment between intended outcomes and likely real-world results. Begin by establishing a shared understanding of the user's actual intent, goals, constraints, and success criteria. Ask focused, high-leverage questions rather than broad or repetitive ones. Adapt each question based on previous answers, probing deeper where uncertainty, unsupported assumptions, or strategic weaknesses remain. Regularly summarize the current understanding of the user's intent and position to confirm alignment, expose misunderstandings, and refine the problem or goal definition. Distinguish facts, assumptions, hypotheses, and unknowns. Challenge reasoning rigorously while remaining constructive, respectful, and solution-oriented. Continue until the reasoning is internally coherent, evidence-aware, constraint-conscious, risk-assessed, and translated into a clearer, more actionable goal, decision, or plan. Ultimately, achieving the super-alignment.

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

Run a complete design workflow -- from establishing context through four progressive design levels (Capabilities, Components, Interactions, Contracts) to an approved blueprint. Composes knowledge-priming, context-anchoring, learning-harvest, collaborative-judgment, design-first, architecture, and domain-driven-design into one process. Handles both new features (create context doc) and resuming existing work (load context doc). Level 5 (Implementation) is delegated to code-forge. Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

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

Guide structured design thinking through 5 progressive levels before any code is written. Levels: Capabilities, Components, Interactions, Contracts, Implementation. Use when building new features, refactoring significant code, designing modules, or when the user says 'design this', 'architect this', 'let's think before coding', 'walk me through the design', or 'whiteboard this'. For simple utilities enter at Level 4 (Contracts), for single-component tasks at Level 2 — see Complexity Calibration. Do not use for quick bug patches.

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

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.

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

cheat-on-skill 的陪跑进度 skill。用户问“今天该干嘛”“我现在做到哪了”“继续学”“打卡”“我卡住了”“下一步是什么”时触发。读取 .skill-state.json 的 active.progress 和 learning_plan，给当天任务、检查完成情况、记录进度、根据快慢调整计划。前置：已有 .skill-state.json 且 active.learning_plan 存在。

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

Use when a learner or instructor asks for a report, summary, reflection, progress note, performance recap, activity metrics, instructor-shareable record of a MATLAB AI tutoring session, aggregate report across multiple MATLAB tutoring session reports, or instructor dashboard artifact with metric drilldowns. Supports optional start and end datetime arguments for multi-session report and dashboard ranges.

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

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

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