torch-request-skills

Capture a PyTorch build-deliverable request (build or sub-version build). Asks clarifying questions, then produces a structured artifact with YAML frontmatter. Use when a consumer needs a new build target.

Validate a PyTorch build-deliverable request — a definition-of-ready check. Confirms the request is complete, well-formed, and internally coherent, then writes a review file. Run after /torch.build.create or against an existing AIPCC- key.

Submit reviewed PyTorch build-deliverable requests to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.build.review when status is Ready.

Validate an internal ask — a definition-of-ready check. Confirms the request is complete, well-formed, internally coherent, and carries the governance signal (named approver + approval status) submission requires, then writes a review file.

Capture a team ask — a cross-cutting request, a dispute, or an unblock-model-validation escalation routed to the architect for prioritization. Asks clarifying questions, then produces a structured artifact with YAML frontmatter.

Validate a team ask — a definition-of-ready check. Confirms the request is complete, well-formed, internally coherent, and carries the technical context the architect needs to route it, then writes a review file.

Submit reviewed team asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.team.review when status is Ready.

Capture an internal ask — a request from another AIPCC team or a PyTorch working group, including RFC handoffs and backports. Asks clarifying questions, then produces a structured artifact with YAML frontmatter.

Submit reviewed internal asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.internal.review when status is Ready.

Capture an external ask — a PyTorch version/hardware/accelerator request originating outside AIPCC (field report, customer escalation, partner-driven). Asks clarifying questions, then produces a structured artifact with YAML frontmatter.

Validate an external ask — a definition-of-ready check. Confirms the request is complete, well-formed, internally coherent, and carries the stricter intake an external ask requires, then writes a review file.

Submit reviewed external asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.external.review when status is Ready.