moraine-start-worklisted

# Moraine Start Work ## Overview Use this workflow to start a Moraine contributor task with the same orientation every time: verify the checkout, isolate the branch, read governing instructions, and choose the right validation path before editing. Using `$moraine-dev:code-review` in Codex or `/code-review` in Kiro is an explicit user request for delegated reviewer subagents. You have permission to launch that review wave when the follow-on workflow reaches that step. ## Harness Invocation Use the invocation form native to the current harness: | Workflow | Codex | Kiro | | --- | --- | --- | | `crystallize` | `$moraine-dev:crystallize` | `/crystallize` | | `code-review` | `$moraine-dev:code-review` | `/code-review` | | `moraine-sandbox-qa` | `$moraine-dev:moraine-sandbox-qa` | `/moraine-sandbox-qa` | | `moraine-author-pr` | `$moraine-dev:moraine-author-pr` | `/moraine-author-pr` | ## Follow-On Workflow After the start checklist and branch/worktree setup, run the rest of the contributor workflow in this order: 1. Use the current harness's `crystallize` invocation to turn rough or ambiguous input into a ready-to-implement local plan. 2. Implement the scoped change from that plan or, when the task is already concrete, from the user's explicit request. 3. Use the current harness's `code-review` invocation and iterate fixes until the review is clean or every remaining item is explicitly rejected or deferred with rationale. 4. Use the current harness's `moraine-sandbox-qa` i