corgispec-propose

To generate a complete engineering proposal, use a one-step workflow that derives a change name from configuration and iteratively produces specs, design, and task artifacts in the correct dependency order. This packages the full planning set for immediate review and handoff.

Worktree isolation works by creating an isolated git worktree and recording its location in a `.worktree.yaml` metadata file. This ensures later implementation phases operate in the correct, separated environment without affecting the main branch.

Yes, you can create GitLab issues automatically from a proposal when GitLab tooling is available. The workflow generates parent and child issues, then writes a canonical `.gitlab.yaml` handoff contract to close the tracking loop if state does not already exist.

The best way to ensure correct artifact generation order is to use a deterministic dependency flow that iteratively checks `applyRequires` outputs. This mechanism produces required specs, design, and task documents sequentially until all outputs are complete.

Yes, you need to read corgispec/openespec configuration to generate task planning artifacts. The workflow requires this configuration to derive the change name and enforce constraints that prevent embedding context or rules blocks into the final outputs.

The generation process enforces constraints that strictly prevent embedding context or rules blocks into the final specs and design outputs. This ensures the planning artifacts remain clean, reviewable, and free of extraneous pipeline instructions.