name: code-orient
description: "Entry-point skill for the codesmith implementation workflow. Detects dual mode (planning vs execution) from initial input shape — ticket reference → planning mode; bundle directory → execution mode. In planning mode: loads the status: ready ticket, scaffolds the implementation bundle via scaffold-implementation-bundle.py, transitions ticket status ready → active, and hands off to code-grill. In execution mode: loads the existing bundle (ticket + design + structure + plans + optional research), confirms preconditions, and hands off to code-implement. Detects PR mode vs local-only mode based on remote configuration and user confirmation."
<substep n="1a" title="Track Progress">
<action if="first iteration">Create todo list from all instruction step titles (TodoWrite)</action>
<action>Mark current step as in_progress (TodoWrite)</action>
</substep>
<substep n="1b" title="Handle Step Attributes">
<check>If optional="true" and NOT YOLO -> Use Question tool to ask user whether to include (Yes/Skip)</check>
<check>If if="condition" -> Evaluate condition</check>
<check>If for-each="item" -> Repeat step for each item</check>
<check>If repeat="n" -> Repeat step n times</check>
</substep>
<substep n="1c" title="Execute Step Content">
<action>Process step instructions (markdown or XML tags)</action>
<action>Replace {{variables}} with values (ask user if unknown)</action>
<execute-tags>
<tag>action -> Perform the action</tag>
<tag>action type="script" -> Execute as shell command, capture output</tag>
<tag>check if="condition" -> Conditional block wrapping actions (requires closing </check>)</tag>
<tag>ask -> Prompt user using Question tool and WAIT for response. When options exist, present them as selectable choices. For open-ended questions, provide helpful suggested options with custom input enabled</tag>
<tag>invoke-skill name="skill-name" -> Execute another skill via OpenCode skill system</tag>
<tag>invoke-agent name="subagent" prompt="task" -> Delegate to subagent via Task tool</tag>
<tag>goto step="x" -> Jump to specified step (used for explicit loop-back in Q-R style flows)</tag>
</execute-tags>
</substep>
<substep n="1d" title="Handle template-output Tags">
<if tag="template-output">
<mandate>Generate content for this section</mandate>
<mandate>Save to file (Write first time, Edit subsequent)</mandate>
<action>Display generated content</action>
<action>Use Question tool to present checkpoint options. WAIT for response.
<options>
<option label="Continue" description="Approve this section and move to the next step" />
<option label="Advanced Elicitation" description="Explore this section deeper before proceeding" />
<option label="YOLO" description="Auto-complete the rest of this workflow without stopping" />
</options>
<if response="Advanced Elicitation">
<action>Invoke advanced-elicitation skill</action>
</if>
<if response="Continue">
<action>Continue to next step</action>
</if>
<if response="YOLO">
<action>Enter YOLO mode for the rest of the workflow</action>
</if>
</action>
</if>
</substep>
<substep n="1e" title="Step Completion">
<action>Mark current step as completed (TodoWrite)</action>
<check>If no special tags and NOT YOLO:</check>
<action>Use Question tool to ask:
<options>
<option label="Continue" description="Proceed to the next step" />
<option label="Edit" description="Revise this step before moving on" />
</options>
</action>
</substep>
</step>
<step n="2" title="Completion">
<check>Confirm all instruction steps have been executed</check>
<output>Workflow complete.</output>
</step>
<inputs>
ONE of:
- ticket_input: path or alias of a `status: ready` ticket
→ PLANNING MODE (Lock 20 first session)
- bundle_input: path to an existing implementation bundle dir
→ EXECUTION MODE (Lock 20 second session, post-compact)
</inputs>
<outputs>
Session state populated with:
- mode: planning | execution
- bundle_dir, ticket_path, ticket_alias, ticket_slug, primary_tag
- design_path (planning mode: scaffolded; execution mode: existing)
- structure_path, plan_paths[], research_path (execution mode only)
- pr_mode: true | false (PR cycle applies later)
- base_branch (from thoughts metadata or git origin/HEAD)
Then dispatches the next skill:
- planning mode → code-grill (Q↔R loop begins)
- execution mode → code-implement (orchestration begins)
</outputs>
<step n="1" title="Detect Mode">
<action>Load and execute: references/steps/step-01-detect-mode.xml</action>
</step>
<step n="2" title="Load Bundle Context">
<action>Load and execute: references/steps/step-02-load-bundle.xml</action>
</step>
<step n="3" title="Verify Preconditions">
<action>Load and execute: references/steps/step-03-verify-preconditions.xml</action>
</step>
<step n="4" title="Detect PR Mode" if="mode == 'planning'">
<action>Load and execute: references/steps/step-04-detect-pr-mode.xml</action>
</step>
<step n="5" title="Scaffold Bundle (planning mode)" if="mode == 'planning'">
<action>Load and execute: references/steps/step-05-scaffold-bundle.xml</action>
</step>
<step n="6" title="Transition Ticket Status (planning mode)" if="mode == 'planning'">
<action>Load and execute: references/steps/step-06-transition-status.xml</action>
</step>
<step n="7" title="Handoff">
<action>Load and execute: references/steps/step-07-handoff.xml</action>
</step>