qcsd-refinement-swarm

QCSD Refinement Swarm v1.0 Shift-left quality engineering swarm for Sprint Refinement sessions. Overview The Refinement Swarm takes user stories that passed Ideation and prepares them for Sprint commitment. Where the Ideation Swarm asks "Should we build this?" using HTSM quality criteria, the Refinement Swarm asks "How should we test this?" using SFDIPOT product factors, BDD scenarios, and INVEST validation. Key Differentiators from Ideation Swarm Dimension Ideation Swarm Refinement Swarm Framework HTSM v6.3 (10 categories) SFDIPOT (7 factors, 37 subcategories) Agents 9 (3 core + 6 conditional) 10 (3 core + 6 conditional + 1 transformation) Core Output Quality Criteria HTML report BDD Gherkin scenarios Decision GO / CONDITIONAL / NO-GO READY / CONDITIONAL / NOT-READY Flags HAS_UI, HAS_SECURITY, HAS_UX, HAS_MIDDLEWARE, HAS_SAP_INTEGRATION, HAS_AUTHORIZATION HAS_API, HAS_REFACTORING, HAS_DEPENDENCIES, HAS_SECURITY, HAS_MIDDLEWARE, HAS_SAP_INTEGRATION, HAS_AUTHORIZATION Phase PI Planning / Sprint Planning Sprint Refinement Final Step Report generation Test idea rewriter transformation ENFORCEMENT RULES - READ FIRST These rules are NON-NEGOTIABLE. Violation means skill execution failure. Rule Enforcement E1 You MUST spawn ALL THREE core agents (qe-product-factors-assessor, qe-bdd-generator, qe-requirements-validator) in Phase 2. No exceptions. E2 You MUST put all parallel Task calls in a SINGLE message. E3 You MUST STOP and WAIT after each batch. No proceeding early. E4 You MUST spawn conditional agents if flags are TRUE. No skipping. E5 You MUST apply READY/CONDITIONAL/NOT-READY logic exactly as specified in Phase 5. E6 You MUST generate the full report structure. No abbreviated versions. E7 Each agent MUST read its reference files before analysis. E8 You MUST apply qe-test-idea-rewriter transformation on ALL test ideas in Phase 8. Always. E9 You MUST execute Phase 7 learning persistence. Store refinement findings to memory BEFORE Phase 8. No skipping. PROHIBITED BEHAVIORS: Summarizing instead of spawning agents Skipping agents "for brevity" Proceeding before background tasks complete Providing your own analysis instead of spawning specialists Omitting report sections Using placeholder text like "[details here]" Skipping the test idea rewriter transformation Skipping learning persistence (Phase 7) or treating it as optional Generating BDD scenarios yourself instead of using qe-bdd-generator PHASE 1: Analyze Story Content (Flag Detection) MANDATORY: You must complete this analysis before Phase 2. Scan the story content and SET these flags. Do not skip any flag. Flag Detection (Check ALL SEVEN) HAS_API = FALSE Set TRUE if story contains ANY of: API, endpoint, REST, GraphQL, contract, integration, webhook, microservice, service-to-service, HTTP, gRPC, request, response, payload, schema, OpenAPI, Swagger, consumer, provider HAS_REFACTORING = FALSE Set TRUE if story contains ANY of: refactor, rearchitect, rewrite, migrate, modernize, tech debt, legacy, restructure, decouple, consolidate, simplify, extract, decompose, re-engineer HAS_DEPENDENCIES = FALSE Set TRUE if story contains ANY of: dependency, coupling, module, package, library, import, shared, cross-team, upstream, downstream, third-party, external, vendor, SDK, plugin, middleware HAS_SECURITY = FALSE Set TRUE if story contains ANY of: auth, security, credential, token, encrypt, PII, compliance, password, login, session, OAuth, JWT, permission, role, access control, RBAC, sensitive, private HAS_MIDDLEWARE = FALSE Set TRUE if story contains ANY of: middleware, ESB, message broker, MQ, Kafka, RabbitMQ, integration bus, API gateway, message queue, pub/sub HAS_SAP_INTEGRATION = FALSE Set TRUE if story contains ANY of: SAP, RFC, BAPI, IDoc, OData, S/4HANA, EWM, ECC, ABAP, CDS view, Fiori HAS_AUTHORIZATION = FALSE Set TRUE if story contains ANY of: SoD, segregation of duties, role conflict, authorization object, T-code, user role, access control matrix, GRC Validation Checkpoint Before proceeding to Phase 2, confirm: +-- I have read the entire story content +-- I have evaluated ALL SEVEN flags +-- I have recorded which flags are TRUE +-- I understand which conditional agents will be needed DO NOT proceed to Phase 2 until all checkboxes are confirmed. MANDATORY: Output Flag Detection Results You MUST output flag detection results before proceeding: +-------------------------------------------------------------+ | FLAG DETECTION RESULTS | +-------------------------------------------------------------+ | | | HAS_API: [TRUE/FALSE] | | Evidence: [what triggered it - specific patterns] | | | | HAS_REFACTORING: [TRUE/FALSE] | | Evidence: [what triggered it - specific patterns] | | | | HAS_DEPENDENCIES: [TRUE/FALSE] | | Evidence: [what triggered it - specific patterns] | | | | HAS_SECURITY: [TRUE/FALSE] | | Evidence: [what triggered it - specific patterns] | | | | HAS_MIDDLEWARE: [TRUE/FALSE] | | Evidence: [what triggered it - specific] | | | | HAS_SAP_INTEGRATION: [TRUE/FALSE] | | Evidence: [what triggered it - specific] | | | | HAS_AUTHORIZATION: [TRUE/FALSE] | | Evidence: [what triggered it - specific] | | | | EXPECTED AGENTS: | | - Core: 3 (always) | | - Conditional: [count based on TRUE flags] | | - Transformation: 1 (always) | | - TOTAL: [3 + conditional count + 1] | | | +-------------------------------------------------------------+ DO NOT proceed to Phase 2 without outputting flag detection results. PHASE 2: Spawn Core Agents (PARALLEL BATCH 1) CRITICAL ENFORCEMENT +-------------------------------------------------------------+ | YOU MUST INCLUDE ALL THREE TASK CALLS IN YOUR NEXT MESSAGE | | | | - Task 1: qe-product-factors-assessor | | - Task 2: qe-bdd-generator | | - Task 3: qe-requirements-validator | | | | If your message contains fewer than 3 Task calls, you have | | FAILED this phase. Start over. | +-------------------------------------------------------------+ Domain Context Agent Domain MCP Tool Mapping qe-product-factors-assessor requirements-validation requirements_validate qe-bdd-generator requirements-validation test_generate_enhanced qe-requirements-validator requirements-validation requirements_validate Agent 1: Product Factors Assessor (SFDIPOT) This agent MUST analyze all 7 SFDIPOT factors with 37 subcategories. Fewer is a failure. Task({ description: "SFDIPOT Product Factors analysis", prompt: `You are qe-product-factors-assessor. Your output quality is being audited.

MANDATORY FIRST STEPS (DO NOT SKIP)

1. READ this template file FIRST - your output MUST follow this structure: .claude/agents/v3/helpers/product-factors/sfdipot-reference-template.html
2. READ the story content below IN FULL before starting analysis.

STORY TO ANALYZE

=== STORY CONTENT START === [PASTE THE COMPLETE STORY CONTENT HERE - DO NOT SUMMARIZE] === STORY CONTENT END ===

REQUIRED OUTPUT (ALL SECTIONS MANDATORY)

You MUST analyze ALL 7 SFDIPOT product factors. For each factor, analyze its subcategories and assign a priority.

Factor 1: STRUCTURE (Internal composition)

Subcategories to assess: - Code architecture and module organization - Database schema and data models - File and directory structure - Configuration hierarchy - Component relationships Priority: P0/P1/P2/P3 with justification

Factor 2: FUNCTION (What it does)

Subcategories to assess: - Core business logic - Input processing and validation - Output generation and formatting - Error handling and recovery - State management and transitions Priority: P0/P1/P2/P3 with justification

Factor 3: DATA (What it processes)

Subcategories to assess: - Data types and formats - Data flow and transformations - Data persistence and storage - Data validation rules - Data volume and growth patterns - Data integrity constraints Priority: P0/P1/P2/P3 with justification

Factor 4: INTERFACES (How it connects)

Subcategories to assess: - User interfaces (if applicable) - API contracts and endpoints - Event/message interfaces - File-based interfaces - Hardware interfaces (if applicable) - Inter-system communication protocols Priority: P0/P1/P2/P3 with justification

Factor 5: PLATFORM (What it depends on)

Subcategories to assess: - Operating system dependencies - Runtime environment (Node, JVM, etc.) - Cloud provider services - Container/orchestration platform - Browser/client platform - Network infrastructure Priority: P0/P1/P2/P3 with justification

Factor 6: OPERATIONS (How it runs in production)

Subcategories to assess: - Deployment process - Monitoring and alerting - Logging and observability - Backup and recovery - Scaling and capacity - Incident response procedures Priority: P0/P1/P2/P3 with justification

Factor 7: TIME (How it changes)

Subcategories to assess: - Scheduling and time-based triggers - Temporal data (timestamps, durations) - Concurrency and race conditions - Timeout and retry behavior - Historical data and versioning - Time zone handling Priority: P0/P1/P2/P3 with justification

SCORING REQUIREMENTS

For each of the 7 factors, provide: | Field | Requirement | |-------|-------------| | Factor Name | One of the 7 SFDIPOT factors | | Priority | P0, P1, P2, or P3 with justification | | Subcategories Assessed | Count of subcategories analyzed | | Coverage Depth | Shallow / Adequate / Deep | | Key Findings | Top 3 findings for this factor | | Test Focus Areas | Specific areas requiring test coverage |

OUTPUT FORMAT

Save your complete analysis in Markdown to: ${OUTPUT_FOLDER}/02-sfdipot-analysis.md Use the Write tool to save BEFORE completing. Report MUST be complete - no placeholders.

VALIDATION BEFORE SUBMITTING

+-- Did I read the SFDIPOT reference template? +-- Did I analyze all 7 factors? +-- Did I assess at least 37 subcategories total? +-- Does every factor have a priority with justification? +-- Did I identify test focus areas for each factor? +-- Did I save the report to the correct output path?, subagent_type: "qe-product-factors-assessor", run_in_background: true }) Agent 2: BDD Scenario Generator This agent MUST generate at least 5 Gherkin scenarios. Fewer is a failure. Task({ description: "BDD Gherkin scenario generation", prompt:You are qe-bdd-generator. Your output quality is being audited.

METHODOLOGY

Apply Behaviour-Driven Development (BDD) principles to generate comprehensive Gherkin scenarios from the story and its acceptance criteria.

STORY TO ANALYZE

=== STORY CONTENT START === [PASTE THE COMPLETE STORY CONTENT HERE - DO NOT SUMMARIZE] === STORY CONTENT END ===

REQUIRED OUTPUT (ALL SECTIONS MANDATORY)

1. Feature File Header

Write a proper Gherkin feature header: Feature: [Feature name derived from story] As a [role from story] I want [capability from story] So that [business value from story]

2. Scenario Categories (ALL MANDATORY)

You MUST generate scenarios in ALL of these categories:

Category A: Happy Path Scenarios (minimum 2)

• Primary success flow
• Variant success flows

Category B: Error/Negative Path Scenarios (minimum 2)

• Invalid input handling
• System error handling
• Boundary violations

Category C: Boundary/Edge Case Scenarios (minimum 1)

• Minimum and maximum values
• Empty states
• Null/undefined handling

Category D: Security Scenarios (if HAS_SECURITY flag is TRUE)

• Authentication failures
• Authorization violations
• Data protection scenarios

3. Gherkin Format Requirements

EVERY scenario MUST follow this structure: Scenario: [Descriptive name] Given [precondition with specific data] And [additional precondition if needed] When [action with specific input] And [additional action if needed] Then [expected outcome with specific assertion] And [additional assertion if needed] RULES: - Use concrete data, not abstract descriptions - Include data tables where 3+ similar checks apply - Use Scenario Outline + Examples for parameterized cases - Every Then step must be verifiable/assertable - No vague steps like "the system works correctly"

4. Scenario Outline with Examples (minimum 1)

At least one scenario MUST use Scenario Outline: Scenario Outline: [Parameterized scenario name] Given [precondition with ] When [action with ] Then [expected ] Examples: | parameter | input | outcome | | value1 | val1 | result1 | | value2 | val2 | result2 | | value3 | val3 | result3 |

5. Traceability Matrix

Map each scenario back to acceptance criteria: | Scenario | Acceptance Criterion | Category | |----------|---------------------|----------| | Scenario 1 | AC-1 | Happy Path | | Scenario 2 | AC-1, AC-3 | Error Path | | ... | ... | ... |

6. Summary Metrics