schema: spec-driven

context: |
  Tech stack: Python 3.11+, requests, SAP ADT REST API
  CLI framework: argparse (subcommand pattern)
  Architecture: CLI → ADT REST API → SAP System
  Testing: unittest
  Code style: PEP 8, type hints, f-strings
  SAP object types: report, class, interface, function, functiongroup, domain, dataelement, table, structure, tabletype

rules:
  proposal:
    - Focus on user-visible behavior changes, not implementation
    - Identify affected capabilities by checking existing specs
  specs:
    - Use WHEN/THEN format for scenarios (not Gherkin code blocks)
    - Describe observable behavior only, no ADT endpoints or class names
    - Every requirement MUST have at least one scenario
    - Use RFC 2119 keywords: SHALL/MUST for mandatory, SHOULD for recommended
  design:
    - Include ADT endpoint details and technical rationale
    - Consider SAP transport management implications
  tasks:
    - Each task independently verifiable
    - "Use checkbox format: - [ ] X.Y Description"