Aiogram feature workflow

aiogram feature workflow

deliver the smallest complete vertical slice. a request to implement means working code, not a plan-only response.

required skills

• if the repository is not already mapped, use aiogram-project-orientation first.
• when handlers or routing change, use aiogram-handler-implementation.
• when stateful conversation flow changes, use aiogram-fsm-flows.
• when keyboards or callback data change, use telegram-keyboards-callbacks.
• when current external behavior is load-bearing, use telegram-docs-check.
• after code changes, use aiogram-bot-verify.

workflow

1. define the trigger, actor, response, permissions, data reads and writes, failure cases, and observable acceptance behavior.
2. classify the feature as command, callback or menu, FSM, admin, data-backed, integration-backed, or a combination.
3. locate nearby conventions for routers, filters, dependencies, services, repositories, texts, keyboards, states, and tests.
4. implement one vertical slice containing only the layers it needs:
   • transport entry and registration
   • service or use-case behavior
   • repository and migration changes
   • text, keyboard, and state changes
   • focused tests and verification
5. preserve the installed aiogram major-version style. never mix an aiogram migration into ordinary feature work.
6. keep telegram transport in handlers and domain decisions outside them. handlers may parse events, call application logic, render responses, and handle telegram-specific errors; they should not own raw sql, large transformations, or integration protocols.
7. update every affected surface, including commands, menus, permissions, middleware dependencies, persisted data, fixtures, and all supported locales.
8. make side-effecting operations transactional or idempotent where retries, duplicate updates, or repeated callbacks can occur.
9. test the success path, permissions, invalid input, routing boundaries, callback parsing, state transitions, repository behavior, repeated actions, and the reported regression when applicable.

completion requires reachable routing, complete data and user-facing surfaces, focused coverage, and a safe verification result. for plan-only requests, stop before editing and return the vertical slice, affected layers, checks, and blocking decisions.