2.3천건 · 관련도순
Turn a broad product idea into an Epic PRD, a requirements document for a large initiative. Defines users, workflows, business requirements, success metrics, and scope to give engineering teams a basis for technical architecture planning.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn application requirements into an Azure Cosmos DB NoSQL data model. Gather read and write patterns, workload volumes, and relationships, then document container structures, partition keys for distributing data, indexes, and design trade-offs in two Markdown files.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Structure responses to buyer questionnaires and proposal requests by classifying requirements, matching claims to verifiable evidence, and exposing gaps. Develop buyer-focused reasons to choose your offer and estimate win probability to support bid decisions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn product or feature ideas into a concise product requirements document that helps teams decide what to build first. Connect target customers, customer value, success measures, and release scope, or review an existing document for gaps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review whether game design requirements are covered by documented architecture decisions. Identify missing coverage, conflicting decisions, and engine compatibility concerns, with an optional matrix linking requirements to development stories and tests.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a feature idea into a structured product requirements document. Clarify goals and scope through multiple-choice questions, then produce a Markdown file with small implementation tasks, checkable completion criteria, functional requirements, and success measures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore one problem through several distinct perspectives to uncover hidden requirements and edge cases. Turn the findings into testable success criteria, refinements, and failure conditions, stopping when additional perspectives no longer produce new requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a feature idea or rough notes into a product requirements document, or PRD. It organizes the problem, users, scope, prioritized requirements, success measures, and unresolved questions so a team can agree on what to build.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turns a feature request into a full implementation-plan requirements document matching docs/plan/_TEMPLATE.md. Use when the user asks for requirements, a spec, an implementation plan, or wants to flesh out a feature before building. Also use for /requirements or "write requirements for X".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when frontend work needs to communicate data, action, state, permission, validation, or business-rule needs to backend teams without dictating endpoint design, field names, database shape, or implementation details; Chinese triggers include front-end and back-end requirements handover, back-end requirements, API requirements clarification, data requirements description.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering", "functional spec" - even if they don't explicitly say "FRD".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Requirements for a Salesforce Enterprise Territory Management (ETM) territory design: alignment criteria, coverage model selection, assignment rule logic, hierarchy depth and breadth, and user-to-territory ratios. Trigger keywords: territory design, territory alignment, territory model requirements, sales coverage model, territory criteria, geographic territory, named account territory, overlay territory. NOT for ETM setup steps — use admin/enterprise-territory-management. NOT for loading territory assignment data — use data/territory-data-alignment. Trigger keywords: territory design questionnaire, territory requirements document, assignment rule matrix, territory type priority, realignment plan, territory access level decision, accountAccessLevel, opportunityAccessLevel, ObjectTerritory2Association, UserTerritory2Association, Planning state model, territory acceptance tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when scoring a list of business or solution requirements against the *actual* capabilities of a specific Salesforce org so each row can be classified Standard / Configuration / Low-Code / Custom / Unfit, given an effort tier (S/M/L/XL), a risk tag, and an AppExchange suggestion when applicable. Trigger keywords: fit gap salesforce requirements, score requirements against salesforce capabilities, salesforce capability matrix, classify requirement as standard config custom, fit-gap effort tier, AppExchange alternative for requirement. NOT for requirements elicitation (use admin/requirements-gathering-for-sf). NOT for architecture decisions on the GAP rows (use architect/solution-design-patterns and standards/decision-trees/). NOT for license or edition selection (use architect/license-optimization-strategy and architect/org-edition-and-feature-licensing). NOT for OmniStudio-specific fit-gap (use architect/omnistudio-vs-standard-decision).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Professional business analysis skill aligned with BABOK® Guide v3 standards. Use this skill when you need to elicit and document requirements, analyze business processes, conduct stakeholder analysis, develop business cases, perform gap analysis, or create business requirements documents (BRD). Ideal for requirements gathering, process mapping (BPMN), financial analysis (ROI, NPV), stakeholder engagement, and solution evaluation. Triggers: "gather requirements", "create business case", "analyze process", "stakeholder analysis", "gap analysis", "BRD", "functional requirements", or requests involving business analysis tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a business need and its constraints into a DRAFT RFP requirements pack: traced functional and non-functional requirements with priorities, mandatory gates, evaluation criteria with weights left to the business owner, and fact-seeking supplier questions. Solution-neutral; never names a supplier or product. Use when the user asks to "write the RFP requirements", "turn this business case into tender requirements", "draft the supplier questionnaire", "structure our RFQ from this brief" or "set up evaluation criteria before we go to market". Do not use for responses already received, use rfp-comparison-pack to compare them or supplier-evaluation-matrix to score them instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guidance on writing high-quality requirements: the requirement quality characteristics and the EARS (Easy Approach to Requirements Syntax) patterns — ubiquitous, event-driven, state-driven, optional-feature, unwanted-behaviour — for unambiguous, singular, verifiable requirements, plus defect/anti-pattern review and verification & traceability. Use when authoring or reviewing requirements. Original synthesis citing EARS (Mavin et al.) and NASA public-domain guidance; not a reproduction of ISO/IEC/IEEE 29148 or the EARS paper.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Knowledge base from NASA NPR 7150.2D — NASA Software Engineering Requirements. Use for NASA's Agency-wide software-engineering requirements: the software classification scheme (Classes A–F), the Requirements Mapping Matrix and class-driven applicability, tailoring and Technical Authority governance, the SWE-### 'shall' requirements across software management (Ch 3) and the engineering life cycle (Ch 4), the supporting disciplines (configuration management, risk, peer reviews/inspections, measurement, non-conformance — Ch 5), safety-critical and cybersecurity requirements, IV&V applicability, traceability, and the Appendix A definitions. Does not cover detailed software-assurance/safety procedures (see NASA-STD-8739.8), implementation how-to and document content (see NASA-HDBK-2203), the systems-engineering process framework (see NPR 7123.1), or program/project management (see NPR 7120.5).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
예약한 Itô GPU의 모델 서비스 지원 여부와 향후 확인 사항을 정리합니다. 현재는 서비스를 시작하지 않으며, 미지원 범위와 필요한 조건을 안내합니다.
모호한 기능 요청이나 영향이 큰 변경의 범위·전제·위험을 정리합니다. 기대 동작과 검증 방법을 명시한 인수 기준이나 인계 자료로 만듭니다.
Python과 JavaScript 의존성 파일의 버전 미지정, 중복, 고정 버전 충돌, 오래된 호환 패키지를 점검합니다. 문제의 영향을 쉽게 설명하고 검토하기 쉬운 수정안을 제시합니다.
Review implemented features against their requirements, add missing tests, and check performance constraints. Produce documentation, a table linking requirements to code and tests, and evidence showing whether the feature is ready for deployment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a feature PRD, a product requirements document, from a parent Epic. Turns a feature idea into user stories, explicit requirements, acceptance criteria, and scope boundaries that engineering teams can use to prepare a technical specification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.