「cis」の検索結果

Systematically document research findings, competitive analysis, market trends, and user insights in Notion. Build searchable research repository for data-driven decisions.

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

Capture meeting notes with clear structure: attendees, agenda, decisions, action items with owners and deadlines. Ensure accountability and alignment post-meeting.

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

Draft, rewrite, or condense emails with precise tone, length, and messaging. Perfect for cold outreach, replies, status updates, and escalations where clarity matters.

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

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

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

Agente de contexto para continuidade entre sessoes. Salva resumos, decisoes, tarefas pendentes e carrega briefing automatico na sessao seguinte.

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

Select and implement the right Azure compute platform for a workload. Decision tree guides choice based on workload characteristics, scaling needs, and operational maturity. Covers serverless, PaaS, containers, Kubernetes, and IaaS patterns.

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

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

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

Review and merge student exercise PRs during TP sessions. Arguments: <repo-url> [--class <class-id>] [--timeslot <HH:MM-HH:MM>] [--dry-run]

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

Persistent vector memory for Claude Code via LanceDB. Use when: remembering across sessions, storing lessons, recalling past decisions, maintaining context continuity. Tools: memory_store, memory_recall, memory_update, memory_forget, memory_merge.

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

Project documentation structure — standard proj-[name]/ layout with ADRs, stories, and operations guides. Use when: initializing docs for a new project, recording architecture decisions, or maintaining project knowledge bases.

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

Relentless delivery mode for complex, multi-step tasks. Use when: multi-file features, unclear root cause debugging, multi-angle research, architecture decisions with trade-offs. Activates parallel subagent dispatch and strict verification.

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

Council — 5 independent AI perspectives + mutual critique + synthesis (adapted from karpathy/llm-council for Claude Code). For high-stakes decisions where the answer does NOT follow unambiguously from the data — go/no-go before real consequences, critiquing a methodology, choosing between competing approaches, pressure-testing a conclusion you're attached to, designing risk controls. NOT for log/data analysis (the council has no data access) and not for factual lookups. Triggers — "convene the council", "run it past the council", "go/no-go", "pressure-test this".

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

Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.

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

Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".

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

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to implementation-loop with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to implementation-loop. Requires implementation-loop and an authenticated backend CLI to execute.

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

Delegate implementation to Codex, grok, or cursor-agent, then review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex, the grok 后端, or cursor-agent to write code, mentions handing off / delegating implementation to one of those backends, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.

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

Delegate implementation work to a dedicated implementer subagent, then review its diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants a separate model to write code, mentions handing off / delegating implementation, asks to work through a plan or spec unit-by-unit with a subagent doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer self-reports success, must not run the full test suite by default, must not touch git, and its report is a claim rather than evidence. Cursor port of implementation-loop. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the cursor-engineering-mode skill (it ships in this same plugin).

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

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to cursor-implementation-loop, this plugin's kernel skill, with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to cursor-implementation-loop. Requires this plugin's cursor-implementation-loop skill; they ship together.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Establish concise, cross-agent project instructions from repository evidence. Use when initializing or repairing AGENTS.md, CLAUDE.md, related discovery links, or project-specific agent guidance.

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

Review every Beads issue waiting on a person, one at a time, using the interactive questionnaire UI rather than plain-text prompts. Use when asked to go through blockers, clear the human queue, answer beads waiting on the user, triage `bd human list`, or unblock agent work that needs a decision.

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

Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.

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