mirror of
https://github.com/garrytan/gstack.git
synced 2026-08-31 18:30:39 +02:00
Garry TanandClaude Fable 5
848973007c
Reorder the pipeline to CEO -> Design (if UI scope) -> DX (if developer-facing scope) -> Eng. The old order (CEO -> Design -> Eng -> DX) let DX findings land AFTER the required gate signed off, so eng validated a stale plan. Accept-all semantics made explicit: every AskUserQuestion resolves to the recommended option; premises no longer pause the pipeline mid-run (clearly-wrong ones queue as User-Challenge items at the single Final Approval Gate). Eng's Codex voice now sees the DX consensus summary. New free static test pins the order; the chain E2E gains DX-between and Eng-terminal assertions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
39 lines
2.0 KiB
JSON
39 lines
2.0 KiB
JSON
{
|
|
"$schema": "https://gstack.dev/schemas/section-manifest.json",
|
|
"skill": "autoplan",
|
|
"version": 1,
|
|
"note": "PASSIVE registry (v2 plan T9 / CM2). Fields are IDs, file paths, human titles, and human-readable trigger text ONLY. The skeleton's phase sequencing (Sequential Execution + the Phase 0 UI/DX scope detection) is the ONLY place that decides WHEN to read a section — Phase 2 and Phase 2.5 are conditional and their sections must NOT be read when their scope is absent; required-reads live in the E2E fixtures. No machine predicate here — see docs/designs/v2_PLAN.md:663.",
|
|
"sections": [
|
|
{
|
|
"id": "ceo-phase",
|
|
"file": "ceo-phase.md",
|
|
"title": "Phase 1: CEO review (strategy & scope) — override rules, dual voices, required outputs",
|
|
"trigger": "starting Phase 1 (CEO review — always runs, after the Phase 0.5 preflight)"
|
|
},
|
|
{
|
|
"id": "design-phase",
|
|
"file": "design-phase.md",
|
|
"title": "Phase 2: design review — override rules, dual voices, 7-pass checklist",
|
|
"trigger": "starting Phase 2 (design review — ONLY if UI scope was detected in Phase 0; skip the read entirely otherwise)"
|
|
},
|
|
{
|
|
"id": "eng-phase",
|
|
"file": "eng-phase.md",
|
|
"title": "Phase 3: eng review + dual voices — override rules, test review, required outputs",
|
|
"trigger": "starting Phase 3 (eng review — always runs, after the Pre-Phase 3 checklist)"
|
|
},
|
|
{
|
|
"id": "dx-phase",
|
|
"file": "dx-phase.md",
|
|
"title": "Phase 2.5: DX review — override rules, dual voices, 8-dimension scorecard",
|
|
"trigger": "starting Phase 2.5 (DX review — ONLY if developer-facing scope was detected in Phase 0; skip the read entirely otherwise)"
|
|
},
|
|
{
|
|
"id": "tasks-aggregator",
|
|
"file": "tasks-aggregator.md",
|
|
"title": "Phase 4: Implementation Tasks aggregator (builds $AGGREGATED_TASKS for the gate)",
|
|
"trigger": "presenting the Final Approval Gate (Phase 4) — the aggregator computes $AGGREGATED_TASKS that the gate message substitutes"
|
|
}
|
|
]
|
|
}
|