onboarding

Estrellas120

Forks8

Actualizado17 de junio de 2026 a las 01:48

Explicit doorway to the Piyaz onboarding subagent. Use only when the user types /piyaz:onboarding directly. For natural-language onboarding requests (the user asks to import an existing repo into Piyaz), the /piyaz skill or the assistant dispatches the onboarding agent via the Task tool — do not invoke this skill for that path.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

FrkAk

FrkAk/piyaz

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas·SOC 15-1299

SKILL.md

readonly

name	onboarding
description	Explicit doorway to the Piyaz onboarding subagent. Use only when the user types /piyaz:onboarding directly. For natural-language onboarding requests (the user asks to import an existing repo into Piyaz), the /piyaz skill or the assistant dispatches the onboarding agent via the Task tool — do not invoke this skill for that path.

Dispatch the onboarding subagent via the Task tool with subagent_type: "onboarding". Pass the user's full request as the prompt. The canonical workflow lives in the agent definition; do not duplicate it here.

Más de este repositorio

mismo repositorio

piyaz

FrkAk/piyaz

Use when the user wants to plan, decompose, track, or resume a multi-task project: scoping a new idea, importing or onboarding an existing repo or workspace, asking what to work on / what's next / what's blocked / where they left off, reporting task completion, dispatching work in parallel, or planning a draft task. Also when the user mentions Piyaz by name (e.g. "piyaz, do X") or references a task by its ref (e.g. VLT-9, KRN-153, PXD-31). Works for any project domain (code or data). Do not invoke for: one-off coding questions, single-file edits, debugging a specific error, generic todos, or scheduling.

2026-07-14120

review

FrkAk/piyaz

Dispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's `in_review` write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N", "review this PR", "review <PR URL>"). Reads `piyaz_get lens='review'` for the implementationPlan rendered alongside executionRecord, AC evaluation against executionRecord excerpts, downstream impact, and the PR handle from `task.links` filtered to `kind='pull_request'`; the PR diff is the source of truth for what changed, and tasks that ship deliverables instead of a PR are reviewed through their linked artifacts. Returns one of `approve`, `request-changes`, or `block` with file-cited reasoning across the security, performance, reliability, observability, and codebase standards lenses. Never auto-flips status; HOTL owns the `in_review` to `done` transition. Do not use for refinement, draft / pl

2026-07-14120

composer

FrkAk/piyaz

Use when the user types /piyaz:composer, /piyaz:composer <taskRef>, or /piyaz:composer rework <taskRef|pr-url>, or asks to run the next Piyaz task end-to-end, ship the backlog, compose through the ready queue, or loop through Piyaz tasks until done. Composer researches, refines, plans, implements, reviews, and fixes each task in a loop until the PR is ready, and merges and continues when the user authorizes it. Do NOT invoke for one-off task lookups, status checks, hand-refinement of one task, or interactive planning of a single task; those flows belong to the piyaz skill and composer adds latency without adding quality.