Agent
Use when the user has a net-new software project idea that needs shaping into a brief before tasks can be created. Triggers: "I want to build...", "I'm thinking about an app for...", "let's plan a project", vague or exploratory phrasing, ambiguous scope. Do not use when an existing repo is present (route to…
Agent
Phase 3 of the /piyaz:composer pipeline. Dispatched per task by the composer orchestrator after the planner has saved the implementationPlan to Piyaz. Reads the plan, implements it on a feature branch with production-grade quality (security, performance, reliability, observability), runs the project's tests /…
Agent
Phase 2 of the /piyaz:composer pipeline. Takes a research brief plus the target task's planning context, writes the unabridged implementationPlan to Piyaz, and transitions the task draft → planned in the same update. Fills refinement gaps the researcher missed via append-only updates. Returns a one-sentence…
Agent
Phase 1 of the /piyaz:composer pipeline. Dispatched per task by the composer orchestrator to gather grounded context before planning. Reads the target task at multiple Piyaz context depths, searches up-to-date library docs via context7, explores the codebase for files and patterns the implementer will touch, surfaces…
Agent
Use when the user wants to add a new feature, capability, or cluster of work to an existing active Piyaz project. Triggers: "add a feature for notifications", "decompose this idea into tasks", "I want to plan out the X subsystem", "extend the project with Y", "add Z to the project". Reuses the project's existing…
Agent
Use when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the oversize-task flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break into smaller pieces"). Composer dispatches this from its…
Agent
Use when a Piyaz project exists with a description but few or no tasks, and the user wants it broken into an implementable graph (project-level decomposition). Triggers: "decompose", "break this down", "create tasks", "turn this into tasks", "give me a task list", "plan out the work", "how should I build this". Do not…
Agent
Use when the user explicitly wants a deep CTO-mode review of a Piyaz project. Triggers: "strategic review", "audit the project", "rebalance the graph", "what's the health of this project", "deep dive on the dependency graph", "I want a thorough navigation session", "prune orphans", "connect missing edges", "audit…
Agent
Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists…
Agent
Dispatched after a task lands at inreview 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 inreview write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N"…