Structured Output
When To Use
- When finalizing any review or analysis.
- To format findings in a consistent way that names specific next steps.
- Before presenting results to stakeholders or committing them to documentation.
When NOT To Use
- Capturing evidence during analysis - use proof-of-work
- Reviewing changes - use diff-analysis or review-core first
Activation Patterns
Trigger Keywords: format, structure, deliverable, report, organize, present, consistent
Contextual Cues:
- "format this as a report" or "structure the output"
- "create a deliverable" or "present these findings"
- "organize this consistently" or "standardize the format"
- "make this actionable" or "prepare for stakeholders"
Auto-Load When: Finalizing any analysis deliverable or when consistent formatting is requested.
Required Progress Items
structured-output:template-selected
structured-output:findings-formatted
structured-output:actions-assigned
structured-output:appendix-attached
Mark each item complete as you finish the corresponding step.
Step 1: Select Template (structured-output:template-selected)
- Choose output format based on deliverable type:
- Review Report: Summary, Findings, Recommendations, Evidence.
- PR Description: Summary, Changes, Test Plan, Notes.
- Release Notes: Highlights, Breaking Changes, Fixes, Credits.
- Incident Report: Timeline, Impact, Root Cause, Remediation.
- Confirm audience and required detail level.
Step 2: Format Findings (structured-output:findings-formatted)
- Use consistent finding structure:
### [SEVERITY] Finding Title
- **Location**: file.rs:123
- **Anchor**: `verbatim source text copied from line 123`
- **Category**: Security | Performance | Correctness | Style
- **Description**: Brief explanation of the issue.
- **Evidence**: [E1, E2] - Reference to evidence log.
- **Recommendation**: Specific remediation steps.
Verification: Run the command with --help flag to verify availability.
- Severity levels: CRITICAL, HIGH, MEDIUM, LOW, INFO.
- Order findings by severity, then by file location.
- Anchor is mandatory and grounds the finding. Copy the exact
source text at
Location (not a paraphrase). It is what a second
pass re-reads to confirm the finding is real. A finding whose anchor
does not appear at its cited line is treated as a hallucination and
dropped. The check is mechanical: imbue:review-core Step 5 runs
plugins/imbue/scripts/citation_verifier.py over the findings.
Step 3: Assign Actions (structured-output:actions-assigned)
- Convert findings to action items with assignee and priority:
## Action Items
- [ ] [HIGH] Fix SQL injection in auth.py:45 (@security-team, P1)
- [ ] [MEDIUM] Add input validation to API endpoint (@backend, P2)
- [ ] [LOW] Update deprecated dependency (@devops, P3)
Verification: Run the command with --help flag to verify availability.
- Include owner assignment where known.
- Add priority indicators (P1/P2/P3) for triage.
- Note dependencies between actions.
Step 4: Attach Appendix (structured-output:appendix-attached)
- Compile supporting materials:
## Appendix
### A. Commands Run
[Full evidence log from imbue:proof-of-work]
### B. External References
[Citations and documentation links]
### C. Raw Data
[Large outputs, full diffs, or data exports]
Verification: Run the command with --help flag to verify availability.
- Keep main report concise; details in appendix.
- validate appendix is navigable with clear section headers.
Output Quality Checklist
Before finalizing:
Exit Criteria
1---2name: structured-output-23description: Formats review deliverables with consistent structure for comparable findings. Use when finalizing any review or analysis that must be shared or compared.4alwaysApply: false5category: output-patterns6tags:7- formatting8- deliverables9- consistency10- reporting11- structure12dependencies:13- imbue:proof-of-work14tools: []15usage_patterns:16- deliverable-formatting17- report-structure18- consistent-output19complexity: beginner20estimated_tokens: 100021metadata:22 source: https://skillmd.com/skills/athola/structured-output-223---2425# Structured Output2627## When To Use28- When finalizing any review or analysis.29- To format findings in a consistent way that names specific next steps.30- Before presenting results to stakeholders or committing them to documentation.3132## When NOT To Use3334- Capturing evidence during analysis - use proof-of-work35- Reviewing changes - use diff-analysis or review-core first3637## Activation Patterns38**Trigger Keywords**: format, structure, deliverable, report, organize, present, consistent39**Contextual Cues**:40- "format this as a report" or "structure the output"41- "create a deliverable" or "present these findings"42- "organize this consistently" or "standardize the format"43- "make this actionable" or "prepare for stakeholders"4445**Auto-Load When**: Finalizing any analysis deliverable or when consistent formatting is requested.4647## Required Progress Items481. `structured-output:template-selected`492. `structured-output:findings-formatted`503. `structured-output:actions-assigned`514. `structured-output:appendix-attached`5253Mark each item complete as you finish the corresponding step.5455## Step 1: Select Template (`structured-output:template-selected`)56- Choose output format based on deliverable type:57 - **Review Report**: Summary, Findings, Recommendations, Evidence.58 - **PR Description**: Summary, Changes, Test Plan, Notes.59 - **Release Notes**: Highlights, Breaking Changes, Fixes, Credits.60 - **Incident Report**: Timeline, Impact, Root Cause, Remediation.61- Confirm audience and required detail level.6263## Step 2: Format Findings (`structured-output:findings-formatted`)64- Use consistent finding structure:65 ```markdown66 ### [SEVERITY] Finding Title67 - **Location**: file.rs:12368 - **Anchor**: `verbatim source text copied from line 123`69 - **Category**: Security | Performance | Correctness | Style70 - **Description**: Brief explanation of the issue.71 - **Evidence**: [E1, E2] - Reference to evidence log.72 - **Recommendation**: Specific remediation steps.73 ```74 **Verification:** Run the command with `--help` flag to verify availability.75- Severity levels: CRITICAL, HIGH, MEDIUM, LOW, INFO.76- Order findings by severity, then by file location.77- **Anchor is mandatory and grounds the finding.** Copy the exact78 source text at `Location` (not a paraphrase). It is what a second79 pass re-reads to confirm the finding is real. A finding whose anchor80 does not appear at its cited line is treated as a hallucination and81 dropped. The check is mechanical: `imbue:review-core` Step 5 runs82 `plugins/imbue/scripts/citation_verifier.py` over the findings.8384## Step 3: Assign Actions (`structured-output:actions-assigned`)85- Convert findings to action items with assignee and priority:86 ```markdown87 ## Action Items88 - [ ] [HIGH] Fix SQL injection in auth.py:45 (@security-team, P1)89 - [ ] [MEDIUM] Add input validation to API endpoint (@backend, P2)90 - [ ] [LOW] Update deprecated dependency (@devops, P3)91 ```92 **Verification:** Run the command with `--help` flag to verify availability.93- Include owner assignment where known.94- Add priority indicators (P1/P2/P3) for triage.95- Note dependencies between actions.9697## Step 4: Attach Appendix (`structured-output:appendix-attached`)98- Compile supporting materials:99 ```markdown100 ## Appendix101 ### A. Commands Run102 [Full evidence log from imbue:proof-of-work]103104 ### B. External References105 [Citations and documentation links]106107 ### C. Raw Data108 [Large outputs, full diffs, or data exports]109 ```110 **Verification:** Run the command with `--help` flag to verify availability.111- Keep main report concise; details in appendix.112- validate appendix is navigable with clear section headers.113114## Output Quality Checklist115Before finalizing:116- [ ] Every finding carries a verbatim `Anchor` the citation verifier117 resolved (no unverified findings ship).118- [ ] All findings have evidence references.119- [ ] Severity levels are justified.120- [ ] Recommendations are specific and name the next step.121- [ ] No orphaned sections or placeholder text.122- [ ] Format renders correctly in target medium (GitHub, Confluence, etc.).123124## Exit Criteria125126- [ ] All `structured-output:` progress items are marked complete127- [ ] The deliverable has every section of the selected template128- [ ] Each finding carries a location and a recommended action