Agent skill

doc-ftest-reviewer

Review FTEST content quality, SYS alignment, and threshold validation completeness for functional test specifications

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-ftest-reviewer

Metadata

Additional technical details for this skill

tags
sdd-workflow layer-10-artifact quality-assurance ftest-review
custom fields
{
    "layer": 10,
    "version": "1.0",
    "priority": "primary",
    "last_updated": "2026-02-27",
    "artifact_type": "FTEST",
    "skill_category": "quality-assurance",
    "development_status": "active",
    "upstream_artifacts": [
        "FTEST"
    ],
    "downstream_artifacts": [],
    "architecture_approaches": [
        "ai-agent-based"
    ]
}
versioning policy
tracks FTEST-MVP-TEMPLATE schema_version

SKILL.md

doc-ftest-reviewer

Purpose

Perform semantic quality review for FTEST artifacts beyond structural validation.


Review Scope

  1. SYS requirement alignment and quality-attribute coverage
  2. Threshold definitions and measurable validation criteria
  3. Test case completeness (workflow steps + measurement methodology)
  4. Edge-case and failure-condition coverage
  5. Traceability completeness and consistency

Output Contract

Reviewer-native output:

  • FTEST-NN.R_review_report_vNNN.md

Audit-wrapper compatibility:

  • doc-ftest-audit may emit FTEST-NN.A_audit_report_vNNN.md as preferred fixer input.

All reports are colocated with parent FTEST file.


Score Gate

  • Pass target: score >=90
  • Manual-required findings block automated completion.

Related Skills

  • doc-ftest-validator
  • doc-ftest-fixer
  • doc-ftest-audit
  • doc-ftest-autopilot

Version History

Version Date Changes
1.0 2026-02-27 Initial FTEST reviewer with audit-compatible report contract and threshold-based pass gate

Implementation Plan Consistency (IPLAN-004)

  • Treat plan-derived outputs as valid source mode and verify intent preservation from implementation plan scope/objectives.
  • Validate upstream autopilot precedence assumption: --iplan > --ref > --prompt.
  • Flag objective/scope conflicts between plan context and artifact output as blocking issues requiring clarification.
  • Do not introduce legacy fallback paths such as docs-v2.0/00_REF.

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

Didn't find tool you were looking for?

Be as detailed as possible for better results