「proposal」の検索結果

Use when the user asks for a council, second opinions, or parallel investigation. Not for cross-examination of existing proposals: use cross-critique.

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

Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.

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

Post one already selected Proto UI work-item claim as a reversible GitHub metadata mutation. Use after pui-select produced a current proposal and the exact claim has authorization, live permission, current readiness, and an idempotent write boundary. Do not select work, decide readiness, release claims, or widen the authorized wording.

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

Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.

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

Use when a consumer repo needs proposal-first backlog, Registry, and Atlas drafts from new project intent before source exists.

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

Fires after fixing any non-trivial bug or regression. Asks: could the graph have caught this as a guarantee? Pairs with reflection-in-and-on-action — picks up after "earliest catchable signal" and asks the next question: was that signal expressible in graph? Triggers: (1) after any non-trivial bug fix is verified working, (2) after a regression report (something used to work, broke), (3) during step 6 (knowledge extraction) of the workflow, (4) when reflection-on-action surfaces a "would have been catchable" signal. Outcome is a triage decision (graph-reachable? rule expressible? rule sound?) and either a draft Linear issue + guarantee proposal, or a recorded "graph capability gap" note. Never auto-creates guarantees.

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

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.

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

PM (총괄) 오케스트레이터 v9.0. 제안서 팀을 이끌어 8-Step 파이프라인을 실행합니다. 입찰 제안서(RFP) + 마케팅 제안서 + 캠페인 브레인스토밍 지원. Step 0 출력 형식 분기 + 4개 병렬 리서치 + 7개 전문 QA. 트리거: 제안서 생성, 제안서 제작, /p, /start, /pf, generate, 스크립트 작성

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

캠페인 브레인스토밍 에이전트. 3인 전문가 에이전트(전략가/크리에이터/데이터분석가)가 개별 브레인스토밍 후 크로스리뷰 토론으로 최적안을 도출합니다. campaign_brief.md 생성 → 제안서 파이프라인(Step 3)으로 연계. 트리거: 브레인스토밍, 캠페인 기획, 아이디어, brainstorm, 캠페인 전략, 크리에이티브

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

시각 자료 관리 스킬. 제안서 스크립트에 이미지, 차트/그래프, 출처 인용을 추가하고 JSON으로 변환합니다. Gemini가 HTML 슬라이드에 시각 자료를 렌더링할 수 있도록 구조화된 데이터를 제공합니다. 트리거: 이미지, 차트, 그래프, 출처, 시각 자료, visual, 데이터 시각화, 인포그래픽

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

제안서 도식화 전략 에이전트. 콘텐츠 분석 → 최적 도식 유형 선택 → Mermaid/차트/인포그래픽 코드 생성. 트리거: 도식화, 다이어그램, 차트, 그래프, 인포그래픽, 플로우차트, 타임라인, 매트릭스, 시각화, 도식, visualize, diagram, mermaid

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

리서치 에이전트. RFP 분석 결과를 기반으로 시장 환경, 경쟁/벤치마킹, 타겟 인사이트, Best Practice, KPI 벤치마크 5대 영역을 웹 리서치하여 research_brief.md를 생성합니다. Planner가 Evidence에 실제 데이터를 사용할 수 있도록 지원합니다. 트리거: 리서치, 시장조사, 트렌드, 벤치마킹, research, 시장 분석, 경쟁 분석

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

분석팀 에이전트. 입찰 제안서(RFP) 또는 마케팅 제안서(마케팅 플랜) 분석. PDF 분석 또는 사용자 브리핑 수집. 프로젝트 메타데이터, Pain Point, 평가기준 배점, 프로젝트 유형을 추출합니다. 트리거: RFP 분석, 제안요청서 분석, PDF 분석, Pain Point, 평가기준, 마케팅 분석, 마케팅 플랜

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

디자인 레퍼런스 분석 에이전트. 디자인 레퍼런스/ 폴더의 PDF, JPG, PPTX 파일을 분석하여 컬러 팔레트, 레이아웃 패턴, 도식 스타일, 분위기 리듬을 추출합니다. 출력: design_analysis.md. 트리거: 디자인 분석, 레퍼런스 분석, design analysis, 디자인 레퍼런스

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

Structured design intake for non-trivial tasks. Asks clarifying questions and produces a design proposal.

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

Improve an existing skill or repository through isolated proposals, reproducible evaluation and evidence-based acceptance. Use for self-evolve or skill improvement.

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

Use when a project-local paper dossier should produce graph delta JSON proposals and run through the human-gated delta loop.

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

Use when a set of sources, dossiers, graph records, or experiment notes must be synthesized into project understanding, evidence pressure, uncertainty, and optional strict-review graph proposals.

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

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

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

Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

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

Write structured Requests for Proposal (RFP) or Requests for Quotation (RFQ) aligned with ISO 20400 sustainable procurement principles. Cover scope, technical requirements, evaluation methodology, and commercial terms. Use when sourcing vendors, services, or equipment.

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

Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.

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

Inspect a codebase, a stack the user describes, or a description of what they want to build; map what is there to agents-inc catalog skills — or intent to candidate built-in stacks the user picks from — and emit a SeedPayload plus a human-readable proposal report. Use when seeding a configuration for a project that has none.

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

Inspect or exercise the paused gaia curate orchestration scaffold for one source URL. The command currently persists an INITIALIZED run ledger and reports status; its 25 named workflow states and transition methods are a design skeleton, not an implemented automated curation or merge pipeline. Use only for scaffold development, status inspection, or dry-run contract work. For live curation, use gaia-full-pipeline or gaia-consult. Trigger phrases: "/gaia-quick-curate", "inspect gaia curate", "curate scaffold", "quick curate status". For batch/multi-page runs use gaia-curate-dynamic; for crawler branches use gaia-bot-curate; for pending intake proposals use gaia-draft-curate.

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