القائمة
Hand off task results between agents. Use when asked to produce a validation, review, test, or implementation report.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | use-reports |
| description | Hand off task results between agents. Use when asked to produce a validation, review, test, or implementation report. |
| metadata | {"version":"0.0.1"} |
Reports are handover artifacts between agents. Start one at the end of your task with:
pst reports write --kind review
Pass --name <slug> when the workspace may hold more than one report of the same kind, for example --name post-merge-review. Pass --template <name> to pick a non-default template.
Edit .pstdio/reports/<name>/report.md directly. Include validation evidence, a Confidence Score from 0/5 to 5/5, and change requests when applicable. Drop supporting artifacts under .pstdio/reports/<name>/files/.
When done, persist your edits:
pst reports save --name <name>
To read another agent's report, open .pstdio/reports/<name>/report.md.
Use pst reports delete --name <name> to discard a draft created by mistake.
Implement a ticket end-to-end. Use when asked to implement or complete a ticket.
Guidance for Prompt Studio and the pstdio CLI for managing project workflows. Covers setup, configuration (.pstdio/config.json), agent configuration, CLI reference, and troubleshooting. Use for "setting up Prompt Studio", "configuring agents", "how does pst work", "what commands are available", or general Prompt Studio questions.
Create or edit a Prompt Studio extension. Use when asked to add or change extension behavior, user actions, automation, project or workspace workflows, templates, skills, custom pages, native resource editors, resource file trees, settings UI, themes, artifact storage, workspace providers, agent providers, or extension validation.
Create a proposal ticket. Use this when asked to write a proposal, introduce changes that add features, large refactors, introduce breaking API or schema changes, modify architecture or design patterns, update security patterns, or to save a plan as proposal. Do not create proposals for bug fixes that restore intended behavior, typos or formatting/comment-only changes, non-breaking dependency updates, configuration-only changes, or tests that validate existing behavior.
Provide additional information to a ticket by researching the codebase and documentation, and/or format a ticket given a template. Use when asked to refine, improve, expand, or format an existing ticket.
Shape controlled Glass Lab artifacts.
