Collection of agents, commands and skills for a generic software development workflow
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
Guided idea exploration workflow that develops a raw concept into a mature, PRD-ready requirement through structured Socratic interviews. Use when user wants to explore, stress-test, or develop an idea — triggers at "explore idea", "I have an idea", "let's explore", or similar. Ends by invoking /workflow-create-prd when the idea is mature.
Orchestrate the implementation of a feature from an approved implementation plan. Detects the tech stack, spawns specialized agents per story and enabler (respecting dependency order), collects all agent artifacts into the spec folder, runs the test suite, and tracks progress. Always use this skill when the user says "implement", "start coding", "execute the plan", "implement the feature", or wants to continue a partially-implemented feature. This is the final phase of the product workflow: Conceituação → PRD → Plano → Implementação. Accepts optional flag --worktree to implement in an isolated git worktree.
Transforms a PRD into a detailed implementation plan broken into user stories with per-layer tasks, acceptance criteria, and user validation steps. Use when the user wants to plan the implementation of a feature, break down a PRD into tasks, or mentions "implementation plan".
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Collection of agents, commands and skills for software engineering.
Some skills were collected from authors listed in the Resources section and some were crafted from study notes and practical examples.
The goal is to enable any agent to develop software using the industry's consolidated knowledge.
Plugins are available for specific stacks: Java, Node.js, Python, Angular, React, DevOps tooling, and more.
[!NOTE] All plugins depend on
programming-skillsas a base. Install it first before any other plugin.
programming-skills — Foundation for All Stacksjava — Java & Spring Boot Developmentpython — Modern Python Developmentnode — Node.js / JavaScript / TypeScriptfrontend — React, Angular, Next.js & Mobiledevops — Infrastructure, CI/CD & Platform Engineeringdocs — Technical Writing & Documentationarchitecture — System Design, C4 & ADRsworkflow — Development Lifecycle Orchestration| Concept | Description | How to invoke | |
|---|---|---|---|
| 🤖 | Agent | Specialized AI persona with focused expertise | @agent-name in Claude Code |
| ⚡ | Command | Slash command that triggers a pre-built workflow | /command-name |
| 🧰 | Skill | Reusable knowledge prompt that guides agent behavior on a specific topic | Referenced in conversation context |
Each plugin follows the same directory layout:
plugins/<plugin-name>/
├── agents/ # Specialized agent definitions (.agent.md)
├── commands/ # Slash commands (/command-name)
└── skills/ # Reusable knowledge prompts
Plugin dependency:
programming-skills (base — required by all)
├── java
├── python
├── node
├── frontend
├── devops
├── docs
├── architecture
└── workflow
| Plugin | 🤖 Agents | ⚡ Commands | 🧰 Skills | Stack |
|---|---|---|---|---|
programming-skills | 11 | 5 | 22 | Any — foundation for all plugins |
java | 5 | 7 | 11 | Java / Spring Boot |
python | 2 | 4 | 19 | Python / Django / FastAPI |
node | 2 | 2 | 11 | Node.js / JavaScript / TypeScript |
frontend | 8 | 2 | 24 | React / Angular / Next.js / Mobile |
devops | 12 | 1 | 21 | CI/CD / Kubernetes / Terraform |
docs | 6 | 5 | 1 | Technical Writing / Documentation |
architecture | 9 | 6 | 13 | System Design / C4 / ADRs |
workflow | 0 | 0 | 4 | Development Lifecycle / Any methodology |
To try without installing:
claude --plugin-dir ./software-engineering-skills/plugins/<plugin-name>
To install as a plugin, run the Claude Code command:
# Remote
claude plugin marketplace add https://github.com/wesleyegberto/software-engineering-skills.git
# Local path
git clone https://github.com/wesleyegberto/software-engineering-skills.git
claude plugin marketplace add ./software-engineering-skills
# Install a specific plugin
claude plugin install programming-skills@software-engineering-skills
claude plugin install java@software-engineering-skills
claude plugin install python@software-engineering-skills
claude plugin install node@software-engineering-skills
claude plugin install frontend@software-engineering-skills
claude plugin install devops@software-engineering-skills
claude plugin install docs@software-engineering-skills
claude plugin install architecture@software-engineering-skills
claude plugin install workflow@software-engineering-skills
To install just link the extension with the folder:
Collection of agents, commands and skills for software development in Java with Spring Boot
Collection of agents, commands and skills for software development in Python
Collection of agents, commands and skills for documentation
Collection of agents, commands and skills for DevOps
Collection of agents, commands and skills for Node
npx claudepluginhub wesleyegberto/software-engineering-skills --plugin workflowMatt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.