|
| 1 | +name: test_job |
| 2 | +summary: "Exercise the DeepWork quality-gate review system with string and file_path outputs to verify string-output reviews run" |
| 3 | + |
| 4 | +step_arguments: |
| 5 | + - name: report_file |
| 6 | + description: "A short markdown report file produced by the step — exercises the file_path review path." |
| 7 | + type: file_path |
| 8 | + |
| 9 | + - name: summary_text |
| 10 | + description: "A 1-2 sentence narrative summary of the step's work — exercises a string output review defined at the step output-ref level." |
| 11 | + type: string |
| 12 | + |
| 13 | + - name: metrics_text |
| 14 | + description: "A concise metrics blurb containing at least one numeric value — exercises a string output review defined at the step_argument level (inherited by any step that outputs it)." |
| 15 | + type: string |
| 16 | + review: |
| 17 | + strategy: individual |
| 18 | + instructions: | |
| 19 | + Verify the value is a concise metrics summary of 1-3 sentences that contains at |
| 20 | + least one numeric value. Flag it if the value is empty, a placeholder, or does |
| 21 | + not mention any numbers. |
| 22 | +
|
| 23 | + - name: notes_text |
| 24 | + description: "A freeform notes string with no review attached — control case that should produce no review task." |
| 25 | + type: string |
| 26 | + |
| 27 | +workflows: |
| 28 | + test_review_system: |
| 29 | + summary: "Produce four outputs of mixed types and review levels to verify the quality gate reviews them correctly." |
| 30 | + common_job_info_provided_to_all_steps_at_runtime: | |
| 31 | + This bespoke test job verifies that the DeepWork quality-gate review system |
| 32 | + executes reviews on string outputs as well as file_path outputs. Four outputs are |
| 33 | + produced in a single step, each hitting a distinct review code path. The control |
| 34 | + case (notes_text) must NOT produce a review task. |
| 35 | + steps: |
| 36 | + - name: produce_outputs |
| 37 | + instructions: | |
| 38 | + # Produce test outputs for the quality gate |
| 39 | +
|
| 40 | + Create each of the four outputs below, then call `finished_step` with all four |
| 41 | + values. Keep the content short. |
| 42 | +
|
| 43 | + 1. **report_file**: write a small markdown file at |
| 44 | + `.deepwork/jobs/test_job/fixtures/report.md` (create the parent directory |
| 45 | + first if needed). Two or three lines — a heading plus a sentence is fine. |
| 46 | +
|
| 47 | + 2. **summary_text**: a 1-2 sentence narrative summary describing the work |
| 48 | + performed in this step. |
| 49 | +
|
| 50 | + 3. **metrics_text**: a 1-3 sentence metrics blurb that includes at least one |
| 51 | + number (e.g., "Produced 4 outputs, 3 reviewed, in under 1 second."). |
| 52 | +
|
| 53 | + 4. **notes_text**: any freeform string — this one has no review attached. |
| 54 | +
|
| 55 | + Expected quality-gate result: three review tasks (one per output that has a |
| 56 | + review configured). `notes_text` should not produce a review task. |
| 57 | + outputs: |
| 58 | + report_file: |
| 59 | + review: |
| 60 | + strategy: individual |
| 61 | + instructions: | |
| 62 | + Verify the file is a valid markdown document with a recognisable heading |
| 63 | + or non-empty first line. Flag it if the file is empty or contains no |
| 64 | + markdown structure. |
| 65 | + summary_text: |
| 66 | + review: |
| 67 | + strategy: individual |
| 68 | + instructions: | |
| 69 | + Verify the value is a non-empty narrative summary of 1-2 sentences |
| 70 | + written in plain English that describes some concrete outcome of the |
| 71 | + step. Flag it if the value is empty, a placeholder, or does not describe |
| 72 | + anything. |
| 73 | + metrics_text: {} |
| 74 | + notes_text: {} |
0 commit comments