Skip to content

Moving From GStack Or GSD To ORCA Framework

What This Guide Is For

Use this guide if you started with GStack or GSD patterns and want to understand how ORCA Framework replaces that workflow.

Do not treat ORCA Framework as something you run alongside them. The intended path is to use ORCA Framework itself as the workflow system.

Why ORCA Framework Exists

GStack and GSD helped shape some early ideas:

  • stronger step-by-step execution
  • more explicit workflow structure
  • better task momentum

But ORCA Framework is the clearer replacement:

  • one named framework
  • one command surface
  • one artifact model
  • one docs system
  • one runtime story
  • one place to learn the workflow and keep using it

Replacement Map

  • vague execution habit -> orca-onboard
  • ad hoc task shaping -> orca-spec
  • implicit next steps -> orca-plan
  • raw execution -> orca-build
  • informal "looks fine" -> orca-review

Default ORCA Path

Start here:

  1. orca-onboard
  2. orca-spec
  3. orca-plan
  4. orca-build
  5. orca-review

Common Mistake To Avoid

Do not keep ORCA Framework as a thin wrapper around an older GStack or GSD routine. If you are adopting ORCA Framework, let ORCA own the workflow.

Do not assume ORCA is only the beginner layer before switching to something else. The intent is that ORCA is both the teaching surface and the durable operating surface.