agbossjs
@agbossjs Organization
Public Skills
triage
by agbossjs
Conveyor stage 1 → status Triage. Takes a requirement (or an existing issue), clarifies its business side through quizzes — why, what it does, what it does NOT do, constraints, business acceptance criteria (AC1…) — and creates or updates GitHub issues, splitting into a parent with sub-issues when useful. Use whenever the user brings a new requirement, idea, request, bug report or an issue number/URL and wants it clarified, triaged, "заведи тикет", "разбери задачу" — before any technical spec or code.
implement
by agbossjs
Conveyor stage 3 → status In progress, and Test after merge. Implements Backlog issues — in parallel where they are independent (git worktrees with sub-agents, or separate Claude Code on the web sessions), in dependency order otherwise — each as its own branch and PR into main with tests, green gate, self-review, Wiki update and a manual-test handoff. Never moves anything to Done. Use after spec-session, or when the user says "implement", "имплементируй", "запусти", "go", or names Backlog issues to build.
framework-review
by agbossjs
Architecture review of the framework itself (DI, components, graph DSL, CLI) for extensibility and API quality in a world where code is written by agents, not by hand. Scores 17 axes, runs empirical probes (agent writes code, misconfiguration matrix, CLI contract, generators), verifies every finding, writes a report with an improvement proposal per finding and can file it as an epic. Use when the user asks for a framework / architecture / API / CLI review, "оцени архитектуру", "ревью фреймворка", or wants to compare against a previous review.
spec-session
by agbossjs
Conveyor stage 2 → status Backlog. For issues in Triage, decides the technical side through quizzes and writes into the issue a detailed spec, an implementation plan, acceptance criteria split into automated (tests) and manual (plain-language instructions for a human — where to go, what to do, what to see), test cases, wiki pages to update and dependencies. Use after triage, or whenever the user says "spec", "спека", "план имплементации", "распиши тикет", or wants issues ready for autonomous implementation.