dev-flow
v0.7.0Conductor for the dev pipeline: detects a task's tier (bug / feature / architecture / client), prints the exact chain of sub-skills it will run and skip with reasons, confirms, then drives them in order. Matches ceremony to stakes.
By Matheus MalagrisLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 24, 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 dev-flow for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dev-flow-2@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/mqmalagris/agent-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is skills/dev-flow/.
Plugin files
├── .claude-plugin/plugin.json└── SKILL.md
Included Skills1
Route a dev task through the right subset of the canonical skill chain (adhd → grill-me → to-prd → compass → blueprint → code → review-pass → pr-craft), matching ceremony to stakes. Detects the task tier (bug / feature / architecture / design / client), shows the exact chain it will run and what it skips, confirms, then drives the sub-skills in order — pausing where each needs user input. Use when the user says "start a feature", "new feature", "kickoff", "route this through the workflow", "run the chain", "which skills for this", "design this but do not build it", "spec it out, no code", or /dev-flow. NOT for tasks already mid-chain (a PRD/plan exists) — invoke the specific next skill instead.
Plugin manifests1
{
"name": "dev-flow",
"version": "0.7.0",
"description": "Conductor for the dev pipeline: detects a task's tier (bug / feature / architecture / client), prints the exact chain of sub-skills it will run and skip with reasons, confirms, then drives them in order. Matches ceremony to stakes.",
"author": {
"name": "Matheus Malagris",
"url": "https://github.com/mqmalagris"
},
"homepage": "https://github.com/mqmalagris/agent-skills/tree/main/skills/dev-flow",
"repository": "https://github.com/mqmalagris/agent-skills",
"license": "MIT",
"keywords": [
"workflow-orchestration",
"dev-chain",
"task-routing",
"worktree",
"skill-conductor",
"engineering-workflow"
]
}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.
[dev-flow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dev-flow-2)