name: beamho-sdd-workflow description: Use when developing, reviewing, or closing work in beamHO-bench that is governed by an active pending SDD, especially when the task requires reading PROJECT_CONSTRAINTS, active pending status, validation rules, and lifecycle-sync docs before editing code.
beamHO SDD Workflow
Use this skill for beamHO-bench/ when the task is tied to an active pending SDD or when lifecycle status may need updating.
Required Read Order
Read these first:
PROJECT_CONSTRAINTS.mdsdd/completed/beamHO-bench-implementation-status.mdsdd/pending/README.md- the current active pending SDD
- if frontend satellite behavior is involved:
docs/zh-TW/07-observer-sky-visual-acceptance.md- related closure-tracked frontend SDDs for lower-layer context
Workflow
- Check
git status --short. - Identify the active pending SDD from status docs.
- Read only the files needed for the current delivery.
- Implement the current delivery directly; do not stop at analysis.
- Run validation appropriate to the change.
- Sync lifecycle docs if the delivery changes pending/completed truth.
- Report:
- delivery reached
- core files changed
- validation results
- remaining open items
Frontend Rule
If the change affects observer-sky rendering:
- passing automated tests is not enough
- the result must also satisfy:
docs/zh-TW/07-observer-sky-visual-acceptance.md
- do not close the SDD early from proxy metrics such as:
- sector diversity only
- determinism only
- retained-ID counts only
Validation Defaults
Prefer this set unless the task is docs-only:
npm run lintnpm run test:simnpm run buildnpm run validate:stage
If validation is skipped, say so explicitly and explain why.
Lifecycle Rules
sdd/completed/beamHO-bench-implementation-status.mdis the authority.sdd/pending/README.mdandsdd/README.mdmust stay in sync with it.- Closure-tracked status requires:
- implementation exists
- validation evidence exists
- lifecycle docs are updated
- visual/manual acceptance is satisfied for frontend packages