What problem does it solve?
Writing iOS code without a clear plan leads to inconsistent architecture, missed dependencies, and rework. This Skill produces a structured implementation plan for Bitwarden iOS features before any code is written, ensuring the design follows the project's established Coordinator-Processor-View patterns.
Core Features & Use Cases
- Change Classification: Categorizes work as new feature, enhancement, bug fix, refactoring, or infrastructure to scope planning depth.
- File-Level Planning: Lists exact files to create or modify across Core, UI, and test layers, following BitwardenShared conventions.
- Dependency-Ordered Phases: Sequences work from data layer through services, DI wiring, Processor/State, View/Coordinator, and tests.
- Risk Assessment: Flags security, app extension memory limits, multi-account isolation, and BitwardenSdk dependency concerns.
- Use Case: When asked to add a new vault feature, the Skill explores similar existing implementations, produces a design document saved to
.claude/outputs/plans/, and asks for confirmation before implementation begins.
Quick Start
Ask the assistant to plan the implementation of a new Bitwarden iOS feature, such as "plan how I should implement a password history screen".