ethanplusai/codex-on-crack / legacy/astra-flash-orchestrator/skill/astra-flash-orchestrator
astra-flash-orchestrator
VerifiedPlan and execute substantial multi-file builds, features, migrations, and refactors with Astra as orchestrator and DeepSeek V4.1 Flash as the native Codex implementation worker. Use for phased planning and delegated build execution, including existing Superpowers or GSD plans. Skip trivial edits and explicitly single-agent tasks. Worker children must not invoke this orchestration skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.9 KB |
| agents/openai.yaml | config | 360 B |
| references/execution.md | markdown | 4.5 KB |
| references/planning.md | markdown | 3.7 KB |
| references/review.md | markdown | 2.6 KB |
| references/routing.md | markdown | 4.3 KB |
| references/sources.md | markdown | 2.7 KB |
| scripts/doctor.py | script | 2.9 KB |
| scripts/local_config.py | script | 12.8 KB |
| scripts/validate_plan.py | script | 7.9 KB |
| templates/checkpoint.md | markdown | 757 B |
| templates/plan.json | config | 628 B |
| templates/spec.md | markdown | 700 B |
| templates/task-brief.md | markdown | 2.0 KB |
| templates/task-report.md | markdown | 1009 B |
references/execution.md
View on GitHub# Execution and workspace ownership
## Default: one native writer, no extra harness
The default is one native Flash child in the current workspace for one coherent
end-to-end phase bundle. Astra supplies the contract, dispatches once, waits, and
reviews one completion report. The worker owns in-scope repository discovery,
implementation, tests, debugging, and routine browser/visual QA. This avoids a
second CLI process, environment-variable command string, automatic commits, and
accidental provider bypass. No `FLASH_WORKER_CMD` or external run_worker.sh is needed.
Before editing, capture the workspace root, current branch/HEAD when Git exists,
tracked/staged diff and untracked-file inventory. Preserve relevant pre-existing
file content in a safe local baseline when it is necessary to distinguish the
worker's changes. Never read or copy secrets just to snapshot the workspace.
Do not auto-stash, reset, commit, or discard user changes. Avoid assigning a file
with actively changing unrelated user edits; a filename list alone cannot recover
those edits. Coordinate a safe baseline or work on an independent scope instead.
Tell the worker what state it should see. With a shared workspace, uncommitted
changes are visible and must be preserved. With a Git worktree made from HEAD,
uncommitted changes from the parent are NOT present. Inspect the resulting files;
do not rely on a statement that contracts were "shared."
Astra does not make overlapping changes while the worker owns paths. The worker
does not mutate shared planning/status files assigned to the coordinator. Give
its task report a unique output path. Do not conflate role instructions with
hard filesystem access controls: inherited host permissions remain authoritative.
## Optional: two genuinely independent writers
Parallelism is opt-in per plan. Use at most two Flash writers by default, and only
when their dependencies are satisfied, writable scopes do not overlap, and
separate workspaces are actually available. A separate agent thread alone does
not satisfy workspace isolation. Shared types, dependency manifests/lockfiles,
routes, migrations, generated outputs, and schema files are usually contention
points; serialize them.
For Git worktrees, Astra establishes a known base and records it PER TASK in the
plan/report, not via shared `git config`. Honor the project's Git permissions.
Do not silently commit a dirty base to make worktree creation convenient. Prepare
local dependencies through the project's approved setup, with test-only data and
no production credentials. A worker must not expand its permissions when setup
fails. Worktrees do not isolate processes, credentials, ports, or network access.
Review and integrate each result before a dependent task starts. Run combined
checks after integration; individually passing branches may conflict. Leave
worktrees/branches available for review unless their removal is authorized and
safe. Do not delete a dirty worktree or unmerged result automatically.
## Handoff, persistence, and correction
Give the task's complete brief and just the relevant shared context. Do not tell
a fresh worker "continue what we discussed" without supplying the decisions.
For a long run, let the child perform internal milestones and test/fix loops.
Require one concise completion report and keep verbose logs in the workspace.
Capture progress at meaningful resumable boundaries, not every tool call. Where a
host turn limit interrupts it, resume the same task with its checkpoint; do not
promise that any model or harness can run indefinitely.
Use native wait/message/continuation functions as actually exposed. Choose the
longest practical wait. Do not use repeated list/status calls as heartbeats, request
play-by-play updates, interrupt a healthy run, or duplicate its repository work.
A wait timeout alone is not a blocker. When a worker is genuinely blocked, Astra
resolves the contract or environment question and sends one targeted update. For
rejected work, batch all concrete findings and send one correction request to the
same child. Default to one correction cycle. Recheck only the affected behavior and
accepted dependencies; broaden further only for a material high-assurance risk.
## Git and production boundaries
No automatic commits, staging, branch merges, pushing, deployment, publishing,
or production migrations are included in this workflow. Execute such operations
only under the user's applicable authorization and after actual review. A build
request by itself is not a reason to edit global router settings mid-project.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |