「task」の検索結果

Branch and commit conventions that keep an agent's work reviewable — one branch per task, main stays clean, nothing force-pushed.

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

Bridge Codex to web-based AI model products by packaging local task context, scrub-checking it, sending it through an approved browser surface to ChatGPT Pro, Claude, Grok, Gemini, or another web model, waiting for the answer, and returning the model response to the user or Codex. Also guide DevSpace-like MCP Connector Mode when the user wants ChatGPT Pro or another MCP-capable web host to access approved local workspaces without relying on Codex browser automation. Use when the user asks for GPT Pro, ChatGPT Pro, Claude web, Grok, Gemini web, web model bridge, external model consult, ask another model, second opinion, use a web AI model, browserless agent access to GPT Pro, MCP connector, DevSpace-like workflow, or send local repo context to a browser-based model for planning, review, debugging, architecture discussion, or implementation guidance.

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

Reviews page hierarchy, grouping, density, actions and state design using consumer-owned product and design-system guidance. Use when asked for a visual design review, page critique or whether a new page communicates its task clearly.

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

Builds new UI prototypes and makes targeted changes to existing prototypes using consumer-owned context. Use when asked to build a prototype, mock up a UI, or add, change, refine or recreate part of an existing prototype. Do not use for unrelated tasks, routine commands, Git lifecycle actions, acknowledgements or infrastructure work.

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

Run independent, task-matched expert attempts, select a base, and synthesize the strongest result.

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

Finish an authorized security research task with a durable solved, abstained, or blocked outcome. Use when evidence is sufficient, a stop condition is reached, a tool budget is nearly exhausted, or the agent must commit its best supported answer.

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

Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers.

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

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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

Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.

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

Implement tasks from an OpenSpec change (Experimental)

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

Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.

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

Run an org-team workflow — a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec over the baseline MCP channel and implements them concurrently, each in its own git worktree. Each peer DECIDES its own in-lane implementation choices in its own main context (Article X); only un-decidable or cross-lane forks escalate peer→lead→human (yield_fork for task-bound forks, ask_lead for free-form queries). Opt-in and OFF by default (velocity.org_mode.enabled). Graduates the retired sprint-dispatch prototype into the constitutionally-sanctioned org-team model (Article X — Multi-session coordinated workflows). Requires git.

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

Workflow Phase 2 — Codebase Scouting and Constraint Discovery. Maps the relevant slice of the codebase for a given task. Produces a scout report at `docs/scout/<slug>.md` naming the files, modules, and patterns the proposed work touches or constrains. Report decisions execute in main context with full conversation visibility; gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips `/scenario` and `/implement` (no failing test to drive) and runs the work directly. `archive`, `memory-sync`, `/grant-commit`, and `/commit` remain mandatory. `verify`, `simplify`, `integrate`, and `document` are conditional — required when the diff hits one of the listed triggers, optional otherwise. `verify` is skipped only when the diff is pure-docs/prose AND `project.json → test.kind` is `behavior` (absent/invalid `test.kind` → `structural` → verify runs). Chore is a stripped-down pipeline, not a bypass; never silently skip a conditional phase whose triggers apply.

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

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

Use when executing implementation plans with independent tasks in the current session

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

Execute plans via delegate_task subagents (2-stage review).

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

Write implementation plans: bite-sized tasks, paths, code.

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

Use when you have a spec or requirements for a multi-step task, before touching code

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

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

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

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