'design-doc' 검색 결과

ISTQB/JSTQB のテストプロセス各工程の出口ゲートとして、工程成果物（test-plan.md / test-analysis.md / test-design.md / test-case.md / テスト実装 / test-execution-log.md / test-monitoring.md / test-summary-report.md）をレビューするスキル。決定論スクリプトの機械検査（トレーサビリティ ID 突合・テンプレ準拠）と test-reviewer サブエージェントの定性レビューを行い、利用者が通過/条件付き通過/差し戻しを判定して軽量記録 test-review-<工程>.md を残す。上流の仕様・基本設計（spec / design-doc 工程。docs/dev/<対象>/spec.md・basic-design.md）は機械検査と利用者判定のみの軽量ゲートとして扱う。各工程スキル（test-plan〜test-report / feature-spec / basic-design）が完了宣言の前に本スキルの実行を促す。ソースコード diff のレビュー（diff-review）とは別物で、対象はテストプロセスの成果物のみ。成果物の修正・代作はしない。/test-review <テスト対象名> [工程] で明示的に呼び出されたときのみ使用する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the full design-doc-writer and design-doc-reviewer loop until consensus. Produces a polished design document with a PR plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Turn a recurring workflow into a new agent skill through guided discussion. Define use cases, activation conditions, file structure, and instructions, then create and validate SKILL.md and supporting files, including workflows using external tools through MCP.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning recurring work into a reusable skill
• Standardizing report or document creation steps
• Designing workflows that use external services through MCP

Create ADRs, short records of architectural decisions, that explain what was chosen, why, and with what trade-offs. Choose among three formats and organize dates, status, numbering, and related links for future team members.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording why a database was chosen
• Preserving the rationale for a framework choice
• Documenting an authentication approach

Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting the design of a new feature
• Planning an external service integration
• Preparing a system migration proposal

Draft structured RFCs, proposals for gathering feedback before a major decision. Organize background, weighted criteria, alternatives, costs, and a recommendation so stakeholders can compare choices and understand the reasons for the proposed direction.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Proposing a database migration
• Reviewing changes to team workflows
• Comparing tools or vendors

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token set. Installed as a plugin, this skill carries what CLAUDE.md carries in the repo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design document writing conventions. Use when writing or reviewing technical design documents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Collaborative document creation via a structured three-stage workflow. Use for writing specs, PRDs, design docs, proposals, RFCs, and any long-form document where quality and clarity matter. Brainstorms 5-20 options per section, builds iteratively, and tests with reader sub-agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a data pipeline design document. Use when the user says "pipeline design doc", "document this pipeline", "pipeline architecture doc", "data flow document", "how does this pipeline work", "design doc for ETL", "pipeline spec", or needs to capture the architecture, data flow, and operational details of a data pipeline - even if they don't explicitly say "design doc".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

YC Office Hours — product validation for a new product, feature, or side-project concept. Startup mode tests demand; Builder mode develops an unvalidated product idea. Use when the user asks whether something is worth building or has an idea whose problem/value is not yet validated. Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use BEFORE a plan exists. For reviewing an existing plan, use /mk:plan-ceo-review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate professional documents — PDF, Word (.docx), Excel (.xlsx), and invoices — from natural language descriptions or structured data. Covers AI-powered and simple document creation, HTML-to-PDF conversion, PDF extraction/OCR, merging, watermarking, and data export. Use when you need to create campaign decks, reports, proposals, invoices, spreadsheets, or any shareable document — especially for Step 7 monthly presentations, campaign briefs, and analytics reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.