dayowe/arcana-codex-plugins
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Default progress requests to lightweight snapshots; preserve explicit deeper-review overrides; release staged-implementation 0.2.0-alpha.5

Browse Source
This commit is contained in:
Dayowe
2026-09-21 11:26:18 +02:00
parent c07be98cfe
commit e8d8199c5f
6 changed files with 19 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/staged-implementation/README.md
+3 -1
View File
@@ -10,7 +10,7 @@ Staged Implementation bundles five skills with two execution entry points:
Use this plugin when a feature or fix is too large or contract-heavy to handle as one open-ended coding pass.
**Experimental preview — `0.2.0-alpha.4`.** Stable `0.1.5` is preserved on `master`. This branch changes Orchestrator's boundary; old whole-checklist launch prompts must explicitly select Coordinator rather than silently losing scope. No installation, migration execution, measured savings or unattended-runtime qualification is implied by the files or structural validators. Qualify the [pilot](skills/coordinator/references/pilot-validation.md) before consequential coordinated execution. Do not mix stable and preview role instructions in one run.
**Experimental preview — `0.2.0-alpha.5`.** Stable `0.1.5` is preserved on `master`. This branch changes Orchestrator's boundary; old whole-checklist launch prompts must explicitly select Coordinator rather than silently losing scope. No installation, migration execution, measured savings or unattended-runtime qualification is implied by the files or structural validators. Qualify the [pilot](skills/coordinator/references/pilot-validation.md) before consequential coordinated execution. Do not mix stable and preview role instructions in one run.
## Plugin Structure
@@ -119,6 +119,8 @@ The usual flow is:
3. Use `validator` when runtime, UI, API, integration, or regression evidence is needed.
4. Use `orchestrator` directly for bounded work, or `coordinator` to continue across a longer checklist with fresh scoped orchestrators.
Ordinary progress questions, such as "progress update" or "how's it going?", default to a brief [progress snapshot](skills/coordinator/references/execution-contract.md#user-requested-progress-snapshots). Each question requests one snapshot from the active orchestrator, reusing an already-pending request for that assignment; if none is active, the coordinator reports the latest known outcome. The orchestrator answers from existing knowledge without cascading worker queries or extra checks. Explicitly ask for investigation, fresh verification or a detailed review to override that default within existing authority; requesting an update does not start periodic reporting.
## Execution Ownership
| Responsibility | Owner |