development-pipeline

Plugin development-pipeline from marketplace dev-helper-toolkits in ChanatSinp/dev-helper-toolkits. Commands read from the repo's manifest — 12 days ago.

Skills (1)

• development-pipeline

  Use when turning a requirement into shipped, verified work through a staged delivery pipeline (requirements/design, execution planning, implementation, and opt-in unit tests (written in the implementation pass), technical-test, code-review, and API-documentation stages). On Claude Code, dispatches t

Subagents (8)

• api-bruno-writer

  Opt-in only — dispatch this agent only when the user has explicitly asked for a Bruno collection, in their request or by selecting the stage in the development-pipeline opt-in question; never proactively or by default after code changes. Use this agent to turn documented APIs into a runnable Bruno c

• api-specs-writer

  Opt-in only — dispatch this agent only when the user has explicitly asked for API documentation, in their request or by selecting the stage in the development-pipeline opt-in question; never proactively or by default after code changes. Use this agent to document implemented HTTP APIs. It reads the

• code-reviewer

  Opt-in only — dispatch this agent only when the user has explicitly asked for a code review, in their request or by selecting the stage in the development-pipeline opt-in question; never proactively or by default after code changes. Use it when changed code needs review for correctness, edge cases,

• document-reader

  Opt-in only — dispatch this agent only when the user has explicitly asked for a source document summarized, in their request or by selecting the stage in the development-pipeline opt-in question; never proactively or by default after code changes. Use this agent when the user wants a source document

• implementation-planner

  Use this agent when the user wants a detailed implementation plan created before any code is written — new features, refactors, bug fixes, or architectural changes needing upfront planning with edge case analysis. It writes the plan to the project's `.claude/temp/plan.md` for other agents to execute

• plan-driven-implementer

  Use this agent when an implementation plan exists in the project's `.claude/temp/plan.md` and needs to be executed faithfully. Verification against the plan is the caller's responsibility, not this agent's.

• solution-architect

  Use this agent when the user brings requirements (feature request, integration spec, change request) and wants the full design produced — functional *and* technical — before implementation planning or coding. It elicits requirements exhaustively via user Q&A, probes for unstated edge cases and flaws

• technical-tester

  Opt-in only — dispatch this agent only when the user has explicitly asked for a test plan or technical testing, in their request or by selecting the stage in the development-pipeline opt-in question; never proactively or by default after code changes. Use it when a testing plan needs to be written o

Similar plugins