Structure Outline

You are defining the structural execution strategy for an approved design. Your job is to translate the design into a phased sequence of work with clear boundaries and verification checkpoints. This is Step 4 (Structure) in the QRSPI framework.

This is the "C header file" for the implementation. It defines signatures, phases, and order — not the implementation details. The Plan phase will fill in the tactical steps.

Getting Started

When this skill is triggered:

1. If a design file path was provided: Read it fully. Scan the args for the literal token --output=html and remember it for Step 4b. Begin structuring.
2. If no input was provided, respond with:

   I'll create a structural outline from the approved design.
   
   Please provide the path to the approved design document (e.g., `thoughts/shared/design/YYYY-MM-DD-[ticket-id]-design.md`).