What problem does it solve? Before a development stage can be planned and implemented, a human operator must supply things code cannot produce: product decisions, external accounts and consoles, secrets, assets, and UI mockups. This Skill scans the requirements document and the repository, then produces a single structured checklist in docs/operator/ so nothing blocking is discovered mid-implementation. ## Core Features & Use Cases - Stage-scoped checklist generation: Reads one stage of a requirements document (e.g. mvp-requirements.md#etap-17), classifies it as UI-touching or pure-data, and derives only the items that stage actually needs. - Repository-aware deduplication: Scans existing screens, env variable names, prior checklists, and fetched Figma specs so already-delivered items are never re-requested. - Series-aware naming and idempotency: Inherits naming conventions from existing checklist series, preserves checked-off items and recorded values on updates, and hands off to /dev-plan when blockers are resolved. - Use Case: You are starting stage E3 of a mobile app roadmap that needs Google OAuth, App Store Connect, and five new screens. Run the Skill to get a checklist of decisions blocking planning, accounts to create with proof-of-done commands, assets to commission, and mockups to order with frame dimensions and states. ## Quick Start Run /dev-prep with the path to your requirements stage, for example docs/brainstorms/mvp-requirements.md#etap-17, to generate the operator preparation checklist.
