development-workflow

Plugin development-workflow from marketplace buildwithjpegg in jpeggdev/buildwithjpegg. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• auto-release

  One-time setup that wires semantic-release into a repository for automated versioning, changelog generation, and GitHub releases from conventional commits. Use when setting up a new repo that will be publicly released.

• blueprint

  Use when you have a spec or requirements for a multi-step task, before touching code

• ci-loop

  Use after creating a PR to monitor CI and automatically fix failures before reporting back. Fires automatically after PR creation. Do not report the PR as ready until CI is green.

• craft-skill

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

• delegate

  Use when executing implementation plans with independent tasks in the current session

• draft-prs

  Manages draft status for stacked PRs. Use when creating any PR in a stack (mark non-current PRs as draft), and when a base PR merges (promote the next PR to ready). Prevents reviewers from seeing PRs that depend on unmerged work.

• evaluate

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

• fan-out

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• handle-review

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

• onboard

  Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

• pr-stack

  Maintains .claude/stack.json tracking stacked PR state across sessions. Read at session start when working on a stacked feature. Update after every PR creation, merge, or rebase.

• pre-ship

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• root-cause

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• seek-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• test-first

  Use when implementing any feature or bugfix, before writing implementation code

• wrap-up

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Slash commands (3)

• /development-workflow:evaluate

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.

• /development-workflow:run-build

  Execute plan in batches with review checkpoints

• /development-workflow:write-blueprint

  Create detailed implementation plan with bite-sized tasks

Subagents (1)

• code-reviewer

  Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing

Hooks (1)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

Similar plugins