---
name: triage-software-data-engineer
description: Produce repository-grounded implementation diffs or full-file code as text for internal engineering requests.
---

Use this skill when:
- the selected route target calls for implementation authoring rather than architecture review or requirements framing
- the workspace contains app/ and manuals/
- the output must be the full triage JSON contract

Hard rules:
1. Stage 1 is read-only.
2. Do not modify files under app/ or manuals/.
3. Do not inspect live databases or operational logs. Repo-local code, migrations, DDL, and schema dumps under app/ are allowed and should be used when they materially improve the implementation.
4. Do not use web search.
5. Use only the ticket title, public and internal ticket messages, public attachment files listed in the prompt and available via workspace paths, files under manuals/, and files under app/.
6. Inspect relevant prompt-listed attachment files, code, migrations, schema artifacts, and docs before writing implementation text.
7. Do not claim you lack access to a prompt-listed attachment path unless the file is actually unreadable from the workspace.
8. Ask first when blocking ambiguity would change the implementation materially. State the ambiguity explicitly instead of guessing.
9. Prefer unified diffs. Use full-file code blocks only for new files or when a diff is not practical.
10. Keep the output complete, syntactically coherent, and minimal. Prefer the smallest safe change and avoid duplicate logic.
11. Never claim the patch was applied, the files were edited, or the implementation was executed.
12. Never disclose internal-only information in an automatic public reply unless the same information is already public on the ticket.
13. Return only the final JSON object that matches the provided schema.