dp

Plugin dp from marketplace claude-dev-pipeline-plugin in kostia-official/claude-dev-pipeline-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (10)

• dp-code-review-apply

  Use when an active dev-pipeline run is at the code-review-apply step. Walks code-review.md findings one-by-one as todos, reasons about each fix in isolation, applies CONFIRMED fixes to the working tree (PLAUSIBLE stay as recommendations, Promise.all never auto-applied), then fills the doc's Applied/

• dp-code-review

  Use when an active dev-pipeline run is at the code-review step. Runs a full /code-review-style review over this run's diff — 8 finder angles (3 correctness + reuse/simplification/efficiency + altitude + conventions), an adversarial verify pass, then writes a ranked findings doc to code-review.md. Ap

• dp-implementation

  Use when an active dev-pipeline run is at the implementation step. Generates todos from plan.md, implements them one-by-one, and runs typecheck + lint at the end. Strict-typing rules (no `any`, no dirty `as`) are self-policed by the skill and verified by the project's lint.

• dp-improve

  Use when the user asks to improve, fix, tweak, or extend the dev-pipeline plugin itself (its skills, orchestrator, scripts, manifest). Edits this plugin's source tree, bumps version, and creates a git commit. Plugin authors only — refuses to run if the plugin is installed via marketplace cache.

• dp-investigation

  Use when an active dev-pipeline run is at the investigation step. Gathers wide context about the feature and writes a structured context.md (Feature explanation, Related files, Existing code worth reusing, Risks & unknowns).

• dp-plan-proposal

  Use when an active dev-pipeline run is at the plan-proposal step. Prints a short proposal (user request + optional root cause for bugs + plan proposal + technical approach) for fast user feedback before any plan file is written. Loops on feedback until approved.

• dp-plan-review-apply

  Use when an active dev-pipeline run is at the plan-review-apply step. Walks plan-review.md findings one-by-one as todos, reasons about each fix in isolation, asks the user with concrete options when direction is unclear, and patches plan.md. Self-contained.

• dp-plan-review

  Use when an active dev-pipeline run is at the plan-review step. Fans out 7 finder subagents over plan.md (coverage, approach-soundness, invariant, blast-radius, altitude, design-efficiency, reuse/extraction), adversarially verifies every candidate, then writes a ranked findings doc to plan-review.md

• dp-plan-wrapup

  Use when an active dev-pipeline run is at the plan-wrapup step. Final consistency check on plan.md, summarizes changes since the proposal, and asks for the user's final approval before implementation.

• dp-plan

  Use when an active dev-pipeline run is at the plan step. Writes a code-forward plan.md (Context, Approach, File-by-file changes shown as real code chunks, Reuse & extraction, Verification) that a post-compaction session can execute and a human can review in one pass.

Slash commands (1)

• /dp:dev-pipeline

  Start, resume, or continue a feature-planning pipeline run. Accepts a feature description (new run), a path to a state.json/context.md/plan.md (explicit resume), or a phrase like "continue <feature>" / "find plan for <feature>" (implicit resume).

Hooks (2)

• SessionStart

  bun ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/capture-session.ts

• Stop

  bun ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/enforce-pipeline-progress.ts

Similar plugins