busya/ss-tools
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
Files
910a1f25258a0191a532e9012f01fc0f93b0485b
ss-tools/specs/027-dataset-llm-orchestration/checklists/requirements.md
busya 7c85552132 feat(ui): add chat-driven dataset review flow 
Move dataset review clarification into the assistant workspace and
rework the review page into a chat-centric layout with execution rails.

Add session-scoped assistant actions for mappings, semantic fields,
and SQL preview generation. Introduce optimistic locking for dataset
review mutations, propagate session versions through API responses,
and mask imported filter values before assistant exposure.

Refresh tests, i18n, and spec artifacts to match the new workflow.

BREAKING CHANGE: dataset review mutation endpoints now require the
X-Session-Version header, and clarification is no longer handled
through ClarificationDialog-based flows
2026-03-26 13:33:12 +03:00

2.0 KiB
Raw Blame History

Specification Quality Checklist: LLM Dataset Orchestration

Purpose: Validate specification completeness and quality before proceeding to planning
Created: 2026-03-16
Feature: spec.md

Content Quality

  • No implementation details (languages, frameworks, APIs)
  • Focused on user value and business needs
  • Written for non-technical stakeholders
  • All mandatory sections completed

UX Consistency

  • Functional requirements fully support the 'Happy Path' in ux_reference.md
  • Error handling requirements match the 'Error Experience' in ux_reference.md
  • No requirements contradict the defined User Persona or Context

Requirement Completeness

  • No [NEEDS CLARIFICATION] markers remain
  • Requirements are testable and unambiguous
  • Success criteria are measurable
  • Success criteria are technology-agnostic (no implementation details)
  • All acceptance scenarios are defined
  • Edge cases are identified
  • Scope is clearly bounded
  • Dependencies and assumptions identified

Feature Readiness

  • All functional requirements have clear acceptance criteria
  • User scenarios cover primary flows
  • Feature meets measurable outcomes defined in Success Criteria
  • No implementation details leak into specification

Notes

  • Validation completed against spec.md and ux_reference.md.
  • Automatic documentation, guided clarification, Superset-derived dataset execution, and manual fallback review are represented as independently testable user journeys.
  • Chat-centric workflow, collapsible completed phases, multi-dataset tabbed review scope, and per-dataset exclusion behavior are reflected in both the specification and UX reference.
  • Error recovery is aligned between the UX reference and the functional requirements, especially for partial filter import, missing run-time values, conflicting metadata, and unavailable LLM assistance.
  • The specification is ready for the next phase.