Agent skill
doc-ftest
Create Functional Test Specifications (FTEST) as Layer 10 subtype artifacts focused on quality-attribute validation
Install this agent skill to your Project
npx add-skill https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-ftest
Metadata
Additional technical details for this skill
- tags
-
sdd-workflow layer-10-artifact ftest shared-architecture
- custom fields
-
{ "layer": 10, "version": "1.0", "priority": "shared", "last_updated": "2026-02-27", "artifact_type": "FTEST", "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 FTEST-MVP-TEMPLATE schema_version
SKILL.md
doc-ftest
Purpose
Create Functional Test Specifications (FTEST) for system-level quality attribute validation (Performance, Reliability, Security, Scalability) as a Layer 10 TSPEC subtype.
Layer: 10
Subtype Code: 43 (TSPEC.NN.43.SS)
Canonical References
Before authoring FTEST, read:
ai_dev_ssd_flow/10_TSPEC/FTEST/FTEST-MVP-TEMPLATE.mdai_dev_ssd_flow/10_TSPEC/FTEST/FTEST-MVP-TEMPLATE.yamlai_dev_ssd_flow/10_TSPEC/FTEST/FTEST-MVP-TEMPLATE.mdai_dev_ssd_flow/10_TSPEC/FTEST/FTEST_MVP_SCHEMA.yamlai_dev_ssd_flow/10_TSPEC/FTEST/FTEST_MVP_SCHEMA.yaml
When to Use
Use doc-ftest when:
- You are creating or editing FTEST-only artifacts.
@sysand@thresholdconstraints are primary.- Quality-attribute threshold validation is 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.
FTEST Contract (MVP)
Required Structure
FTEST follows a 6-section contract:
- Document Control
- Test Scope
- Test Case Index
- Test Case Details
- SYS Coverage Matrix
- Traceability
Required Tags
- Cumulative Layer-10 tags:
@brd,@prd,@ears,@bdd,@adr,@sys,@req,@spec(+@ctrif exists) - Type-specific required tags:
@sys,@threshold
Threshold and Coverage
- TASKS-Ready threshold:
>=90% - SYS coverage target: template-aligned (
>=85%baseline)
Folder Rule
Use nested folder structure:
docs/10_TSPEC/FTEST/FTEST-NN_{slug}/FTEST-NN_{slug}.md
Validation Commands
# FTEST subtype validation
python ai_dev_ssd_flow/10_TSPEC/scripts/validate_ftest.py docs/10_TSPEC/FTEST/
# 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/FTEST/FTEST-NN_slug/FTEST-NN_slug.md --auto-fix
# Cumulative tag validation
python ai_dev_ssd_flow/scripts/validate_tags_against_docs.py --artifact FTEST-NN --expected-layers brd,prd,ears,bdd,adr,sys,req,spec --strict
Output Quality Gate
- No schema/structure blockers.
- All required FTEST sections present.
@thresholdmappings are explicit for measurable criteria.- Traceability includes required cumulative tags.
- Report references use versioned naming where applicable.
Related Skills
doc-ftest-autopilotdoc-ftest-validatordoc-ftest-reviewerdoc-ftest-fixerdoc-ftest-auditdoc-tspec(multi-subtype fallback path)
Version History
| Version | Date | Changes |
|---|---|---|
| 1.0 | 2026-02-27 | Initial FTEST authoring skill; aligned to canonical FTEST MVP template/rules/schema; added TSPEC coexistence routing and canonical validation command set |
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?