「bounded」の検索結果

Freeze one eligible Proto UI autonomous-maintenance candidate into a bounded mission packet and lease. Use before observation when a current request or governed queue supplies scope, oracle, baseline, capability, risk, budget, completion, and stop conditions. Do not observe, verify, repair, or invent a mission.

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

Diagnose one bounded Proto UI Actions or CI failure from an exact workflow run and revision, then route the exact repair, validation, or recheck transition. Use to locate the owning failure and distinguish infrastructure from change failures. This leaf remains read-only.

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

Execute one bounded read-only Proto UI autonomous-maintenance observation mission. Use for drift hunting, external-oracle comparison, repeatability control, or a no-finding maintenance run. Stop before verification or remediation.

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

Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.

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

Repair one independently verified Proto UI maintenance finding when governing authority or an explicit product decision fixes the expected result. Use for the bounded remediation and its evidence packet before independent review.

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

Plan Odylith delegation ownership, bounded fanout, and merge-safe orchestration.

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

Append a bounded execution note into Compass.

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

Apply Odylith security-hardening guidance to bounded product changes.

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

Choose local execution versus bounded delegation for Odylith slices and shape routed payloads.

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

Use when a bounded execution note needs to be appended into Compass.

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

Run the Codex Optimized Development, Evaluation, and Remediation (CODER) Loop with an orchestration-only coordinator, non-overlapping task-family owners, fresh independent reviewers, evidence-scoped remediation, and final coordinator acceptance. Discover and compose optional MSW, Timebox, MSL, and Codex Voice Optimizer companions as the Slopware Dev Stack without making them dependencies. Use in Codex when the user invokes the CODER Loop, asks to divide a complex change into bounded implementation families with independent reviewers, requests multi-agent implementation without overlapping ownership, requires review and repair until every blocking gap is independently rechecked, asks for the CODER tutorial or Slopware Dev Stack, or wants CODER to install or use its companions. Do not trigger for an ordinary single-agent change, a review-only request, or a non-Codex host.

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

Use when optimizing Convex database read bandwidth, documents-read cost, query indexes, full-table scans, function-level usage dashboard findings, or code that uses .filter(), unbounded .collect(), N+1 reads, or expensive reactive Convex queries.

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

Use when a Research Pilot project needs an experiment proposal from a weak or bounded project claim.

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

"Apply behavioral economics concepts including bounded rationality, prospect theory, mental accounting, and nudge theory to analyze decision-making biases. Use this skill when the user needs to understand why people make irrational economic decisions, design choice architectures, or apply nudges to influence behavior — even if they say 'why do customers make bad choices', 'how do we encourage people to save more', or 'design a better default option'.".

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

Choose responsibility for substantial work before deep execution: keep one responsibility's coupled parts in a single lane, and hand a bounded or independent lane to a worker when clean context, an unknown cause, independent review, or coordinator attention materially improves the outcome.

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

Investigate and fix bugs, failing tests, regressions, build failures, or unexpected behavior using boundary localization, evidence, and bounded hypotheses.

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

Break complex work into bounded Codex delegation tasks with clear ownership, expected outputs, and integration checkpoints.

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

Diagnose and fix Flutter layout, overflow, unbounded constraint, scroll, and responsive rendering issues in this repository while preserving the template's existing feature, theme, localization, and shared widget patterns. Use when UI overflows, text clips, widgets disappear, layouts fail on mobile/tablet/desktop, or a feature needs responsive behavior.

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

Fierce autonomous internal co-founder. Bounded web research for evidence-backed improvements. Structured idea formulation with self-critique filter that rejects ideas not serving the goal. Auto-implements high-confidence aligned improvements, proposes medium-confidence ideas for approval. Evaluates viral coefficient, AI search visibility (GEO), and solo SaaS economics. Considers higher pursuits: employing disabled people, spiritual tech investigation, 99% wealth donation ethos.

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

Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.

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

Run bounded, read-only semantic advisory sidecar passes for candidate mapping, issue triage, upstream diffs, evidence verification triage, and meta audit hints. Enforces monthly spend limits with explicit fallback to worker-luna.

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

Phase 1 of the feature-pipeline suite — stress-test a CLI command, feature, flag, or module as a developer seeing it for the first time, then file GitHub issues for every distinct finding. Use when someone says "explore X", "test X", "find issues with X", "what's wrong with X", or after /feature-pipeline init. Also triggers standalone as /fp-explore <feature> when you want just the exploration phase without the full pipeline. Reads the target feature from .fp-state.json (or the argument if provided). Completes in one bounded turn and prints the M1 stop hook so the user decides whether to continue to /fp-plan.

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

Phase 4 of the feature-pipeline suite. Use this after /fp-review has posted a sandbox review comment — it reads the outstanding checkbox items, applies fixes, then watches CI until green (or exits cleanly so you can retry). Trigger phrases: "address review items", "fix review feedback", "resolve review checklist", "watch CI", "poll CI", "check if CI is green", "iterate on PR", "fp-iterate", "Phase 4", "after review comment", "fix the review issues and watch CI". Always bounded — max 10 poll rounds, never loops forever. Exits with a clear status: green (hands off to /fp-drift), still-pending (re-invoke), or failed (diagnose before touching anything).

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

Batch wrapper for /gaia-ingest. Ingests a bounded set of already-verified evidence rows through CLI-only writes, uses --no-build on every row, appraises Trust Magnitude for every affected named skill, then runs exactly one build and validation pass. Use for an L4-approved intake after /ev-pipeline; benchmark-result rows also require a Phase 2B report and explicit human gate approval.

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