decompose-task

Sterne121

Forks8

Aktualisiert17. Juni 2026 um 01:48

Explicit doorway to the Piyaz decompose-task subagent. Use only when the user types /piyaz:decompose-task directly. For natural-language requests to split an existing oversize task (the user says "split this task" or composer's oversize handler routes here), the /piyaz skill or the assistant dispatches the decompose-task agent via the Task tool. Do not invoke this skill for that path.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

FrkAk

FrkAk/piyaz

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige ComputerberufeInformatik- und Mathematikberufe·SOC 15-1299

SKILL.md

readonly

name	decompose-task
description	Explicit doorway to the Piyaz decompose-task subagent. Use only when the user types /piyaz:decompose-task directly. For natural-language requests to split an existing oversize task (the user says "split this task" or composer's oversize handler routes here), the /piyaz skill or the assistant dispatches the decompose-task agent via the Task tool. Do not invoke this skill for that path.

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

Mehr aus diesem Repository

gleiches Repository

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-14121

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-14121

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.