115 lines
3.3 KiB
Markdown
115 lines
3.3 KiB
Markdown
# Scene Skill 102 Pseudo-Production Batch Execution Preparation Plan
|
|
|
|
> Date: 2026-04-20
|
|
> Status: Draft
|
|
> Upstream Design: `docs/superpowers/specs/2026-04-20-scene-skill-102-pseudoprod-batch-execution-preparation-design.md`
|
|
|
|
## Plan Intent
|
|
|
|
Prepare the first pseudo-production batch for execution without executing it.
|
|
|
|
This plan creates handoff and evidence templates for the 10 selected scenes.
|
|
|
|
## Fixed Inputs
|
|
|
|
1. `tests/fixtures/generated_scene/scene_skill_102_pseudoprod_batch_selection_2026-04-20.json`
|
|
2. `examples/scene_skill_102_final_materialization_2026-04-19/scene_skill_102_index.json`
|
|
3. `tests/fixtures/generated_scene/scene_skill_102_full_direct_mock_execution_2026-04-20.json`
|
|
|
|
## Planned Outputs
|
|
|
|
1. `tests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_handoff_2026-04-20.json`
|
|
2. `tests/fixtures/generated_scene/scene_skill_102_pseudoprod_execution_record_template_2026-04-20.json`
|
|
3. `tests/fixtures/generated_scene/scene_skill_102_pseudoprod_evidence_checklist_2026-04-20.json`
|
|
4. `docs/superpowers/reports/2026-04-20-scene-skill-102-pseudoprod-batch-execution-preparation-report.md`
|
|
|
|
## Allowed Files
|
|
|
|
1. planned JSON assets
|
|
2. planned report
|
|
|
|
## Forbidden Files
|
|
|
|
1. `src/generated_scene/analyzer.rs`
|
|
2. `src/generated_scene/generator.rs`
|
|
3. `src/generated_scene/ir.rs`
|
|
4. `examples/scene_skill_102_final_materialization_2026-04-19/skills/**`
|
|
5. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
|
|
## Phase 0: Freeze Preparation Boundary
|
|
|
|
### Tasks
|
|
|
|
1. Confirm selected batch is exactly 10 scenes.
|
|
2. Confirm all 10 are direct-mock-pass.
|
|
3. Confirm no browser/network execution happens in this plan.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. No production or quasi-production target is invoked.
|
|
2. No credentials are requested or stored.
|
|
|
|
## Phase 1: Build Environment Handoff
|
|
|
|
### Tasks
|
|
|
|
1. List required environment inputs for the operator.
|
|
2. Map required dependencies per selected scene.
|
|
3. Define credential handling rule: outside repository only.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Every selected scene has environment prerequisites.
|
|
2. The handoff asset contains no credential values.
|
|
|
|
## Phase 2: Build Evidence Checklist
|
|
|
|
### Tasks
|
|
|
|
1. Define evidence required for each scene.
|
|
2. Define evidence file names.
|
|
3. Define redaction requirements for logs and screenshots.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Every selected scene has an evidence checklist.
|
|
2. Every checklist includes final execution classification.
|
|
|
|
## Phase 3: Build Execution Record Template
|
|
|
|
### Tasks
|
|
|
|
1. Define common execution record fields.
|
|
2. Include per-scene placeholders for operator output.
|
|
3. Include allowed result states and failure taxonomy.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. The template can record pass, blocker, mismatch, and runtime error.
|
|
2. The template stores references to evidence files, not credentials.
|
|
|
|
## Phase 4: Publish Preparation Report
|
|
|
|
### Tasks
|
|
|
|
1. Summarize selected batch.
|
|
2. Summarize environment handoff.
|
|
3. Summarize evidence package structure.
|
|
4. Identify next bounded execution plan.
|
|
|
|
### Acceptance Criteria
|
|
|
|
1. Report states this is preparation-only.
|
|
2. Report does not claim pseudo-production execution.
|
|
|
|
## Completion Criteria
|
|
|
|
This plan is complete when handoff, evidence checklist, record template, and report are published.
|
|
|
|
## Stop Statement
|
|
|
|
Stop after publishing preparation assets.
|
|
|
|
Do not run pseudo-production execution under this plan.
|
|
|