By helderberto
Automates the full software development lifecycle for AI agents: generates PRDs and plans, drives test-driven development, reviews code, audits accessibility, i18n, security, and performance, organizes commits, and runs pre-ship checks.
Create a PRD through user interview, codebase exploration, and module design. Use when starting a feature with unclear requirements, when the user asks to spec or define what to build, or says "write a PRD". Don't use when requirements are crisp and a plan already exists (use /plan or /build).
Audit accessibility compliance in frontend code. Use when user asks to "check accessibility", "/a11y-audit", "audit a11y", "check WCAG", or wants to find accessibility issues. Don't use for backend code, non-UI files, or projects without HTML/JSX output.
Explore a codebase to surface architectural friction and propose refactors toward deep modules (simple interface, large implementation) as GitHub issue RFCs. Use when the user asks to audit architecture, find structural friction, or identify refactor opportunities across a codebase. Don't use for single-module interface design (use /codebase-design) or code-level review of a diff (use /code-review).
Group unstaged changes into atomic commits by concern, then push. Use when user asks to "atomic commits", "commit by group", "group commits", or wants to split changes into related commits before pushing.
Session briefing — shows active features, progress, and suggested focus. Use at the start of a session, when asking what to work on, or when checking active features.
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.
Personal SDLC toolbelt for AI coding agents — from PRD to ship.
A collection of skills that encode the workflows, quality gates, and engineering practices I use day-to-day. Pure Markdown, zero runtime deps, installable as a Claude Code plugin or copied into any agent that reads instruction files.
DEFINE PLAN BUILD VERIFY REVIEW SHIP
┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐
│ Idea │ ────▶ │ Spec │ ─────▶ │ Code │ ──────▶ │ Test │ ──────▶ │ QA │ ──────▶ │ Go │
│Refine│ │ PRD │ │ Impl │ │Debug │ │ Gate │ │ Live │
└──────┘ └──────┘ └──────┘ └──────┘ └──────┘ └──────┘
/hb:prd /hb:plan /hb:build /hb:verify-plan /hb:review /hb:ship
Each phase has a dedicated workflow skill that orchestrates the smaller toolbelt skills underneath it. Type the spine in order, or let it chain — every skill auto-routes by description. Only the outward-facing steps that push work out of your hands (ship, create-pull-request) are gated against auto-triggering, so you always pull that trigger yourself.
Install via the marketplace:
/plugin marketplace add helderberto/agent-skills
/plugin install hb@helderberto-skills
After install, skills are available as /hb:<skill-name> — e.g. /hb:prd, /hb:tdd, /hb:ship. Most skills also auto-trigger from natural language ("review this PR", "check accessibility", etc.) based on their description.
Install as native skills:
gemini skills install https://github.com/helderberto/agent-skills.git --path skills
Skills are auto-discovered and routed by description. See docs/gemini-cli-setup.md.
Clone and point OpenCode at the workspace — AGENTS.md plus the skills/ directory drive auto-routing:
git clone https://github.com/helderberto/agent-skills.git
Open the project in OpenCode. The .opencode/skills symlink and root AGENTS.md are already wired. See docs/opencode-setup.md.
Clone the repo, then copy individual skills into .cursor/rules/:
git clone https://github.com/helderberto/agent-skills.git
cp agent-skills/skills/tdd/SKILL.md .cursor/rules/tdd.md
cp agent-skills/skills/code-review/SKILL.md .cursor/rules/code-review.md
See docs/cursor-setup.md for the recommended starter set.
A non-trivial feature flows through all six phases. Each workflow skill is one invocation:
You: /hb:prd add dark mode support
AI: Interviews, scans the codebase, writes .specs/prds/dark-mode.md.
Run /hb:plan dark-mode next?
You: /hb:plan dark-mode
AI: Breaks the PRD into phased vertical slices.
Writes .specs/plans/dark-mode.md.
You: /hb:build dark-mode
AI: Implements next incomplete phase. TDD loop, lint, type-check.
Marks checkboxes in the plan. Offers a commit.
You: /hb:verify-plan dark-mode
AI: Verifies plan checkboxes against actual codebase.
Reports total progress and remaining blockers.
You: /hb:review
AI: Detects what changed, runs relevant audits in order
(code-review, a11y-audit, safe-repo, perf-audit, deps-audit, ...).
Consolidates findings into Critical / Important / Suggestion.
You: /hb:ship
AI: Pre-launch gate (validate-code + safe-repo --diff).
Atomic commits, push current branch.
/hb:ship --fast skips the gate (hotfix only).
For quick standalone tasks, you don't need the workflow — just describe what you want and the relevant skill triggers ("write tests for X", "audit deps", "create an ADR for Y").
Skills come in two modes. User-invoked ones never auto-trigger (disable-model-invocation: true) — reserved for outward-facing, irreversible actions you must pull the trigger on yourself: ship and create-pull-request. Everything else is model-invoked: it auto-routes by description and stays callable explicitly as /hb:<name>. Model-invoked descriptions carry the trigger and anti-trigger clauses routing depends on; the two user-invoked ones keep a single what-it-does sentence, since trigger phrases are dead weight when nothing auto-routes.
npx claudepluginhub helderberto/agent-skills --plugin hbSpec-driven workflow for AI coding agents: PRD, plan, build, verify, and track features using tracer-bullet vertical slices.
PRD-driven AI dev team control plane for Claude Code — agents, skills, and a GitHub-first sprint workflow.
Core developer skills for feature planning, code review, testing, commits, and daily development workflows.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Focused agentic engineering workflow: design-doc, spec, plan, implement, tdd, refactor, review, address-pr-feedback, browser-verify, explain-visually, compress, branch, and commit.
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
Plugin de ingeniería de software completa: 10 agentes de núcleo y 9 opcionales con personalidad propia, memoria persistente por proyecto, quality gates y flujos automatizados desde la idea hasta producción.