sfdipot-product-factors

Generate prioritized test cases from software requirements using the SFDIPOT framework.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/CENKSSS/valocase-backend --skill sfdipot-product-factors-cenksss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfdipot-product-factors
Source: https://github.com/CENKSSS/valocase-backend/tree/main/.claude/skills/sfdipot-product-factors
Command: npx skills add https://github.com/CENKSSS/valocase-backend --skill sfdipot-product-factors-cenksss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires brutal-honesty-review, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in the generation of a comprehensive test strategy based on James Bach's HTSM Product Factors (SFDIPOT) for thorough testing of software requirements.

Core Features & Use Cases

  • Test Strategy Generation: Provides a structured approach to test requirements, epics, or user stories using SFDIPOT categories.
  • Prioritization & Coverage: Assigns priorities to test ideas and clarifies coverage gaps.
  • Use Case: Utilize this Skill during epic planning, sprint reviews, or test strategy definition to ensure robust test coverage.

Quick Start

Generate a SFDIPOT test strategy for the new 'e-commerce' feature epic, prioritizing critical paths.

Frequently Asked Questions about sfdipot-product-factors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a test strategy from software requirements using the SFDIPOT framework?

To generate a SFDIPOT test strategy, analyze your software requirements or user stories by evaluating Structure, Function, Data, Interfaces, Platform, Operations, and Time factors to produce prioritized test cases and identify coverage gaps.

What is the SFDIPOT framework in software testing?

The SFDIPOT framework is a product factors testing model from James Bach's HTSM that categorizes software elements into Structure, Function, Data, Interfaces, Platform, Operations, and Time to guide comprehensive test strategy generation and coverage assessment.

Can I use this SFDIPOT analysis for healthcare or finance domain user stories?

Yes, you can apply SFDIPOT analysis to healthcare and finance domains, as the Python-based evaluation processes detailed requirement factors and prioritizes test ideas for critical paths across e-commerce, healthcare, and finance contexts.

How does this approach prioritize test cases for epic planning?

This approach prioritizes test cases during epic planning by mapping software requirements against SFDIPOT categories, assigning priority levels to test ideas, and clarifying coverage gaps to ensure robust testing of critical paths.

Do I need a brutal honesty review dependency for software testing strategy generation?

Yes, the brutal honesty review dependency is required to critically evaluate the generated test strategy, ensuring that coverage gaps and prioritized test cases are rigorously assessed without bias during requirement analysis.

What are the limitations of using SFDIPOT for test coverage assessment?

A limitation of using SFDIPOT for coverage assessment is that it focuses strictly on product factors like Structure and Operations, meaning it evaluates static requirement completeness but may not dynamically capture runtime environment or performance testing variables.