oneflow

A Claude Code plugin providing six development workflow skills that work together to take a task from backlog to merged PR.

Skills

Skill	Trigger	Description
`/do`	`/do <branch> <instructions>`	Full dev workflow: worktree → plan → implement → test → PR
`/green`	`/green [PR-URL]`	Make a PR merge-ready: fix pipeline, apply review comments, auto-merge
`/review`	`/review [PR]`	Review a PR (fresh / re-review / self-review of your own draft)
`/backlog`	`/backlog [description]`	Capture out-of-scope work to `.claude/TODO.md`
`/backlog-review`	`/backlog-review`	Triage, ticket, and dispatch items from the backlog
`/investigate`	`/investigate <question>`	Answer a manager's question with evidence-based analysis

Workflow

/backlog-review          # triage, ticket future work, decide what to implement
  └─ /do <branch>        # plan + implement + PR
       └─ /review        # self-review the draft (optional, before /green)
            └─ /green    # fix CI, address review, merge

/review also runs against someone else's PR (fresh review or re-review). Comments it posts are what /green triages on the receiving side.

Anything discovered while working that's out of scope → /backlog to park it for later.

Dependencies

gh CLI — authenticated with repo access
Atlassian MCP (getJiraIssue, createJiraIssue) — for Jira ticket lookup and creation in /do, /backlog-review. Re-authenticate via /mcp if needed.
pup CLI — Datadog access for /investigate (used by dd-apm, dd-logs, dd-monitors skills). Required only when investigating service/performance/error/alert questions.
Subagent types:
- git-ops, test-runner — for worktree setup, commits, PRs, and test runs in /do and /green. Typically installed via personal-setup or a team plugin.
- codestyle-reviewer, architecture-reviewer — required for the review gates in /do Step 5b, /green Step 3e, and /review's dimension fanout. Typically installed via personal-setup or a team plugin; if unavailable, those steps must be skipped explicitly.
- Optional but recommended — these are suggested in the skills; if missing, skills fall back to inline approaches:
  - critic — adversarial reviewer (used in /do Step 3 plan check, Step 5b implementation check, and /review's dimension fanout)
  - Explore — broad codebase exploration (used in /do Step 2 context-gathering)
  - feature-dev:code-explorer — deep code analysis (used in /investigate for code-walk questions)
  - personio-common:code-expert-finder — git-blame ownership (used in /investigate for "who owns X" questions)
superpowers plugin — /do invokes superpowers:brainstorming for complex tasks

References

Shared git and code-review conventions live in skills/references/:

git-ops.md — worktree, commit, push, and PR conventions
CODE-REVIEW-STYLE.md — Conventional Comments style

/do, /green, and /review Read these on demand at the dispatch step, rather than @-importing them at skill-load time, to keep the always-loaded body of each skill lean.

Jira project key

/backlog-review defaults to creating new Jira tickets in project ID. Override in skills/backlog-review/SKILL.md Step 5b.

Installation

Add this repo as a marketplace entry (or install directly). Once installed, invoke skills from any Claude Code session with /do, /green, /review, /backlog, /backlog-review, or /investigate.