ticket-plan

name

ticket-plan

description

P-phase skill for the ticket-writing workflow. Plans HOW to fill the ticket sections defined by ticket-structure: writing order, per-section subagent dispatch (for sections requiring fresh research), review checkpoints (where to pause for user review during writing — especially Part boundaries for heavy tickets). Reads the Structure Outline; produces a Writing Plan section in the ticket body that ticket-write consumes. P is tactical: sequence, dispatch, and pause points — not content.

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 P-phase of the ticket-writing QRDSPIV: plan HOW to fill the sections that ticket-structure outlined. Per QRDSPIV §P: "P takes the structure from S and makes it tactical: sequencing, dependencies, effort estimates, decision points." At the ticket-writing layer, P plans the WRITING of the ticket itself — not the implementation of the feature.

<output>
  A Writing Plan section in the ticket body containing:
  - Section writing order (which to draft first, which depend on others)
  - Per-section subagent dispatch (for sections that need additional
    research to fill — typically when a section's scope note
    requires evidence not yet in the research file)
  - Review checkpoints (where to pause during ticket-write for
    user review — especially at Part boundaries for heavy tickets)
  - Per-section length estimates (rough guidance; ticket-write
    treats these as targets, not hard limits)

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

<key-responsibility>
  The Writing Plan is the schedule for ticket-write. It exists
  because:
  - Some sections need fresh research before they can be written
    (e.g., "Acceptance Criteria" may need codebase pattern-finder
    dispatched to find test conventions)
  - Heavy tickets cannot be written end-to-end without pause
    points; the user reviews after each Part
  - Some sections depend on others (e.g., "Out of Scope" reads
    cleanest after the main behavior sections are drafted; the
    scope contrast is more visible)

  Per spec §3, this is a soft transition from S to P (no firm
  checkpoint), but the Plan itself is presented to the user once
  drafted — they confirm before ticket-write begins.
</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, Design, Structure sections),
    research, questions, linked DRs. The Structure Outline is
    the primary input — every section in the outline gets a
    plan entry.
  </note>
</step>

<step n="2" title="Draft Writing Plan">
  <action>Load and execute: references/steps/step-02-draft-plan.xml</action>
  <note>
    For each section: assign writing order, identify whether
    subagent dispatch is needed for content, estimate length.
    Define review checkpoints (typically at Part boundaries
    for heavy tickets).
  </note>
</step>

<step n="3" title="Align with User">
  <action>Load and execute: references/steps/step-03-align.xml</action>
  <note>
    Present the Writing Plan. Lighter checkpoint than D-phase
    or S-phase (P is tactical, not foundational), but still get
    explicit confirmation before ticket-write begins.
  </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 Writing Plan to ticket body, stamp last_updated,
    re-validate, recommend ticket-write.
  </note>
</step>

After step 4, present: 1. The Writing Plan 2. Bundle file paths 3. Estimated total ticket length (sum of per-section estimates) 4. Next action: invoke `ticket-write` from the ticketsmith menu (cmd: TW) to begin drafting the ticket per this plan.