Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.
日本語の概要は準備中です。原文の説明を表示しています。
798 件 ・ 関連度順
概要と使いどころ
Expand a 1-4 sentence product brief into a full spec with a design language, acceptance surface, and an ordered feature list.
日本語の概要は準備中です。原文の説明を表示しています。
Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".
日本語の概要は準備中です。原文の説明を表示しています。
Generate high-potential viral title candidates for content across WeChat public account articles, X/Twitter posts, YouTube videos, Bilibili videos, and similar content platforms. Use when the user needs headline/title ideation, batch title generation, platform-specific title adaptation, title-library reuse, title selection, title scoring, or a reusable title workflow based on universal formulas plus separated platform methods such as 公众号, X, YouTube, and B站.
日本語の概要は準備中です。原文の説明を表示しています。
Core UX principles for product owners. Load when evaluating interface designs, writing acceptance criteria with UX requirements, or reviewing wireframes and mockups.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Terminal UI and CLI design patterns for product owners. Load when designing command-line tools, interactive terminal applications, or writing CLI-specific acceptance criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Web UI design patterns for product owners. Load when designing web application interfaces, writing web-specific acceptance criteria, or evaluating responsive designs.
日本語の概要は準備中です。原文の説明を表示しています。
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof
日本語の概要は準備中です。原文の説明を表示しています。
BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a completed change for acceptance, regressions and release risk; read-only, not a whole-codebase audit.
日本語の概要は準備中です。原文の説明を表示しています。
Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only.
日本語の概要は準備中です。原文の説明を表示しています。
Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.
日本語の概要は準備中です。原文の説明を表示しています。
Maps acceptance criteria to implementation evidence, tests, and scope creep. Use during review when a diff, PR, ticket, or story includes numbered ACs.
日本語の概要は準備中です。原文の説明を表示しています。
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.
日本語の概要は準備中です。原文の説明を表示しています。
Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.
日本語の概要は準備中です。原文の説明を表示しています。
멀티 에이전트 디자인 워크플로우 supervisor. writer, locale adaptation, humanize, UI slop audit, designer review, final QA, image materialization을 routing한다. 2-round revision cap을 유지하며 다국어 문서·UI 개선·출간 준비처럼 여러 역할이 필요한 요청에 사용한다.
日本語の概要は準備中です。原文の説明を表示しています。
멀티 에이전트 디자인 워크플로우 supervisor. writer, locale adaptation, humanize, UI slop audit, designer review, final QA, image materialization을 routing한다. 2-round revision cap을 유지하며 다국어 문서·UI 개선·출간 준비처럼 여러 역할이 필요한 요청에 사용한다.
日本語の概要は準備中です。原文の説明を表示しています。
한국어 canonical 문서·UX copy를 EN/JA/ZH-CN/ZH-TW로 번역이 아니라 locale adaptation한다. thesis·사실·명령어는 보존하되 문장 순서, 주어, register, 제품 용어와 호흡은 각 언어에서 다시 쓴다. '다국어 적용', '영문/일문/간체/대만어 버전', 'locale 문서 만들어줘' 요청에 사용한다.
日本語の概要は準備中です。原文の説明を表示しています。
User story generation - INVEST criteria, acceptance criteria (BDD/Given-When-Then), story mapping, epic decomposition, edge case stories, NFR stories
日本語の概要は準備中です。原文の説明を表示しています。