'specs' 검색 결과

API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.

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

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

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

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

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

Review code changes against linked GitHub issue specs to catch implementation drift — building something plausible but wrong. Checks each acceptance criterion against actual code.

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

Generate a professional product specification sheet with images, feature tables, technical specs, and contact information.

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

Extract product details from a supplier data sheet, then generate a branded e-commerce listing image with the product name, price, and key specs.

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

Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.

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

API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.

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

Use by any agent before writing specs, editing code, or changing workflow files when the change could add compatibility behavior, aliases, silent fallbacks, or default-value fallbacks.

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

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.

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

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

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

Responde dimensão, proporção, área segura, tipografia mínima e contagem de slides por plataforma. Use quando o usuário perguntar "qual o tamanho", "que dimensão", "quantos slides", "área segura", "cabe texto onde", "especificação do formato", ou quando outra skill precisar validar medidas. Fonte única desses números.

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

Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.

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

UI runtime 驗證 SKILL — 刷新 Cocos asset-db、執行 validate-ui-specs.js、headless-snapshot-test.js、capture-ui-screens.js，並依環境選用 cocos-screenshot 或 cocos-preview-qa 檢查實際畫面殘差，回寫 generated-review / runtime-verdict。USE FOR: 修改 layout / skin / screen / content / Panel / UI 資產後的驗證收尾。DO NOT USE FOR: 純資產生成、無 target 的整專案大範圍探索。

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

UI 資產品質驗證 SKILL — 執行 validate-visual-assets.js、validate-ui-specs.js 與必要的 snapshot regression，對 skin family 資產、screen package、proof draft / family-map 進行全面驗證，並回寫 generated-review。USE FOR: 任何 UI 資產生成後、在 ui-preview-judge 前必須先通過的 QA 關卡。DO NOT USE FOR: debug runtime 崩潰（用 cocos-log-reader）、Layout 佈局調整（用 ui-vibe-pipeline）。

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

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

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

Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.

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

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

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

Turn a rough idea into a fully approved design before any code is written. Load when the user wants to brainstorm, explore ideas, design a feature, think through approaches, plan a new capability, or figure out what to build. Also triggers on "let's think through", "help me design", "explore options", "what's the best approach for", "I have an idea for", "before we build", or any request to design something before implementation. Enforces a hard gate: no code, no implementation until user approves a design. For executable feature specs (FRs, NFRs, ACs as Given/When/Then), route to `feature-spec` instead — brainstorming owns approach and architecture, not machine-readable requirements.

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

Set a deliberate visual direction before any UI is built — the single biggest lever against generic AI output. Derives a posture from product-soul/PRD/specs, scores a curated archetype palette, then generates 2-3 GENUINELY DISTINCT directions and compares them side-by-side before committing to one. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, explore visual options, says "what should this look like", "make it feel like [Linear/Apple/ Duolingo]", "give me design directions", "explore some looks", or when frontend-design routes here. Replaces design-archetype. Sub-skill of frontend-design.

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

Orchestrator + builder for distinctive, production-grade frontends that don't look AI-generated. Derives stack and design context from product-soul/PRD/specs, then runs the anti-slop chain — explore distinct directions, lock a DESIGN.md system, build from golden examples with mandatory polish + every interactive/empty/loading/error state, then review. Load when the user asks to build a UI, design a frontend, build a landing page or dashboard or web app, beautify or redesign a page, make a UI look premium/playful/editorial, says "build me a frontend", "make this not look AI-generated", "design this interface", "give this real polish", or "frontend design". Routes to design-direction, design-system, design-review.

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

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

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

API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.

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