「scope」の検索結果

Create a durable Architecture Review Record from a confirmed System Architecture Reviewer scope, evidence, pillar analysis, trade-offs, and dispositions

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

Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.

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

Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.

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

Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never curated prose.

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

Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.

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

Optimizes or restructures CLAUDE.md/AGENTS.md with progressive disclosure and zero information loss. Use when the user asks to optimize, audit, 精简/瘦身/重构, or split instruction files, asks for their best practices (最佳实践), sees Memory files taking a large share of /context, reports rules in instruction files being ignored, or a task starts moving instruction sections. Not for generic task drift unless instruction files are in scope; not for moving memory entries into docs (use claude-code-ops-router).

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

Routes any Feishu/Lark/Doubao operation through the version-matched lark-cli domain guide embedded in the installed CLI, then executes and verifies the task. Use for 飞书/Lark/Doubao docs, drive, sheets, Base, wiki, minutes, meetings, calendar, IM, mail, tasks, approval, apps, auth/scope, resource URLs or tokens, and lark-cli troubleshooting. This is the single Lark entry point; use ima-copilot instead for Tencent IMA.

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

Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies. Use for 提 PR / 上游 PR / 贡献代码, "open a PR", "fix this upstream", "rebase against main", "respond to the bot review". Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops).

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

Two scopes: (1) drives Kimi.app via computer-use for Work/Agent data-plugin queries (天眼查、同花顺 iFinD、SEC、IMF etc.) and Chat's built-in 深度研究 report; (2) kimi-cu macOS desktop-automation playbook — AX set_value / keyboard / click channel selection, foregrounding, AX-tree recovery, form & dialog recipes. Use for "用 Kimi 查" / "操作 Kimi 客户端" / "Kimi 插件" / "Kimi 深度研究" / driving any macOS desktop app (Electron/webview/native) via kimi-cu. Not for kimi.com browser automation (use kimi-webbridge) or direct iFinD API access.

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

Spot a bad client before you sign — the warning signs of the projects that turn into unpaid, scope-creeping nightmares, and how to screen, price, or decline them. Use when asked is this client a red flag, should I take this client, screening a difficult client, or how to avoid bad clients. Produces a read on the warning signs present (haggling, vagueness, disrespect, urgency, unrealistic expectations), what each predicts, screening questions to ask before committing, protective terms if you proceed anyway, and how to decline gracefully — so you avoid the clients who cost more than they pay.

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

Draft a defensible construction change order with entitlement basis, scope delta, itemised pricing, and schedule impact. Use when asked to write a change order, price extra work, draft a CO or COR/PCO, respond to a directive for changed work, or paper a field change. Produces a complete change order request with contract-clause entitlement, labour/material/equipment/OH&P breakdown, time impact statement, and reservation of rights.

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

Keep a running brag document of your accomplishments so reviews and promo cases write themselves. Use when asked to start or update a brag doc, log a win, track accomplishments, or prep evidence for a review/promotion. Produces a structured, dated accomplishment log — impact-first entries with metrics, scope, and the evidence link — grouped so it drops straight into a self-review or promo packet.

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

Sanity-check a greenhouse gas inventory before it goes into a report or gets audited. Use when asked to review a carbon footprint, check a GHG inventory, validate scope 1/2/3 numbers, explain a year-over-year emissions change, or prepare emissions data for assurance. Produces a boundary review, data-quality assessment, emission-factor sensitivity list, YoY bridge, and a fix-before-publishing list.

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

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance requirements, and the submittals and testing schedule.

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

Analyse a construction bid or tender package for scope gaps, risk-shifting exclusions, unit-rate red flags, and front-loading in the schedule of values. Use when asked to review a bid, level bids, check a tender for gaps, compare sub quotes, or vet a schedule of values before award. Produces a structured bid review with a gap register, exclusion risk table, pricing red flags, and an award recommendation with pre-award clarifications.

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

Structure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.

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

Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, short-term design choices that hurt maintainability, blindly following incorrect user assumptions, poor dependency choices, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into project artifacts or user-facing UI.

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

Scan application source, agent skills, and MCP components; run penetration tests against scoped web test deployments, validate findings, and configure scan gates. Use oma-qa for broad quality reviews and domain skills for remediation.

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

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

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

Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.

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

Review changes for correctness, security, accessibility, and performance. Use for scoped quality reviews or verification plans; bug fixes use oma-debug.

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

Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent opinion from Claude, or asks to delegate a well-scoped task to Claude. Supports selecting `--model` and thinking/effort level with defaults of `opus` and `high`.

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

Refactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.

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

Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

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