From devflow
Discovers all DevFlow plugin primitives — skills, agents, hooks, and commands — with descriptions and entry points for each workflow. Use this when the user asks things like "what does DevFlow include," "list all skills," "show me available commands," "what agents are available," or "give me an overview of the plugin."
npx claudepluginhub joshuarweaver/cascade-code-general-misc-4 --plugin codingthefuturewithai-claude-code-primitivesThis skill is limited to using the following tools:
**Say exactly:** "SKILL INVOKED: devflow:plugin-overview"
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Say exactly: "SKILL INVOKED: devflow:plugin-overview"
Request: $ARGUMENTS
Discover all primitives installed in ${CLAUDE_PLUGIN_ROOT} and present them to the user. If $ARGUMENTS specifies a filter, show only that section.
Each subdirectory of ${CLAUDE_PLUGIN_ROOT}/skills/ that contains a SKILL.md is a skill. Read the YAML frontmatter of each SKILL.md to extract name and description.
Categorize each skill by its directory name prefix:
| Directory prefix | Category key | Display heading |
|---|---|---|
| build | build | Build Workflow (Issue → PR/MR) |
| pm | pm | Project Management (Upstream SDLC) |
| foundation | foundation | Foundation (Team Standards & Config) |
| docs | docs | Documentation |
| rag-memory | rag-memory | RAG Memory |
| devops | devops | DevOps |
| (no prefix match) | setup-utilities | Setup & Utilities |
Every non-hidden file in ${CLAUDE_PLUGIN_ROOT}/agents/ is an agent definition (markdown with YAML frontmatter — may or may not have .md extension). Read the frontmatter to extract name, description, model, and tools.
${CLAUDE_PLUGIN_ROOT}/hooks/ contains Python hook scripts (.py files) and a hooks.json configuration. Read hooks.json to find matchers grouped by event type. Group matchers by backend — infer from the matcher pattern (atlassian, gitlab, google-drive, rag-memory).
If $ARGUMENTS matches a category key, "hooks", or "agents", show only that section and end with:
Run
/devflow:plugin-overviewwith no arguments to see the full guide.
If $ARGUMENTS is empty or "all", show the full guide below.
DevFlow is an AI-native SDLC plugin for Claude Code. It connects your issue tracker, documentation, and VCS into a single workflow — from problem discovery through PR/MR creation.
Present this verbatim as the first thing after the opening:
Where do you want to start?
| I want to... | Run |
|---|---|
| Work on an existing issue | /devflow:build:fetch-issue [KEY] |
| Start a new project or feature | /devflow:pm:discover |
| Set up team standards | /devflow:foundation:capture-conventions |
| Audit a repo against team standards | /devflow:foundation:audit-conventions |
| Generate CLAUDE.md for a repo | /devflow:foundation:generate-claude-md |
| First-time setup | /devflow-setup |
| See the build workflow end-to-end | /devflow:build:workflow-guide |
For each category that has skills, render:
[Display heading] ([count])
| Skill | Description |
|---|---|
/[name] | [description] |
Custom Agents ([count])
| Agent | Model | Description |
|---|---|---|
| [name] | [model] | [description] |
Approval Hooks ([script count] scripts, [matcher count] protected operations)
These hooks require user approval before writing to external backends.
For each backend group:
[Backend Name]
| Operation | Matcher |
|---|---|
| [last segment of matcher] | [full matcher pattern] |
Total: [skill count] skills, [agent count] agents, [hook script count] hook scripts ([matcher count] protected operations)
Quick start:
/devflow-setup — Configure your backends (first time)/devflow:build:workflow-guide — Learn the build workflow/devflow:build:fetch-issue [KEY] — Start working on an issue/devflow:pm:discover — Start a new project or feature