/attest

Criteria Extraction and Specification Quality

Purpose: Read this when ingesting a specification, extracting AC-* criteria, classifying testability, raising AMBIGUOUS_FLAG, or scoring specification quality.

Contents

• Source format detection
• Extraction strategies by format
• Testability classification
• Dangerous expression catalog
• Requirement smells
• Acceptance-criteria quality patterns
• Specification quality metrics
• AMBIGUOUS_FLAG protocol
• Criterion ID convention
• INGEST-time quality check flow
• Output format

Source Format Detection

Auto-Detection Rules

Confidence Threshold

Extraction Strategies by Format

Scribe[unified] L3

Source: ## L3 受入基準 / ## Acceptance Criteria
  -> Each bullet becomes one AC
  -> ID: AC-{feature}-{NNN}
  -> Priority: inherit from parent priority when available
  -> Testability: classify with the matrix below

PRD / SRS

Source: numbered functional requirements
  -> Split compound requirements into separate ACs
  -> MUST / SHALL -> CRITICAL
  -> SHOULD -> HIGH
  -> MAY -> MEDIUM or LOW depending on business impact

User Stories

Primary AC:
  derive from the "I want" canon

Additional ACs:
  derive from explicit acceptance bullets

Implicit ACs:
  infer only when the "so that" canon makes the benefit testable

Free-Form Text

1. Extract action verbs and affected entities
2. Convert them into testable assertions
3. Mark uncertain items as PARTIALLY_TESTABLE or AMBIGUOUS
4. Prefer clarification over over-inference

Testability Classification

Testability Matrix

Dangerous Expression Catalog

Every match below should trigger AMBIGUOUS_FLAG.

Requirement Smells

Acceptance-Criteria Quality Patterns

Good Traits

Quality Anti-Patterns

Specification Quality Metrics

Quality Score

GOOD: Ambiguity < 10%, Testability > 80%, Completeness > 90%
FAIR: Ambiguity < 20%, Testability > 60%, Completeness > 70%
POOR: Below FAIR -> route to Scribe / Scribe[unified] for improvement

AMBIGUOUS_FLAG Protocol

AMBIGUOUS_FLAG:
  criterion_id: AC-LOGIN-005
  original_text: "The login should be fast"
  ambiguity_type: UNMEASURABLE | CONTRADICTORY | INCOMPLETE | SUBJECTIVE | OPEN_ENDED
  what_is_missing: "No latency threshold defined"
  suggested_clarification: "Login response time should be under 500ms at P95"
  impact: HIGH
  route_to: Scribe

Criterion ID Convention

AC-{FEATURE}-{NNN}

Examples:
  AC-LOGIN-001
  AC-PAYMENT-015
  AC-GLOBAL-001

Priority Assignment

INGEST-Time Quality Check Flow

1. Dangerous-expression scan -> AMBIGUOUS_FLAG
2. Testability classification -> TESTABLE / PARTIALLY_TESTABLE / AMBIGUOUS
3. Completeness check -> normal / error / boundary coverage present?
4. Consistency check -> contradiction candidates for adversarial probing
5. NFR check -> performance / security / accessibility criteria present?
6. Quality score -> GOOD / FAIR / POOR

Output Format

EXTRACTED_CRITERIA:
  spec_source: "docs/login-spec.md"
  spec_format: SCRIBE_L3 | PRD | USER_STORY | FREE_FORM
  extraction_confidence: 0.95
  spec_quality: GOOD | FAIR | POOR
  total_criteria: 12
  by_priority:
    CRITICAL: 3
    HIGH: 5
    MEDIUM: 3
    LOW: 1
  by_testability:
    TESTABLE: 8
    PARTIALLY_TESTABLE: 3
    AMBIGUOUS: 1
  criteria:
    - id: AC-LOGIN-001
      text: "Valid credentials grant access to dashboard"
      priority: CRITICAL
      testability: TESTABLE
      source: "login-spec.md:L24"
      related_criteria: [AC-LOGIN-002, AC-LOGIN-003]
  ambiguity_flags:
    - criterion_id: AC-LOGIN-005
      type: UNMEASURABLE
      suggestion: "Define latency threshold"

ISO/IEC/IEEE 29148 Quality Gate (SKILL.md excerpt)

Before extraction is complete, validate each criterion against these attributes:

Flag violations as QUALITY_DEFECT:{attribute} and report in Specification Quality Feedback.

INTERACTION_TRIGGERS Question Templates (SKILL.md excerpt)

questions:
  - question: "No specification found. How would you like to proceed?"
    header: "Spec Source"
    options:
      - label: "Delegate spec creation to Scribe/Scribe[unified]"
        description: "Create the specification first, then run verification"
      - label: "Reverse-extract spec from code (EXTRACT)"
        description: "Infer implicit specifications from existing implementation and report"
      - label: "Specify the spec file path manually"
        description: "Provide the specification file location manually"
    multiSelect: false

questions:
  # Use only when verification scope was not already authorized; never narrow frozen ACs.
  - question: "The specification contains 20+ acceptance criteria and scope is unspecified. Select the verification scope."
    header: "Scope"
    options:
      - label: "Verify all criteria (recommended)"
        description: "Exhaustively verify every acceptance criterion"
      - label: "CRITICAL/HIGH only"
        description: "Limit verification to high-priority criteria"
      - label: "Diff-related criteria only"
        description: "Auto-select criteria affected by recent changes"
    multiSelect: false

Signal Keywords → Recipe (SKILL.md excerpt)

For natural-language input without a subcommand; a subcommand match wins. Mode auto-detect runs in parallel — explicit Recipe selection overrides it.

Required Criterion Fields (SKILL.md excerpt)

Set AMBIGUOUS_FLAG whenever the spec is subjective, incomplete, contradictory, or unmeasurable.