Menu
Implement a ticket end-to-end. Use when asked to implement or complete a ticket.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
Hand off task results between agents. Use when asked to produce a validation, review, test, or implementation report.
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.
| name | implement-ticket |
| description | Implement a ticket end-to-end. Use when asked to implement or complete a ticket. |
| metadata | {"version":"0.0.6"} |
Implement planner tickets inside a workspace (a git worktree). Progress is reported by this session itself: ticket movement is derived from live session state, not from a stored workspace status.
PS-12). Pass it to --id — commands resolve it. If the ticket is missing or ambiguous, ask the user to confirm it.
pst tickets list --status <ready-status> (see pst statuses list for the project's status names).pst tickets view --id <shorthand>.pst tickets update --status during or after implementation — ticket transitions are derived from session state.pst tickets link-review --id <shorthand> --url <review-url>.To be review-ready a ticket must produce verifiable outputs generated while doing the work. Capture them in a workspace report so reviewers can inspect the proof alongside the implementation:
pst reports write --kind validation --name implementation..pstdio/reports/implementation/files/..pstdio/reports/implementation/report.md.pst reports save --name implementation.Report evidence includes:
curl responsesArtifacts must be concrete, inspectable, and reproducible.