dev-workflow

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

Skills (4)

• dev-resume

  Resume an interrupted development from its persistent checkpoint in ~/.claude/dev-state, reconciled against the real state of Git. Use when the user invokes /dev-resume, and equally whenever they say "continúa con la PROJ-123", "retoma la PROJ-123", "seguimos con la 123", "continúa con el desarrollo

• dev-task

  Run a software development task through the global orchestrated agent workflow: work-item context from an optional issue tracker, task classification, codebase research, stack-routed architecture, an approval gate on the plan, TDD RED to GREEN, documentation and version maintenance, code review, and

• install-rules

  Install or update the dev-workflow global rules into ~/.claude — the rules block in CLAUDE.md, the reference docs and scripts under ~/.claude/dev-workflow/, and a starter ~/.claude/dev-workflow.json. Use after installing or updating the dev-workflow plugin, or when the user says "install the workflo

• pr-review

  Quick review of someone else's pull request, merge request or branch: code quality, AI slop (filler code, invented service layers, wrappers, duplicated helpers, defensive noise, tests that prove nothing) and real edge cases, with C#/.NET, React+TypeScript and Android (Kotlin/Java) best practices. Di

Subagents (15)

• android-architect

  Senior Android and Kotlin architecture and planning specialist. Use proactively for non-trivial Android development after repository research. Detects whether the app is Compose, Views/XML or hybrid, decides UI state modelling, coroutine and Flow usage, lifecycle boundaries, persistence, networking,

• android-implementer

  Implementation engineer for Android and Kotlin. Use it to execute an already-approved implementation plan (or an approved micro plan on the trivial fast path) in an Android codebase: ViewModels, coroutines and Flow, Compose or XML UI, Room, Retrofit/OkHttp, Hilt wiring, navigation, and making a fail

• code-reviewer

  Senior read-only reviewer. Use it after implementation and documentation, before the final report and before an MR, or on demand for "revisa esta rama". It reviews the DIFF for correctness, security, concurrency, data integrity, contracts, performance that matters, error handling, missing important

• codebase-researcher

  Repository fact-finder. Use proactively before architecture planning for non-trivial software changes: it detects which stacks the project really uses (.NET, React, Android, other), locates the relevant areas, describes current behaviour, existing patterns, dependencies, test setup, API documentatio

• debugger

  Root-cause specialist. Use proactively for difficult bugs, unexplained exceptions, build failures, unexpected test failures, integration problems, and whenever another agent is stuck. It works from symptom to evidence to hypothesis to verification to root cause, refuses to keep guessing without new

• documentation-release-maintainer

  Documentation and release-metadata finisher. Use it after GREEN and before the final review on non-trivial changes, and for DOCUMENTATION_ONLY and RELEASE_PREPARATION work. It cleans up temporary and work-item-specific source comments, keeps the comments that explain WHY, updates OpenAPI/Swagger/Sca

• dotnet-architect

  Senior ASP.NET Core architecture and planning specialist. Use proactively for non-trivial .NET development after repository research. Identifies technical decisions, risks, missing evidence and user questions, then produces an approval-ready implementation plan. Never implements.

• dotnet-implementer

  Implementation engineer for .NET / ASP.NET Core. Use it to execute an already-approved implementation plan (or an approved micro plan on the trivial fast path) in a C# codebase: endpoints, application logic, EF Core / Dapper access, HTTP clients, DI and configuration wiring, and making a failing tes

• issue-tracker-coordinator

  Issue-tracker work-item specialist. Use it to fetch the context of a work item before planning (subject, description, tracker, project, parent, status, priority, relevant comments, acceptance criteria, relations, relevant attachments), to search for related issues or a plausible parent task, and to

• mr-reviewer

  Quick read-only reviewer for someone else's pull/merge request or branch, launched by the /pr-review skill. Reviews the diff against the development branch for code quality, AI slop (filler code, invented service layers, wrappers, duplicated helpers, defensive noise, tests that prove nothing) and re

• node-implementer

  Implementation engineer for Node.js and TypeScript backends and tooling. Use it to execute an already-approved implementation plan (or an approved micro plan on the trivial fast path) in a Node/TS codebase: HTTP APIs (Express/Fastify/Hono), WebSocket and SSE channels, persistence (SQLite, Postgres,

• react-architect

  Senior React and TypeScript architecture and planning specialist. Use proactively for non-trivial frontend development after repository research. Decides component architecture, state and server state, data fetching, forms, navigation, error and loading behaviour, accessibility and the test strategy

• react-implementer

  Implementation engineer for React and TypeScript. Use it to execute an already-approved implementation plan (or an approved micro plan on the trivial fast path) in a frontend codebase: components, hooks, forms, routing, API calls, state and server state, and making a failing test go green. It follow

• review-request-publisher

  Review-request specialist. Use it after the user has validated the development and approved the MR, to prepare and publish one review request (a GitHub PR or GitLab MR) into the repository's development branch with the configured title format and the Summary / QA / Tests description, synthesised pri

• test-engineer

  Testing specialist across .NET (xUnit, WebApplicationFactory, Testcontainers, Moq/NSubstitute), React (Vitest, Jest, React Testing Library) and Android (JUnit, coroutine tests, Compose UI and instrumentation tests). Use it to write the failing test FIRST for an approved plan and prove a valid TDD RE

Hooks (1)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guard.py" 2>/dev/null || python "${CLAUDE_PLUGIN_ROOT}/hooks/guard.py"

Similar plugins