「findings」の検索結果

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

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

Capture and organize knowledge in Notion—research findings, best practices, reference materials. Build searchable knowledge base for your team and future self.

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

Perform comprehensive technical reviews of Ruby on Rails applications. Runs automated analysis tools (RubyCritic, Brakeman, bundler-audit, Gitleaks, Debride, linters, SimpleCov, Rails stats, Rails ERD), analyzes code for architecture, security, authorization (Pundit/CanCanCan), dead code, and design issues, and produces a structured markdown report with prioritized findings and a 0-10 score. Use when the user requests a tech review, code audit, project assessment, or quality analysis of a Rails application.

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

Drafts privilege-protective, board-ready executive summary memoranda of internal antitrust investigation findings for US federal law. Covers monopolization, vertical restraints, acquisitions, FTC Act Section 5, tech-platform conduct, risk assessment, and remediation. Use when drafting antitrust investigation summaries, board memos on competition risk, or internal compliance investigation reports.

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

Read-only full Jira ticket analysis incl. media + linked issues via jira-analyst agent; produces comment-ready findings. NOT complexity scoring (mk:jira-evaluator) or estimation (mk:jira-estimator).

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

Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).

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

Structured second-pass reasoning after code review or plan evaluation. Offers named reasoning methods (pre-mortem, inversion, red team, Socratic, etc.) to re-examine findings through a specific lens. Use after /mk:review verdict or any time deeper analysis is needed on an existing output. NOT for initial review (see mk:review); NOT for creating implementation plans (see mk:plan-creator).

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

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

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

DraftForge PR lifecycle workflow. Use when the user runs /pr, opens or pushes a pull request, or asks to monitor CI checks and Copilot review on a branch. Creates the PR (or reuses an existing one), polls GitHub Actions and Copilot up to ~15 min, then analyses CI failures and Copilot comments and reports findings grouped by file and skill.

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

Analyze release workflow findings and recommend follow-up actions — execute immediately or register as issues

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

Calculates the lowest effective glucocorticoid dose (dexamethasone or prednisone) to normalize blood pressure and serum potassium in glucocorticoid-remediable aldosteronism (GRA/FH-I) by titrating to biochemical and clinical targets. Indicated when initiating medical treatment for confirmed GRA, triggered by findings such as early-onset hypertension, family history of stroke before age 40, spontaneous hypokalemia, or suppressed plasma renin activity with elevated aldosterone.

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

Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.

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

Workflow Phase 8 (optional) — OWASP-aligned security review of pending code changes. Produces a prioritized findings report (Critical/High/Medium/Low) mapped to OWASP Top 10 and CWE IDs. Output at `docs/security/<slug>-<date>.md`. Read-only.

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

Act as a senior Amazon account growth operator that combines Amazon performance-drop analytics, Amazon growth-opportunity analytics, Amazon Ads data, retail readiness, BSR/rank signals, margin, inventory, and campaign/search-term evidence into a prioritized profitable growth action plan. Use when Codex needs to decide what to protect, fix, scale, reduce, pause, harvest, launch, or monitor for an Amazon brand, agency, marketplace, ASIN set, or account; when building daily, weekly, or monthly Amazon account operating plans; when reallocating ad budget; when deciding which ASINs are safe or risky to push; or when turning performance-drop and growth-opportunity findings into approval-gated actions with success/failure criteria.

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

Continuously bridges DESIGN.md into the active planning phase. When the user is working on a UI phase, reads the project's DESIGN.md, extracts the relevant token slice, and appends it to findings.md under "## Design Context" so the agent sees design constraints in its attention window. Never edits DESIGN.md, never edits task_plan.md. Idles when DESIGN.md is absent.

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

Review all uncommitted work and commits not yet pushed on the current branch, fix credible findings, commit remaining changes, and push. Use when the user invokes `$push` or asks to review, commit, and push all current branch work.

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

Use for SWOT analysis, or when the user wants to assess where a team, product or company stands: "strengths and weaknesses", "should we enter this market?", "review our position", "competitor comparison". Turns findings into actions. Skip for detailed planning or pure market sizing.

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

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible pi conversation into a new or existing NeatContext context. Use only when the user explicitly asks to preserve the current conversation as reusable context, or runs /neatcontext-save.

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

Save durable decisions, findings, plans, and implementation knowledge from the visible Kimi Code conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.

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

Research a technical topic thoroughly by exploring the codebase and summarizing findings. Use when asked to investigate how something works, research an area of the codebase, trace a data flow, or understand a component in depth.

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

Investigate two separate areas of the codebase simultaneously and combine findings into a comparison report. Use when you need research on two independent topics at once, want to compare two subsystems, or need to understand how two components relate to each other.

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

Use this skill to drive a research question (RQ) end-to-end: validate the RQ README, generate a fill batch-plan, start the Docker batch in the background, monitor progress, run aggregation, and propose findings updates. Trigger when the user says "RQ-N voranbringen", "run-rq", "fill RQ-N", "run RQ-N", "Forschungsfrage N starten", or names a specific RQ-N directory in research/.

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