dev-workflow

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

Skills (10)

• dev-workflow:addressing-pr-comments

  Address PR review feedback in the current session — reads new comments, file-level inline comments, and review decisions since the last commit, then implements the required changes and replies to the PR with a summary of fixes. Use when a user asks to address PR comments, respond to review feedback,

• dev-workflow:creating-stories

  Use when a user wants to capture a feature idea as a formal story, create a ticket, write to the backlog, or says 'create a story', 'write a ticket', 'add to backlog', or describes a feature they want tracked.

• dev-workflow:debugging

  Three-mode unified skill for debugging bugs, standalone story implementation, and addressing PR review feedback (rework). Mode is auto-detected from arguments: no args = debug mode (investigate a reported bug), story-id only = development mode (implement a story), story-id + --rework = rework mode (

• dev-workflow:dev-verify

  Run the developer's dev deploy and verification gate against an existing PR on its current HEAD: exemption check, trigger the dev deploy CI, wait, verify each acceptance criterion in dev, fix loop, post the evidence comment, mark the PR ready. Invoked by the developer agent's verify mode and by wrap

• dev-workflow:developing

  Full-stack development workflow with story context loading, TDD, automated planning, subagent execution, and PR creation. Use this skill whenever implementing features, fixing bugs, or any hands-on coding task. Always use this when a user says 'implement', 'build', 'code up', 'add feature', 'start d

• dev-workflow:full-cycle

  Drives the entire dev-workflow lifecycle end to end in order — creating-stories → writing-specs → developing → reviewing-prs → testing-prs — looping back through review and testing until both pass. Use when a user wants to run the whole development pipeline for a feature, take a story 'all the way t

• dev-workflow:reviewing-prs

  Comprehensive multi-perspective PR review (Product Manager, Developer, QA, and Architect lenses) that compares implementation against story requirements and CI/CD results. Includes automatic first-review vs re-review mode detection. Always use this when a user asks to review a PR, check a pull reque

• dev-workflow:testing-prs

  Evidence-based functional testing of PRs in a dev/test environment — deploys the branch, brainstorms and designs test scenarios, executes them with evidence collection, and submits a formal GitHub review. Use whenever a user wants to functionally test a feature branch, validate a PR in a dev environ

• dev-workflow:toiling

  Use when a task is operational or one-off and needs no code change, branch, or PR, when a user asks for a runbook, or says "toil", "toiling", "ops task", "runbook", or "/start toiling". Covers cleanups, restarts, scaling, rotations, and similar chores, with or without a story ID.

• dev-workflow:writing-specs

  Use when a developer needs a detailed technical spec before coding, when a user provides a story ID and asks for a spec, implementation plan, or Claude Instructions, or always before the `developing` skill when working from a PM story.

Subagents (5)

• developer

  Implementation and rework worker for the dev-workflow pipeline. Story mode wraps the developing skill: branches, implements with TDD, and opens one PR per repo. Rework mode (a PR number is supplied) lands on the PR's branch and wraps addressing-pr-comments to fix review or test feedback. Verify mode

• pr-state-reader

  Read-only state probe for the dev-workflow pipeline. Used by full-cycle for entry/resume detection, resolving PR numbers linked to a story, and reading the authoritative review/test decision (from GitHub, or from the Local Mode round notes), the pre-send hand-off check (draft state plus dev-verifica

• reviewer

  Code-review worker for the dev-workflow pipeline. Wraps the reviewing-prs skill. Gates on the developer's dev-verification evidence for current HEAD (bouncing immediately when it is missing, stale, or invalid), reuses the developer's validated deploy run as CI evidence or else runs a fresh dev build

• spec-writer

  Spec-writing worker for the dev-workflow pipeline. Wraps the writing-specs skill. Runs as a persistent role session (one per story) for standalone full-cycle, where it relays clarifying questions and finished specs to the user through the orchestrator and runs the final linking only after the record

• tester

  Functional-testing worker for the dev-workflow pipeline. Wraps the testing-prs skill. Gates on the developer's dev-verification evidence for current HEAD (bouncing immediately when it is missing, stale, or invalid), reuses the developer's validated deploy when dev still serves that HEAD or else depl

Hooks (3)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/role-session-context.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/context-meter.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/compact-injector.sh

Similar plugins