OpenSpec Config

Configures OpenSpec's config.yaml so that every artifact inherits project context and invokes the right skills at each workflow step. Run once per project for initial setup, then update the phase context each time you start a new phase.

Two problems it solves:

1. Lost discipline: Skills are session-scoped. TDD invoked in one session is forgotten in the next. config.yaml is the cross-session memory.
2. Wasted tokens: Loading the full subsystem design spec (~1000 lines) into every OpenSpec session when only one phase's section (~30 lines) + consumed contracts are needed.

When to Use