2.1 KiB
2.1 KiB
Orch Markdown Test Plan Skeleton
Status
completed
Owner
- codex
Started At
2026-03-19
Goal
- create an inbox-style human-readable Markdown test-plan skeleton for
orchso future agents can add command and workflow cases without rediscovering the documentation structure
Scope
- add
docs/tests/orch/README.mdanddocs/tests/orch/ROADMAP.md - add shared and workflow entrypoint documents under
docs/tests/orch/ - add one directory per
orchleaf command with an indexREADME.md - update the implementation roadmap and archive this execution roadmap when complete
Checklist
- read the existing inbox Markdown test-plan roadmap and directory conventions
- define the
orchleaf-command directory model - add the
docs/tests/orch/skeleton files and per-command indexes - update
docs/implementation-roadmap.md - archive this roadmap with a completion summary
Files
docs/roadmaps/archive/orch-markdown-test-plan-skeleton.mddocs/implementation-roadmap.mddocs/tests/orch/README.mddocs/tests/orch/ROADMAP.mddocs/tests/orch/_shared/README.mddocs/tests/orch/workflows/README.md
Decisions
- mirror the inbox test-plan structure at the directory and index level, but model
orchby leaf commands rather than command groups - seed the new roadmap with a concrete pending-case backlog derived from existing
internal/cli/orch/integration_test.gocoverage so later authoring can proceed without rediscovery
Blockers
- none
Next Step
- start writing the highest-value
orchcase documents from the new backlog, beginning with the happy-path scheduler workflow and strict worktree dispatch cases
Completion Summary
- created
docs/tests/orch/with a top-levelREADME.md,ROADMAP.md, shared conventions, workflow entrypoint, and one indexREADME.mdper implemented leaf command - documented the initial
orchMarkdown test-plan model as leaf-command directories instead of command groups - updated the project implementation roadmap so future agents can discover the new
orchtest-plan skeleton from the main handoff document