skills.rest
Emrebener
EmrebenerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ss-sdd-testing-feature

Execute Given/When/Then acceptance scenarios to verify SDD feature behavior.

Updated May 19, 2026
Search Tags:#test strategy#mcp#acceptance criteria#sdd#integration verification#feature testing#spec validation
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-testing-feature
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-sdd-testing-feature
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/spec-driven-development/ss-sdd-testing-feature
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-testing-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures an implemented feature actually fulfills the acceptance criteria defined in the spec, using real available tools rather than assumptions or fabricated results.

Core Features & Use Cases

  • Feature-level verification: Executes Given/When/Then acceptance scenarios for each P1 user story to validate end-to-end behavior.
  • Depth-scoped coverage: Uses dispatcher-provided DEPTH to run either only P1 golden paths (quick) or P1 edge cases plus straightforward P2/P3 (standard).
  • Honest tool availability handling: Returns PASS, FAIL, or MCP_UNAVAILABLE and includes a manual test plan when required MCPs/runners are not available.

Quick Start

Ask your agent to run the ss-sdd-testing-feature skill for the SDD feature at DEPTH standard using the provided SPEC_PATH and PLAN_PATH so it can report PASS, FAIL, or MCP_UNAVAILABLE with the scenarios it truly exercised.

Frequently Asked Questions about ss-sdd-testing-feature

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

FAQPage Schema
How do I verify a spec-built feature end-to-end against acceptance criteria?▼

Spec-built feature end-to-end verification executes Given/When/Then acceptance scenarios for each P1 user story, ensuring the implemented behavior matches the spec using real MCPs or runners.

What is the best way to run feature testing for SDD acceptance scenarios?▼

Feature testing for SDD acceptance scenarios uses dispatcher inputs like DEPTH, SPEC_PATH, and PLAN_PATH to select the correct testing strategy, executing real runners to validate end-to-end behavior.

Can I execute spec validation when required MCPs are unavailable?▼

Spec validation cannot execute real tests when MCPs are unavailable; the runner returns MCP_UNAVAILABLE and provides a manual test plan to ensure honest coverage reporting without fabrication.

Does depth-scoped coverage affect integration verification of P1 user stories?▼

Depth-scoped coverage directly affects integration verification by using the DEPTH input to run either only P1 golden paths for quick checks or P1 edge cases plus straightforward P2/P3 scenarios for standard verification.

Why does feature testing return MCP_UNAVAILABLE instead of failing the build?▼

Feature testing returns MCP_UNAVAILABLE to maintain honest execution integrity, signaling that required MCPs or runners are missing so it cannot exercise the Given/When/Then scenarios without modifying code or fabricating results.

Related Skills

Explore More Software Engineering Skills→
EmrebenerEmrebener

ss-sdd-testing-implementation

Coordinate feature-level SDD testing with a tester subagent and bounded fix loop.

Community
Advanced
TruCol270TruCol270
1

springboot-verification

Automate Spring Boot project verification with builds, tests, coverage, and security scans.

Community
Advanced
YangYuS8YangYuS8

requesting-code-review

Request code review with a structured template before merging changes.

Community
Intermediate
opsMachineopsMachine
1

plan-tests

Generate a structured Test Plan from an approved spec by mapping acceptance criteria to test types.

Official
Intermediate