ticket-structure

name

ticket-structure

description

S-phase skill for the ticket-writing workflow. Designs the TICKET ITSELF — sections, numbered Parts for heavy tickets, custom outline for unusual ones. Tag recipe drives the default shape (when Phase 4 references are in place); custom outline applies when the recipe doesn't fit. Reads the Design Summary from ticket-design; produces a Structure Outline section in the ticket body that ticket-plan and ticket-write will consume. Per QRDSPIV §S: 'scope, don't prescribe' — the outline names sections, it doesn't fill them.

Execute workflow by following instructions and producing output Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown Execute ALL steps in instructions IN EXACT ORDER Save to template output file after EVERY "template-output" tag NEVER skip a step - YOU are responsible for every step's execution without fail or excuse Steps execute in exact numerical order (1, 2, 3...) unless an explicit goto directs otherwise Optional steps: Ask user unless YOLO mode active Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the user indicates to proceed (unless YOLO mode has been activated) For each step in instructions:

  <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 &lt;/check&gt;)</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>

Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except YOLO mode Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by simulating the remaining discussions with a simulated expert user step n="X" goal="..." - Define step with number and goal substep n="Xa" title="..." - Sub-step within a step phase n="X" - Phase within a substep optional="true" - Step can be skipped if="condition" - Conditional execution for-each="collection" - Iterate over items repeat="n" - Repeat n times action - Required action to perform action type="script" - Execute shell command action if="condition" - Single conditional action (inline, no closing tag needed) check if="condition">...</check> - Conditional block wrapping multiple items (closing tag required) ask - Get user input via Question tool (ALWAYS wait for response before continuing). Present defined options as selectable choices. For open-ended questions, offer helpful suggestions with custom input enabled goto - Jump to another step (explicit loop-back) invoke-skill - Call another skill invoke-agent - Delegate to subagent via Task tool invoke-protocol - Execute a reusable protocol (e.g., discover_inputs) template-output - Save content checkpoint critical - Cannot be skipped example - Show example output note - Informational content output - Display to user without saving halt-conditions - Define conditions that MUST stop execution condition - Single halt condition validation - Pre-condition rules to check - This is the complete workflow execution engine - You MUST follow instructions exactly as written - This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context - YOU ARE FACILITATING A CONVERSATION with a user to produce a final document step by step - The whole process is meant to be collaborative - helping the user flesh out their ideas - Do not rush or optimize and skip any section Run the S-phase of the ticket-writing QRDSPIV: design the ticket ITSELF. Tag recipe drives the default shape (sections, numbered Parts for heavy tickets); when the recipe doesn't fit, the agent proposes a custom outline. Per QRDSPIV §S: "S = scope, not prescribe — at ticket-writing layer." The outline names sections; ticket-write fills them.

<output>
  A Structure Outline section written into the ticket body containing:
  - The ticket's section list (level-2 headings in writing order)
  - For heavy tickets (per spec §2.3): numbered Parts that group
    sections for section-batched review
  - Per-section notes on what the section covers (one or two lines
    each — not the section content, just its scope)
  - Any custom outline decisions (which recipe sections were
    omitted, which were added)

  Bundle state after this skill: ready for ticket-plan.
</output>

<key-responsibility>
  In this harness, tickets are heavy (per spec §2.3 / Lock 1): they
  absorb PRD-and-Spec weight because Brief and Spec layers don't
  exist yet. Consequence: tickets often have 400-1500+ lines and
  numbered Parts. The Structure phase decides:

  - Which recipe-mandated sections this specific ticket needs
  - Whether numbered Parts are warranted (typically when the
    ticket exceeds ~600 lines or has >2 distinct concern areas)
  - The section ORDER (writing order will likely follow this; some
    sections may be batched in ticket-plan's review checkpoints)
  - Any sections the recipe does NOT include but this ticket
    needs (custom additions)
  - Any recipe sections this ticket does NOT need (custom omissions)

  The agent must keep "scope, don't prescribe" in mind: the outline
  describes WHAT sections exist and what each one is for; the
  content of those sections is ticket-write's job.
</key-responsibility>

<step n="1" title="Load Bundle">
  <action>Load and execute: references/steps/step-01-load-bundle.xml</action>
  <note>
    Read the ticket (Readiness Summary + Design Summary), research
    file, questions file, linked DRs. The Design Summary's
    artifact-chain shape informs the outline.
  </note>
</step>

<step n="2" title="Select Shape (Recipe or Custom)">
  <action>Load and execute: references/steps/step-02-select-shape.xml</action>
  <note>
    Load the tag recipe for the primary tag (when Phase 4 references
    exist). If the recipe fits, use it. If the ticket's nature
    deviates significantly from the recipe's assumptions, design a
    custom outline. Decide whether numbered Parts apply.
  </note>
</step>

<step n="3" title="Draft and Align" critical="true">
  <action>Load and execute: references/steps/step-03-draft-and-align.xml</action>
  <note>
    Compose the Structure Outline draft. Present to user via firm
    checkpoint. User confirms or adjusts; loop on adjustments
    until aligned.
  </note>
</step>

<step n="4" title="Finalize and Handoff">
  <action>Load and execute: references/steps/step-04-finalize-and-handoff.xml</action>
  <note>
    Write the Structure Outline into the ticket body, stamp
    last_updated, re-validate, present handoff to ticket-plan.
  </note>
</step>

After step 4, the ticket body has a Structure Outline section describing the writing target. Present: 1. The Structure Outline 2. Bundle file paths 3. Whether the outline came from a tag recipe or was custom 4. Next action: invoke `ticket-plan` from the ticketsmith menu (cmd: TP) to plan how to fill these sections.