[PM-33576] llm: Add orchestration command, agent, and skill index to CLAUDE.md#2450
[PM-33576] llm: Add orchestration command, agent, and skill index to CLAUDE.md#2450SaintPatrck wants to merge 2 commits intomainfrom
Conversation
github-actions
bot
added
the
t:llm
|
Great job! No new security vulnerabilities introduced in this pull request |
|
Claude finished @SaintPatrck's task in 3m 54s —— View job I'll analyze this and get back to you. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2450 +/- ##
==========================================
- Coverage 87.08% 85.95% -1.13%
==========================================
Files 1862 2092 +230
Lines 165404 180212 +14808
==========================================
+ Hits 144040 154907 +10867
- Misses 21364 25305 +3941 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
.claude/commands/work-on-ios.md
Outdated
|
|
||
| ## Phase 1: Load or Create Plan | ||
|
|
||
| Check for an existing plan at `.claude/outputs/plans/`: |
There was a problem hiding this comment.
🤔 We don't have a .gitignore of some sort set up against this directory, which means, are we anticipating now that we'll be committing Claude's generated plans into the repo?
There was a problem hiding this comment.
No. This shouldn't reference any specific file locations yet. However, I do suggest making a global ~/.gitignore_global entry to a common place for Claude to safely drop its outputs. As you can see, I use .claude/outputs/.
Once these tools are converted to plugins, they'll have their own output locations outside of any repo/project context. 🚀
There was a problem hiding this comment.
P.S.
I removed the references and realigned with the Android counterpart. Thanks for calling this out.
There was a problem hiding this comment.
My just base-level plan-mode documents have been going in ~/.claude/plans for the time being, which is a mite inconvenient. Probably something for me to consider doing some more reconfiguration around 🤔
…CLAUDE.md - /work-on-ios command: 7-phase workflow with user confirmation between phases — load/create plan, implement, write tests, build/verify, preflight, commit, create PR + label - ios-implementer agent: opus model, blue color; invokes /work-on-ios as primary workflow; auto-approves phase transitions; enforces security, test, and PR creation constraints - outputs/plans/.gitkeep: directory for design docs saved by planning skills - CLAUDE.md: add Skills & Commands index table at end of file (10 skills, 2 commands with trigger phrases and usage)
…plans directory - Restructure work-on-ios.md to match work-on-android.md pattern - Remove plan-loading phase, add review phase with code-review-local - Remove .claude/outputs/plans/ directory (addresses gitignore concern) - Align ios-implementer agent with android-implementer structure - Update plan-ios-work.md to present plans in-context instead of saving to disk
SaintPatrck
force-pushed
the
llm/orchestration
branch
from
50189e3 to
88a6d8c
Compare
Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed changes across 4 files in the Code Review DetailsNo findings. Changes are internally consistent, align with the stated objective of matching the Android template structure, and address the prior review feedback regarding committing generated plans by removing the disk-saving phase entirely. |
2 participants
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-33576
📔 Objective
Adds the final orchestration layer: a
/work-on-ioscommand that sequences all skills end-to-end, an autonomous agent for hands-off execution, and a skill/command index in CLAUDE.md.What changed:
commands/work-on-ios.md— 7-phase guided workflow with user confirmation between each phase: implement → test → build & verify → self-review → commit → code review → create draft PR. Invokes the appropriate skill at each phase. Structured to match the Androidwork-on-android.mdtemplate.commands/plan-ios-work.md— 3-phase planning command: ingest requirements (Jira or description) → refine with gap analysis → design implementation approach. Plans are presented in-context rather than saved to disk.agents/ios-implementer/AGENT.md— Opus model, blue. Runs/work-on-iosas primary workflow with a self-review protocol at each phase transition, auto-approving when criteria are met. Includes decision-making framework and explicit skill tool declarations. Aligned with the Androidandroid-implementeragent structure.CLAUDE.md — Adds a Skills & Commands index table: 10 skills with trigger phrases, and 2 commands with usage descriptions.
This is the final commit in the 7-PR series (PM-33570 through PM-33576) that brings the iOS
.claude/configuration to full parity with the Android template.