piyaz
v0.4.13Persistent context network for coding projects. Tracks tasks, dependencies, and decisions across sessions.
By Piyaz188 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 9 skill or MCP entries
- Source updated
- Aug 28, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install plugin
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install piyaz@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/FrkAk/piyazClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/claude-code/.
Plugin files
├── .claude-plugin/plugin.json├── skills/brainstorm/SKILL.md├── skills/composer/SKILL.md├── skills/decompose/SKILL.md├── skills/decompose-feature/SKILL.md├── skills/decompose-task/SKILL.md├── skills/manage/SKILL.md├── skills/onboarding/SKILL.md├── skills/piyaz/SKILL.md└── .mcp.json
Included Skills8
Explicit doorway to the Piyaz brainstorm subagent. Use only when the user types /piyaz:brainstorm directly. For natural-language brainstorm requests (the user describes a net-new project idea), the /piyaz skill or the assistant dispatches the brainstorm agent via the Task tool — do not invoke this skill for that path.
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.
Explicit doorway to the Piyaz decompose subagent. Use only when the user types /piyaz:decompose directly. For natural-language decompose requests (the user asks to break a project description into tasks), the /piyaz skill or the assistant dispatches the decompose agent via the Task tool — do not invoke this skill for that path.
Explicit doorway to the Piyaz decompose-feature subagent. Use only when the user types /piyaz:decompose-feature directly. For natural-language requests to add a new feature or capability cluster to an active project, the /piyaz skill or the assistant dispatches the decompose-feature agent via the Task tool. Do not invoke this skill for that path.
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.
Explicit doorway to the Piyaz manage subagent. Use only when the user types /piyaz:manage directly. For natural-language manage requests (strategic review, graph health audit, rebalancing, deep planning, housekeeping), the /piyaz skill or the assistant dispatches the manage agent via the Task tool — do not invoke this skill for that path.
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.
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.
MCP servers1
- url
- https://app.piyaz.ai/api/mcp
Plugin manifests1
{
"name": "piyaz",
"description": "Persistent context network for coding projects. Tracks tasks, dependencies, and decisions across sessions.",
"version": "0.4.13",
"author": {
"name": "Piyaz"
},
"keywords": [
"project-management",
"task-tracking",
"dependencies",
"context-network"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[piyaz on Agent Plugins Marketplace](https://pluginsmp.com/plugins/piyaz)