llm: Add plan-implement-review pipeline command - #7121
Conversation
github-actions
Bot
added
the
t:llm
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7121 +/- ##
=======================================
Coverage 85.86% 85.86%
=======================================
Files 926 926
Lines 65940 65940
Branches 9376 9376
=======================================
Hits 56617 56617
Misses 6098 6098
Partials 3225 3225
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR adds a single new slash command, Code Review Details
Also noted, not raised inline: Step 7 suggests |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| After all 4 review tasks for a phase are complete, **you (the team lead) consolidate** the findings: | ||
|
|
||
| 1. Read all 4 review output files. | ||
| 2. Write a consolidated review summary to `.claude/outputs/reviews/{slug}-REVIEW-SUMMARY.md`: |
There was a problem hiding this comment.
♻️ DEBT: Consolidated summary path is not phase/round-scoped, so it is overwritten every cycle.
Details and fix
Step 3b scopes reviewer outputs per phase ({slug}-REVIEW-CODE-P{N}.md), and Step 6b explicitly overwrites per round. But Step 5 always writes to the same fixed {slug}-REVIEW-SUMMARY.md, even though the template inside it carries **Phase** and **Round** fields.
For a multi-phase run (which Step 3 calls "the norm"), the final artifact only contains the last round of the last phase. Step 7 then promises to present "Consolidated review summary path" and "Number of review-fix cycles per phase" from artifacts that no longer exist.
Suggested fix — scope the path the same way reviewer files are:
2. Write a consolidated review summary to `.claude/outputs/reviews/{slug}-REVIEW-SUMMARY-P{N}-R{round}.md`:
and update the Step 1 output-path list to match.
| @@ -0,0 +1,304 @@ | |||
| --- | |||
| description: End-to-end pipeline orchestrating requirements analysis, architecture planning, implementation, and multi-agent code review via agent team | |||
| argument-hint: <task description, Jira ticket, or Confluence URL> [--confirm] | |||
There was a problem hiding this comment.
♻️ DEBT: New command is not registered in the .claude/CLAUDE.md command table.
Details and fix
.claude/CLAUDE.md maintains a Command registry that currently lists /plan-android-work, /work-on-android, and /review-android. Adding a command without a corresponding row makes it undiscoverable to anyone reading the project config, and leaves the table stale for the next contributor.
Suggested addition to the Command table in .claude/CLAUDE.md:
| `/plan-implement-review <task>` | Agent-team pipeline: plan → implement → 4-reviewer gauntlet → fix cycle (requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`) |1 participant
Objective
Add a
plan-implement-reviewcommand that orchestrates an end-to-end Android development pipeline — requirements analysis, architecture planning, implementation, and multi-agent code review — driven by a Claude Code agent team.Pipeline
Notes
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.TeamCreate/TeamDelete.