「fea」の検索結果

Apply behavioral science and mental models to revenue (cuan) decisions, prioritized using a psychological leverage and feasibility scoring system.

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

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

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

Use when a feature launch needs experiment design, test sequencing, rollout guardrails, and measurement logic before exposure to users.

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

Use when a plan, feature, or launch needs an explicit adversarial pass to find weak assumptions, abuse cases, or strategic blind spots before execution.

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

Reviews construction plans for architecture consistency and implementation feasibility. Use when reviewing implementation plans before approval.

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

Discover what Cowork can do for YOUR specific role and tasks, for mapping your daily work to Cowork capabilities. Use when exploring what Cowork offers, for planning your Cowork adoption, during onboarding and role discovery, when figuring out where to start, or when the user says "what can cowork do", "what is cowork", "show me cowork features", "how can cowork help me", "what should I use cowork for", or "cowork capabilities".

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

Walks you through pairing your phone with Cowork and sending your first remote task — so you can control your desktop from anywhere. For deploying tasks while commuting or in meetings, when setting up mobile-to-desktop control for the first time, or during a Cowork Max feature exploration session. Use when the user says "dispatch", "control cowork from phone", "remote task", "phone to desktop", "try dispatch", "can I use cowork from my phone", or "send cowork a task while I am away".

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

Run Phase 2a (test generation, Red phase) for the active VCSDD feature. Invokes vcsdd-builder to generate failing tests for all spec requirements. Records red phase evidence.

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

Run Phase 2b (implementation, Green phase) and Phase 2c (refactor) for the active VCSDD feature. Invokes vcsdd-builder to implement minimal code to pass failing tests, then refactor.

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

Display the current VCSDD pipeline status for the active (or specified) feature. Shows phase, mode, sprint count, open findings, pending proofs, and the traceability summary.

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

Run Phase 3 (adversarial review) for the active VCSDD feature. Spawns a fresh vcsdd-adversary agent with zero Builder context to review implementation against spec. Produces binary PASS/FAIL verdict per dimension.

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

Create a git commit for the current VCSDD phase. Auto-generates a conventional commit message from state.json including phase, sprint, gate verdict, and affected bead IDs. Tags with vcsdd/<feature>/phase-<id>.

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

Run Phase 1c (spec review gate) for the active VCSDD feature. Spawns a fresh vcsdd-adversary instance to review the behavioral spec and verification architecture. Records PASS/FAIL gate verdict.

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

Run Phase 5 (formal hardening) for the active VCSDD feature. Invokes vcsdd-verifier to execute proof obligations, security hardening, and a purity-boundary audit before convergence.

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

Run Phase 6 (convergence check) for the active VCSDD feature. Validates four-dimensional convergence: finding diminishment, finding specificity, criteria coverage, and duplicate detection.

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

Run Phase 1a (behavioral specification) and Phase 1b (verification architecture) for the active VCSDD feature. Invokes vcsdd-builder to write EARS-format requirements and purity boundary analysis.

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

REQUIRED skill for any security-related request. Use this skill whenever the user wants to find anything dangerous, sensitive, or risky in their code, files, or repository. This includes but is not limited to: scanning for secrets/keys/tokens/credentials, checking dependencies for vulnerabilities, auditing destructive commands for missing safeguards, reviewing files for PII or internal data before open-sourcing, checking .env files or git history for leaked credentials, or any request where the concern is "is this safe/secure/exposed?" This skill provides a structured audit methodology and checklist you MUST follow — do not attempt security reviews without it. Skip this skill ONLY for pure feature work, refactoring, bug fixes, or non-security code review.

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

Create diagrams and visualizations using Mermaid.js v11 syntax. Use when generating flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, user journeys, timelines, architecture diagrams, or any of 24+ diagram types. Supports JavaScript API integration, CLI rendering to SVG/PNG/PDF, theming, configuration, and accessibility features. Essential for documentation, technical diagrams, project planning, system architecture, and visual communication.

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

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

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

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

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

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

Use when implementing any feature or bugfix, before writing implementation code

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

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

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

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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