feature-dev

Plugin feature-dev from marketplace juanmhidalgo-plugins in juanmhidalgo/claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (2)

• spec-driven-development

  Use when starting a new feature or significant change with no spec yet. Covers single-repo and multi-repo features. Do NOT use for typos, single-line fixes, or post-hoc documentation of finished work. - spec - specification - requirements - planning - acceptance-criteria - "write a spec" - "define r

• tdd-patterns

  Use when executing TDD cycles with coverage gates and quality checks. Do NOT use for general testing advice or test writing without the full TDD cycle. - tdd - red-green-refactor - coverage-gate

Slash commands (8)

• /feature-dev:cleanup

  Use to bulk-delete implemented features (spec, plan, review history and feedback) from .feature-dev/features/, and stale review-server pointers. Lists only safe candidates and requires Y/N confirm. Offers first to rescue a spec's Decisions Log and unticked QA items as a comment on its branch's PR or

• /feature-dev:explore-plan

  Use when starting a feature that touches multiple parts of the codebase and you need a structured implementation plan before coding. Do NOT use for simple bug fixes or single-file changes. - exploration - planning - parallel-agents - implementation-plan - architecture - "explore and plan" - "plan th

• /feature-dev:harden

  Use after an implementation is finished — typically right after /feature-dev:tdd — to review it in fresh context (defects, spec conformance and tech debt at once), verify every finding, fix the ones you approve, and re-review what the fixes changed. Replaces running /code-review:staged, /code-review

• /feature-dev:plan-review

  Use to re-validate a PLAN-*.md edited by hand, or one written before explore-plan reviewed its own plans. Outputs Blocking / Should Address / Nice to Have findings. Do NOT use right after /feature-dev:explore-plan (it already ran this review), for code review, or for SPEC review (use /feature-dev:sp

• /feature-dev:review

  Use to review a SPEC-*.md or PLAN-*.md in the browser — outline, decision cards, text-anchored comments, diff against the previous version — and apply the verdict. Do NOT use for a structural gap check (use /feature-dev:spec-review or /feature-dev:plan-review) or for code review. - review - browser

• /feature-dev:spec-review

  Use to validate a SPEC-*.md for gaps before planning or implementation. Outputs Blocking / Should Address / Nice to Have findings. Do NOT use to verify implementation (use /prd:validate). - spec-review - spec-validation - gap-analysis - feature-dev - "review the spec" - "validate the spec" - "find g

• /feature-dev:spec

  Use before writing code when requirements are ambiguous or a feature has non-obvious scope. Do NOT use for simple, self-evident changes. - spec - specification - requirements - planning - "write a spec" - "create specification" - "define requirements first" - "spec-driven development" - Read - Grep

• /feature-dev:tdd

  Use when implementing a new feature or fixing a bug where you want tests to lead, not follow. Do NOT use for quick one-line fixes or refactors without behavioral change. - tdd - test-driven - feature-development - coverage - red-green-refactor - "implement with TDD" - "test-driven development" - "wr

Subagents (13)

• api-contract-explorer

  Explores declared API contracts for a feature — OpenAPI, GraphQL, tRPC, protobuf, JSON Schema. Separate from endpoint *code* (backend-explorer covers that). Critical for multi-repo features. Opt-in primitive — invoke directly from any skill.

• backend-explorer

  Explores backend/API layer for a feature. Finds models, views, serializers, endpoints, services, and database patterns. Spawned by explore-plan for parallel exploration.

• config-explorer

  Explores the configuration surface for a feature. Finds env vars, settings modules, feature flags, secrets handling, and per-environment overrides. Opt-in primitive — invoke directly from any skill.

• cross-repo-advisor

  Produces a decision brief for ONE bounded cross-repo question during feature work — which side owns a field, whether a change breaks a declared contract, how a consumer should branch on an error. Reads the spec's `repos:` block and the sibling repos and recommends. Read-only: it never edits, never r

• feature-implementer

  Orchestrates execution of an approved PLAN-*.md (or equivalent step list) by dispatching each step to plan-step-executor in order, accumulating carry-over notes between steps, and halting on blockers. Use AFTER a plan is approved and you want a single delegate to drive the whole feature instead of s

• frontend-explorer

  Explores frontend/UI layer for a feature. Finds components, views, hooks, API clients, routing, and state management. Spawned by explore-plan for parallel exploration.

• history-explorer

  Explores git history and open PRs for a feature. Finds recent changes, conflicts, and historical patterns. Spawned by explore-plan for parallel exploration.

• observability-explorer

  Explores logging, metrics, tracing, error reporting, and alerting conventions for a feature's domain. Opt-in primitive — invoke directly from any skill.

• plan-step-executor

  Executes ONE step of an approved multi-step plan in isolation, so the orchestrating agent preserves its context budget. Spawn one instance per qualifying step — a step with its own acceptance criteria, multi-file scope, or independent verification. Do NOT use for trivial single-line changes, pure re

• schema-explorer

  Explores database schema and migration state for a feature's domain. Finds migration files, current schema, indexes, constraints, and naming conventions. Opt-in primitive — invoke directly from any skill.

• spec-plan-validator

  Validates a SPEC-*.md or PLAN-*.md artifact for structural and logical gaps before downstream work, and checks a spec's factual claims about the existing code (paths, symbols, fields, FK direction, endpoints) against the repository. Emits a categorical Blocking / Should Address / Nice to Have findin

• tdd-runner

  Executes strict red-green-refactor TDD cycles for one bounded task, enforcing the discipline that RED must legitimately fail before any production code is written. Caps at 5 cycles per invocation by default. Stack-agnostic: detects backend (pytest) vs frontend (vitest) from target path or task descr

• test-explorer

  Explores the test suite for a feature. Finds test files, fixtures, factories, patterns, and coverage config. Spawned by explore-plan for parallel exploration.

Similar plugins