「rd」の検索結果

Finalize an implemented rolling-wave slice for user review. Use when the user wants Codex to review the current branch state against a ready-for-review or in-review slice contract, confirm and fix required findings, repeat review and verification until no required findings remain, ask before accepting findings that materially change project shape or contradict project assumptions, record review state, and leave the clean slice in review for complete-slice.

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

Implement a ready rolling-wave slice without locking it down with broad tests yet. Use when the user explicitly wants to code the current docs/rolling-wave/{project}/slices/NNN-slug.md slice, mark it in progress while working, implement small or cohesive work in the main context by default, use one to three gpt-5.6-terra workers only for genuine parallel chunks or large discovery/mechanical work where delegation pays for its handoff cost, pause or hand off chunks marked human-fit when appropriate, record implementation notes and final-test backlog, preserve the original slice contract, and mark completed implementation ready for review.

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

Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.

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

Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.

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

Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.

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

Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.

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

Report the current development environment: Node, Python, OS, git state. Use when debugging environment issues, onboarding, or checking system compatibility.

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

Review database migration files for naming conventions and dangerous operations. Auto-activates for migration files.

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

Perform a deep architectural analysis or security review requiring extended reasoning. Use for complex architecture decisions, security audits, or when standard analysis is not finding the root cause.

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

Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.

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

Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.

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

Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.

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

Scan the codebase for common security issues: hardcoded secrets, SQL injection vectors, XSS, unvalidated inputs, and insecure defaults. Use before deploying, as part of code quality review, or when asked to check for security issues.

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

[Utilities] Use when asking what the .claude framework does for THIS project: configuration, skills/agents/workflows, reference docs, key tech/architecture/structure facts. Command keyword search: framework-config --mode=help.

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

[Project Management] Use for explicit project-owned tracker guidance (--mode=guide), or portable-engine work records, placement, linked concerns, lifecycle, evidence, acceptance and local status. Existing engine modes and bare inspect remain supported.

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

[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.

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

[Document Processing] Use when converting between Word DOCX and Markdown (GFM, math rendering). --to={markdown|docx}.

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

Plan, order and deliver a batch of backlog items (e.g. every High item) in a Conventional Docs repo, one decision, branch, worktree, draft PR, review and merge per item. Use when asked to work through the backlog, implement all items of a priority, or sequence several backlog items end to end.

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

Generic ad-hoc topic search across CopilotKit + AG-UI Discord/GitHub. "Find all reports about <topic> in the last <N> days." Returns a structured chronological list with reporter handles + 1-line summaries + optional enterprise enrichment. Triggers on "find all reports about", "search across both communities", "look for X in last N days".

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

P0 classification rules for community reports. Six categories that auto-headline regardless of reporter count. Reference doc — invoked by weekly-report when classifying.

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

Subagent that scans CopilotKit + AG-UI releases shipped in (and just after) the report window, diffs the git tags to extract what each release actually fixed, and returns a fix-map the weekly-report writer cross-checks against open issues. Catches issues that are quietly already-fixed in a shipped release, and is the authoritative source for the "current release vX.Y.Z" version claims. Invoked by weekly-report (spawned in parallel with the Discord/GitHub pulls); runs as a general-purpose subagent so the orchestrator's context stays small.

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

Fri→Fri community signals routine across CopilotKit + AG-UI. Orchestrator that supervises subagents — Discord pull, GitHub pull, deep-read, reporter enrichment, Reddit Pulse — and synthesizes a Notion report under the Community Signals parent page. Triggers on "go", "weekly report", "community signals", "run routine".

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

Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic", "design this", "theme this", "use my brand", "iterate on this design", "review this artifact", "make this bolder", "make this quieter", "simplify this design", "animate this", "improve the look of", "give this a refresh"). Captures brand from the user's codebase, asking, or live site, then applies it to every artifact.

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

Expert Clay platform consultant for B2B data enrichment and workflow automation. Use when the user asks about Clay tables, waterfall enrichment, Clay credits, Clay AI columns, Claygent, enrichment workflows, Clay integrations, Clay exports, Clay table design, lead scoring in Clay, or building data pipelines in Clay. Also triggers on "Clay table", "enrichment waterfall", "Clay credits", "Claygent", "Clay AI column", "Clay export", "Clay providers", "enrich in Clay", "Clay column", "Clay formulas", "find emails", "email waterfall", "phone waterfall", "lead scoring", "Clay debugging", "Clay troubleshoot". Do NOT use for general CRM questions without Clay context, cold email copy (use cold-email-copy-playbook), or signal routing (use buying-window-signal-workflow).

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