Files
gps-denied-onboard/.cursor/skills/plan/steps/00_prerequisites.md
T
Oleksandr Bezdieniezhnykh 1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
Update demo replay validation and testing documentation
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.
2026-06-20 11:24:43 +03:00

1.2 KiB

Prerequisite Checks (BLOCKING)

Run sequentially before any planning step:

Prereq 1: Data Gate

  1. _docs/00_problem/acceptance_criteria.md exists and is non-empty — STOP if missing
  2. _docs/00_problem/restrictions.md exists and is non-empty — STOP if missing
  3. _docs/00_problem/input_data/ exists and contains at least one data file — STOP if missing
  4. _docs/00_problem/problem.md exists and is non-empty — STOP if missing

All four are mandatory. If any is missing or empty, STOP and ask the user to provide them. If the user cannot provide the required data, planning cannot proceed — just stop.

Prereq 2: Finalize Solution Draft

Only runs after the Data Gate passes:

  1. Scan _docs/01_solution/ for files matching solution_draft*.md
  2. Identify the highest-numbered draft (e.g. solution_draft06.md)
  3. Rename it to _docs/01_solution/solution.md
  4. If solution.md already exists, ask the user whether to overwrite or keep existing
  5. Verify solution.md is non-empty — STOP if missing or empty

Prereq 3: Workspace Setup

  1. Create DOCUMENT_DIR if it does not exist
  2. If DOCUMENT_DIR already contains artifacts, ask user: resume from last checkpoint or start fresh?