Agent skill
doc-stest
Create Smoke Test Specifications (STEST) as Layer 10 subtype artifacts for deployment critical-path validation
Install this agent skill to your Project
npx add-skill https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-stest
Metadata
Additional technical details for this skill
- tags
-
sdd-workflow layer-10-artifact stest shared-architecture
- custom fields
-
{ "layer": 10, "version": "1.0", "priority": "shared", "last_updated": "2026-02-27", "artifact_type": "STEST", "skill_category": "core-workflow", "development_status": "active", "upstream_artifacts": [ "BRD", "PRD", "EARS", "BDD", "ADR", "SYS", "REQ", "CTR", "SPEC" ], "downstream_artifacts": [ "TASKS", "Code" ], "architecture_approaches": [ "ai-agent-based", "traditional-8layer" ] } - versioning policy
- tracks STEST-MVP-TEMPLATE schema_version
SKILL.md
doc-stest
Purpose
Create Smoke Test Specifications (STEST) for deployment critical-path validation with strict fail-fast pass/fail outcomes as a Layer 10 TSPEC subtype.
Layer: 10
Subtype Code: 42 (TSPEC.NN.42.SS)
Canonical References
Before authoring STEST, read:
ai_dev_ssd_flow/10_TSPEC/STEST/STEST-MVP-TEMPLATE.mdai_dev_ssd_flow/10_TSPEC/STEST/STEST-MVP-TEMPLATE.yamlai_dev_ssd_flow/10_TSPEC/STEST/STEST-MVP-TEMPLATE.mdai_dev_ssd_flow/10_TSPEC/STEST/STEST_MVP_SCHEMA.yamlai_dev_ssd_flow/10_TSPEC/STEST/STEST_MVP_SCHEMA.yaml
When to Use
Use doc-stest when:
- You are creating or editing STEST-only artifacts.
@ears,@bdd, and@reqconstraints are primary.- Deployment smoke validation and critical-path rollback readiness are the core objective.
Use doc-tspec instead when:
- Multi-subtype orchestration is required (UTEST/ITEST/STEST/FTEST/PTEST/SECTEST).
- Cross-subtype normalization or batch TSPEC work is primary.
STEST Contract (MVP)
Required Structure
STEST follows a 6-section contract:
- Document Control
- Test Scope
- Critical Path Index
- Test Case Details
- Rollback Procedures
- Traceability
Required Tags
- Cumulative Layer-10 tags:
@brd,@prd,@ears,@bdd,@adr,@sys,@req,@spec(+@ctrif exists) - Type-specific required tags:
@ears,@bdd,@req
Deployment Gate Requirements
- Total timeout budget must be
<=300s(max 300s / <5 minutes) - Quality gate target is
100% quality gate(Target: 100%) - Every test must have rollback procedure
- Pass/fail criteria must be binary and fail-fast
Folder Rule
Use nested folder structure:
docs/10_TSPEC/STEST/STEST-NN_{slug}/STEST-NN_{slug}.md
Validation Commands
# STEST subtype validation
python ai_dev_ssd_flow/10_TSPEC/scripts/validate_stest.py docs/10_TSPEC/STEST/
# Layer-wide TSPEC validation
bash ai_dev_ssd_flow/10_TSPEC/scripts/validate_all_tspec.sh docs/10_TSPEC/
# Quality score validation
bash ai_dev_ssd_flow/10_TSPEC/scripts/validate_tspec_quality_score.sh docs/10_TSPEC/
# Cross-document validation
python ai_dev_ssd_flow/scripts/validate_cross_document.py --document docs/10_TSPEC/STEST/STEST-NN_slug/STEST-NN_slug.md --auto-fix
# Cumulative tag validation
python ai_dev_ssd_flow/scripts/validate_tags_against_docs.py --artifact STEST-NN --expected-layers brd,prd,ears,bdd,adr,sys,req,spec --strict
Output Quality Gate
- No schema/structure blockers.
- All required STEST sections present.
@ears,@bdd, and@reqmappings are explicit.- Timeout and rollback constraints are present.
- Binary pass/fail criteria are explicit for critical paths.
- Report references use versioned naming where applicable.
Related Skills
doc-stest-autopilotdoc-stest-validatordoc-stest-reviewerdoc-stest-fixerdoc-stest-auditdoc-tspec(multi-subtype fallback path)
Version History
| Version | Date | Changes |
|---|---|---|
| 1.0 | 2026-02-27 | Initial STEST authoring skill aligned to canonical STEST MVP template/rules/schema with deployment-gate constraints and TSPEC coexistence routing |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
doc-spec-reviewer
Comprehensive content review and quality assurance for SPEC documents - validates YAML structure, REQ coverage, interface definitions, and identifies issues requiring manual attention
doc-prd-fixer
Automated fix skill that reads review reports and applies fixes to PRD documents - handles broken links, element IDs, missing files, and iterative improvement
doc-procspec-autopilot
Automated PROCSPEC (Process Specification) generation from REQ - generates specifications for SOPs, runbooks, playbooks, and operational procedures
doc-riskspec-autopilot
Automated RISKSPEC (Risk Specification) generation from REQ - generates specifications for risk matrices, impact assessments, and mitigation plans
doc-ptest-autopilot
Automated PTEST generation and review orchestration for performance category and threshold validation
doc-adr-autopilot
Automated ADR generation pipeline from BRD Architecture Decision Requirements - analyzes topics, generates Context-Decision-Consequences records
Didn't find tool you were looking for?