Design taste evaluation framework — DVF primary filter, Apple/Google/Jobs design principles as explicit scoring criteria, weighted decision matrix, and option ranking for the DIVERGE wave
日本語の概要は準備中です。原文の説明を表示しています。
863 件 ・ 関連度順
概要と使いどころ
Design taste evaluation framework — DVF primary filter, Apple/Google/Jobs design principles as explicit scoring criteria, weighted decision matrix, and option ranking for the DIVERGE wave
日本語の概要は準備中です。原文の説明を表示しています。
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
日本語の概要は準備中です。原文の説明を表示しています。
Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.
日本語の概要は準備中です。原文の説明を表示しています。
Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
YAML output format and approval criteria for platform design reviews. Load when generating review feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
日本語の概要は準備中です。原文の説明を表示しています。
Desktop application UI patterns for product owners. Load when designing native or cross-platform desktop applications, writing desktop-specific acceptance criteria, or evaluating panel layouts and keyboard workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions and scoring for root cause analysis quality assessment
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions and bug patterns for journey artifact reviews
日本語の概要は準備中です。原文の説明を表示しています。
Quality dimensions and review checklist for devop reviews
日本語の概要は準備中です。原文の説明を表示しています。
Definition of Ready checklist criteria, antipattern detection patterns, UAT quality rules, and domain language enforcement for product owner review
日本語の概要は準備中です。原文の説明を表示しています。
Translating JTBD analysis to BDD scenarios - job story to Given-When-Then patterns, forces-based test discovery, job-map-based test discovery, and property-shaped criteria
日本語の概要は準備中です。原文の説明を表示しています。
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
日本語の概要は準備中です。原文の説明を表示しています。
Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics
日本語の概要は準備中です。原文の説明を表示しています。
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is launching or running a DROPSHIPPING business end to end — the full 12-phase pipeline: product research with winning criteria, Minea and PiPiAds, supplier sourcing on AliExpress, CJ, Spocket, and Zendrop, Shopify store and app setup, the 10-ads-per-week creative pipeline, interest and lookalike targeting, 3-5x markup and BE-ROAS math, customer service, and scaling. Trigger on 'start dropshipping', 'winning product research', 'Shopify store setup', 'AliExpress supplier', 'scale my dropshipping store', 'my store gets traffic and no sales'. Not for — only the ad copy, see `05-ad-copy-global`; only the product page, see `12-landing-page-brief-global`; only the account audit, see `21-ads-audit-global`; only pricing, see `17-pricing-strategy-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria. Trigger on 'go-to-market', 'GTM plan', 'product launch plan', 'we are launching a new product', 'beachhead segment', 'how do we launch this course'. Also use when the user has a finished product and no route to the first customers. Not for — the day-by-day execution checklist, see `60-launch-playbook-global`; the ongoing period plan, see `00-marketing-plan-global`; one campaign inside the launch, see `02-campaign-brief-global`; positioning first, see `58-positioning-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see `59-go-to-market-global`; the campaign brief, see `02-campaign-brief-global`; the post-launch review, see `63-campaign-retrospective-global`; a live crisis, see `66-crisis-playbook-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agency or freelancer takes on a NEW client and needs everything up front — an 11-section intake covering business overview, audience, current marketing, goals, budget, timeline, brand assets, approval process, and success criteria, written for the client to fill in and return. Trigger on 'client intake', 'agency brief', 'onboard a new client', 'discovery call template', 'what should I ask a new client', 'kickoff questionnaire'. Also use when the user just signed someone and does not know where to begin. Not for — the internal context file the skills read, see `product-marketing-context-global`; the plan built from the answers, see `00-marketing-plan-global`; briefing an outside vendor, see `67-agency-vendor-brief-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when ONE static image needs a full brief for a designer or photographer — visual objective, concept and mood, composition, overlay copy, colors and fonts read from the brand guideline, per-channel dimensions, deliverables, and approval criteria. Trigger on 'image brief', 'banner brief', 'thumbnail brief', 'brief for the designer', 'how should this graphic look', 'the design came back wrong again'. Also use when the user has a post idea and needs to explain the visual. Not for — a multi-slide sequence, see `43-carousel-brief-global`; tool-level production steps in Canva or Figma, see `45-design-tool-brief-global`; generating the image with AI, see `30-design-master-global`; an urgent same-day swap, see `48-quick-visual-brief-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a completed phase needs unit or E2E tests, or the user asks to add tests for phase N. Classifies implementation files into TDD, E2E, or skip, gets plan approval, then generates RED-GREEN tests from SUMMARY.md and UAT criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify a decision one question at a time and compare options against explicit criteria. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.
日本語の概要は準備中です。原文の説明を表示しています。
Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.
日本語の概要は準備中です。原文の説明を表示しています。
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
日本語の概要は準備中です。原文の説明を表示しています。