Aiogram feature workflow

Skill ballisarium/aiogram-bot-skills/skills/aiogram-feature-workflow

focused workflows for building and maintaining aiogram bots

Install

npx -y skills add ballisarium/aiogram-bot-skills --skill aiogram-feature-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

use when adding or changing an aiogram bot feature; фича, команда, кнопка, меню, сценарий, callbacks, FSM, admin, database, integration flow.

SKILL.md

2.5 KB, as published. Nobody here has run it

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

define the trigger, actor, response, permissions, data reads and writes, failure cases, and observable acceptance behavior.
classify the feature as command, callback or menu, FSM, admin, data-backed, integration-backed, or a combination.
locate nearby conventions for routers, filters, dependencies, services, repositories, texts, keyboards, states, and tests.
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
preserve the installed aiogram major-version style. never mix an aiogram migration into ordinary feature work.
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.
update every affected surface, including commands, menus, permissions, middleware dependencies, persisted data, fixtures, and all supported locales.
make side-effecting operations transactional or idempotent where retries, duplicate updates, or repeated callbacks can occur.
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.

Gives 0 of the 12 instructions most automation workflows skills give

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

write conventional commit messagesin 36 of 745, across 35 files
delete branches after mergein 30 of 745, across 21 files
make atomic commitsin 25 of 745, across 15 files
write minimal code to pass testsin 22 of 745, across 10 files
run tests before committingin 21 of 745, across 13 files
re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
use try-catch for error handlingin 20 of 745, across 6 files
write tests before implementationin 20 of 745, across 8 files
configure branch protection rulesin 19 of 745, across 5 files
explain the why in commit messagesin 19 of 745, across 9 files
refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

deliver the smallest complete vertical slice
map the repository before starting work
implement only the layers the slice needs
preserve the installed aiogram major-version style
keep telegram transport in handlers
keep domain decisions outside handlers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.