Agent skill

doc-utest

Create Unit Test Specifications (UTEST) as Layer 10 subtype artifacts for component-level test validation

View SKILL.md on GitHub Repository
Stars 10
Forks 3

Install this agent skill to your Project

npx add-skill https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-utest

Metadata

Additional technical details for this skill

tags
sdd-workflow layer-10-artifact utest shared-architecture
custom fields 
{
    "layer": 10,
    "version": "1.0",
    "priority": "shared",
    "last_updated": "2026-02-27",
    "artifact_type": "UTEST",
    "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 UTEST-MVP-TEMPLATE schema_version

SKILL.md

doc-utest

Purpose

Create Unit Test Specifications (UTEST) for component-level validation as a Layer 10 TSPEC subtype with explicit REQ traceability and TASKS-ready quality gates.

Layer: 10
Subtype Code: 40 (TSPEC.NN.40.SS)

Canonical References

Before authoring UTEST, read:

  1. ai_dev_ssd_flow/10_TSPEC/UTEST/UTEST-MVP-TEMPLATE.md
  2. ai_dev_ssd_flow/10_TSPEC/UTEST/UTEST-MVP-TEMPLATE.yaml
  3. ai_dev_ssd_flow/10_TSPEC/UTEST/UTEST-MVP-TEMPLATE.md
  4. ai_dev_ssd_flow/10_TSPEC/UTEST/UTEST_MVP_SCHEMA.yaml
  5. ai_dev_ssd_flow/10_TSPEC/UTEST/UTEST_MVP_SCHEMA.yaml

When to Use

Use doc-utest when:

  • You are creating or editing UTEST-only artifacts.
  • @req and @spec mappings are primary.
  • Component-level logic, state, validation, and edge-case checks 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.

UTEST Contract (MVP)

Required Structure

UTEST follows a 6-section contract:

  1. Document Control
  2. Test Scope
  3. Test Case Index
  4. Test Case Details
  5. REQ Coverage Matrix
  6. Traceability

Required Tags

  • Cumulative Layer-10 tags: @brd, @prd, @ears, @bdd, @adr, @sys, @req, @spec (+ @ctr if exists)
  • UTEST-specific required tags: @req, @spec

Unit-Test Gate Requirements

  • TASKS-Ready score target must be >=90%.
  • REQ coverage target must be >=90%.
  • Test categories must include [Logic], [State], [Validation], [Edge].
  • Every test case must include an Input/Output table.
  • Complex test logic must include pseudocode.

Folder Rule

Use nested folder structure:

  • docs/10_TSPEC/UTEST/UTEST-NN_{slug}/UTEST-NN_{slug}.md

Validation Commands

bash
# UTEST subtype validation
python ai_dev_ssd_flow/10_TSPEC/scripts/validate_utest.py docs/10_TSPEC/UTEST/

# 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/UTEST/UTEST-NN_slug/UTEST-NN_slug.md --auto-fix

# Cumulative tag validation
python ai_dev_ssd_flow/scripts/validate_tags_against_docs.py --artifact UTEST-NN --expected-layers brd,prd,ears,bdd,adr,sys,req,spec --strict

Output Quality Gate

  • No schema/structure blockers.
  • All required UTEST sections present.
  • @req and @spec mappings are explicit.
  • REQ coverage and TASKS-ready scores meet >=90% target.
  • [Logic], [State], [Validation], [Edge] categories are represented.
  • Input/Output tables and pseudocode guidance are present where required.
  • Report references use versioned naming where applicable.

Related Skills

  • doc-utest-autopilot
  • doc-utest-validator
  • doc-utest-reviewer
  • doc-utest-fixer
  • doc-utest-audit
  • doc-tspec (multi-subtype fallback path)

Version History

Version Date Changes
1.0 2026-02-27 Initial UTEST authoring skill aligned to canonical UTEST MVP template/rules/schema with 90%-gate constraints and TSPEC coexistence routing

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

vladm3105/aidoc-flow-framework

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

10 3
Explore
vladm3105/aidoc-flow-framework

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

10 3
Explore
vladm3105/aidoc-flow-framework

doc-procspec-autopilot

Automated PROCSPEC (Process Specification) generation from REQ - generates specifications for SOPs, runbooks, playbooks, and operational procedures

10 3
Explore
vladm3105/aidoc-flow-framework

doc-riskspec-autopilot

Automated RISKSPEC (Risk Specification) generation from REQ - generates specifications for risk matrices, impact assessments, and mitigation plans

10 3
Explore
vladm3105/aidoc-flow-framework

doc-ptest-autopilot

Automated PTEST generation and review orchestration for performance category and threshold validation

10 3
Explore
vladm3105/aidoc-flow-framework

doc-adr-autopilot

Automated ADR generation pipeline from BRD Architecture Decision Requirements - analyzes topics, generates Context-Decision-Consequences records

10 3
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results