Results for “requirements”

Eliciting, documenting and structuring requirements for a Salesforce implementation: stakeholder discovery interviews, As-Is and To-Be process mapping, and gap analysis against standard Salesforce capability. Trigger keywords: requirements gathering, user story, As-Is To-Be, gap analysis, stakeholder interview, process mapping, business requirements, fit gap. NOT for authoring the user stories themselves - use admin/user-story-writing-for-salesforce. NOT for scoring requirements against a specific org - use admin/fit-gap-analysis-against-org. NOT for technical design decisions - use architect/solution-design-patterns. Also covers the requirements catalogue itself (one row per requirement, MoSCoW priority, source stakeholder, downstream target) and Salesforce non-functional requirements: record volume, sharing layer, integration pattern, reporting joins, mobile/offline, and licence implication.

The English summary is being prepared. Showing the original description.

Use this skill to gather, document, and validate OmniScript flow design requirements before development begins — covering screen layout requirements, branching logic, data source requirements, and user journey mapping. Trigger keywords: OmniScript requirements, OmniScript BA, OmniScript screen design, OmniScript user journey, OmniScript branching requirements. NOT for building the OmniScript or moving logic into an Integration Procedure — use omnistudio/omniscript-design-patterns. NOT for FlexCard requirements — use admin/flexcard-requirements.

The English summary is being prepared. Showing the original description.

Use this skill to elicit, document, and validate CRM Analytics requirements — covering data source mapping (Salesforce object sync vs external connector vs Data Cloud), transformation needs, audience-specific lens or dashboard views, and drill-down path specifications — before any dataset or dashboard is built. Trigger keywords: CRM Analytics requirements, analytics data source mapping, CRM Analytics audience requirements, analytics visualization requirements. NOT for the formula and target behind each KPI — use admin/analytics-kpi-definition. NOT for building the dashboard once requirements are agreed — use admin/analytics-dashboard-design.

The English summary is being prepared. Showing the original description.

Use when gathering requirements for a customer portal, partner community, or self-service Experience Cloud site. Triggers: 'gathering requirements for customer portal', 'planning Experience Cloud site', 'what license for community portal', 'portal user journey mapping', 'self-service requirements'. NOT for building the site in Experience Builder — use admin/experience-cloud-site-setup. NOT for designing the deal-registration and MDF processes themselves — use admin/partner-community-requirements. More trigger keywords: portal persona licence matrix, which Experience Cloud licence do these requirements imply, external user needs a Contact and Account, sharing set vs sharing rule for a portal, self-registration vs SSO for a portal, portal requirements catalogue, handoff to Experience Cloud site setup.

The English summary is being prepared. Showing the original description.

Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Use this skill for all requirements-related work in a MATLAB MBSE project using the Requirements Toolbox (slreq). Covers creating and populating requirement sets, derivation links, test case requirements, verification coverage, reading and tracing links across requirement sets and models, checking link health, allocating requirements to components (Implement links), and building traceability reports. Trigger when the user asks about slreq API, slreqx files, slmx link files, outLinks/inLinks, traceability matrices, coverage analysis, broken links, or mapping requirements to architecture components. Use proactively for any requirements or traceability task.

The English summary is being prepared. Showing the original description.

Create a requirements traceability matrix linking requirements to design, test, and delivery. Use when the user says "traceability matrix", "RTM", "requirements traceability", "link requirements to tests", "trace requirements", "coverage matrix", "are all requirements tested", "requirements coverage", "forward traceability", "backward traceability" - even if they don't explicitly say "traceability matrix".

The English summary is being prepared. Showing the original description.

Facilitate structured requirements gathering. Use when the user says "gather requirements", "elicitation session", "stakeholder interview", "requirements workshop", "what do the users need", "discover requirements", "trawl for requirements", "understand the business need", "conduct interviews", or needs to systematically extract requirements from stakeholders - even if they don't explicitly say "elicitation".

The English summary is being prepared. Showing the original description.

Use this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.

The English summary is being prepared. Showing the original description.

Use when documenting, reviewing, or gathering requirements for Salesforce CPQ subscription lifecycle behavior: how amendments, renewals, upgrades, downgrades, and cancellations must work for a specific business. Trigger keywords: subscription requirements, amendment requirements, renewal requirements, proration requirements, co-termination, subscription ledger, upgrade downgrade policy. NOT for configuring CPQ amendments and renewals — use admin/contract-and-renewal-management. NOT for amendment architecture — use architect/subscription-management-architecture.

The English summary is being prepared. Showing the original description.

Use this skill when gathering, documenting, or validating requirements for a Salesforce marketing automation program — covering MCAE (Account Engagement / Pardot) lifecycle stages, MQL/SQL threshold definitions, scoring model specifications (sources, weights, decay, ceiling), handoff notification design, CRM field updates on status change, and sales SLA. Trigger keywords: MQL criteria, marketing-to-sales handoff, lead lifecycle, scoring requirements, automation program requirements, Marketing Cloud Automation Studio scope. NOT for building the scoring and grading rules in MCAE — use admin/mcae-lead-scoring-and-grading. NOT for a Sales-Cloud composite score built from formula fields — use admin/lead-scoring-requirements.

The English summary is being prepared. Showing the original description.

Transform client hearing sheets and meeting notes into structured requirements documents. Use when converting raw hearing data (Japanese/English) into formal requirements, generating traceability matrices, identifying gaps/ambiguities, and mapping requirements to WBS items. Triggers include "hearing to requirements", "meeting notes to specs", "requirements traceability", "gap analysis for requirements", or requests involving hearing sheet analysis.

The English summary is being prepared. Showing the original description.

Turn ideas, briefs, product requirements, or meeting notes into actionable tickets with Sofia, the Product Owner. Break large initiatives into smaller work items, refine requirements, review board status, validate ticket structure, and replan when requirements change.

• Turn ideas and notes into ticket requirements
• Break large initiatives into smaller work items
• Refine tickets and review readiness

Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.

• Finding requirements missing from an implementation
• Turning unmet requirements into GitHub issues
• Checking for duplicate issues before creating tasks

Turn support feedback or chat logs into a structured requirements document. Use numbered questions to clarify problems, goals, users, constraints, and open questions, then guide human review before handing approved requirements to development.

• Turning support feedback into requirements
• Clarifying missing details in chat logs
• Recording requirements review and resubmission

Turn a feature idea into a specification through structured questions about users, business goals, and technical constraints. Produce requirements, user stories, testable acceptance criteria, and an implementation checklist, including performance, security, and error handling.

• Defining requirements for a new feature
• Clarifying vague feature requests
• Writing testable acceptance criteria

Use this skill when building or maintaining a Requirements Traceability Matrix (RTM) on a Salesforce project: one row per requirement, columns for source, user-story id(s), test-case id(s), defect id(s), sprint, release, and status. Covers forward traceability (req → story → code → test) and backward traceability (test → req). Trigger keywords: RTM, requirements traceability matrix, audit trail for salesforce delivery, traceability for steerco, deferred requirement tracking, regulatory traceability. NOT for eliciting the requirements in the first place — use admin/requirements-gathering-for-sf. NOT for user-story authoring — use admin/user-story-writing-for-salesforce. NOT for UAT test design — use admin/uat-test-case-design. NOT for Apex test design — use apex/test-class-standards. NOT for backlog prioritization — use admin/moscow-prioritization-for-sf-backlog. More triggers: traceability.md, build-layer traceability, REQ-XXX and FG-XXX id mapping, artefact-to-requirement orphan report, coverage-gap report, check_rtm.py --manifest-dir, owning run-time agent column, design decision ref column, metadata API name in a traceability row.

The English summary is being prepared. Showing the original description.

Specify a FlexCard before a developer opens Card Designer: the card-state set and the condition that selects each state, the data source type behind each card (DataRaptor, Integration Procedure, Apex remote, SOQL), the action menu users get (navigate, launch OmniScript, Apex, DataRaptor), and every embedded child FlexCard or custom LWC. Produces the artifacts a BA hands to the builder. Trigger keywords: FlexCard requirements, FlexCard BA, FlexCard layout design, FlexCard data sources, FlexCard actions, FlexCard card states, OmniStudio FlexCard scoping. NOT for building the card in Card Designer, NOT for OmniScript step and branching requirements (use admin/omniscript-flow-design-requirements), NOT for standard Lightning record-page component requirements.

The English summary is being prepared. Showing the original description.

Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.

The English summary is being prepared. Showing the original description.

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

The English summary is being prepared. Showing the original description.

Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.

• Turning a product idea into a PRD
• Discovering requirements through user interviews
• Aligning stakeholders on product requirements

Turn identified threats and business needs into specific, testable security requirements. Define priorities, explain the rationale, and develop security user stories, acceptance criteria, and test cases linked to the risks they address.

• Turn threat models into security requirements
• Write security user stories and acceptance criteria
• Develop security test cases

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 a broad SaaS idea into an Epic PRD
• Define target users and their main workflows
• Clarify requirements, success metrics, and exclusions

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.

• Designing a data model for a new application
• Choosing how to group and partition related data
• Reviewing database costs for high-volume workloads