CybernetKZ
Official@CybernetKZ
CybernetKZ provides structured software engineering process skills covering domain modeling, incident triage, OpenSpec requirement authoring, review, and gated implementation.
Agent Skills by CybernetKZ
Showing 9 vetted skills indexed across 1 GitHub repositories.
domain-modeling
Build and maintain project domain glossaries and architectural decision records.
incident-flow
Guides production incident investigation from Telegram report to verified fix.
feature-flow
Orchestrates YouTrack ticket intake through spec-driven planning, testing, and PR delivery.
grill-with-docs
Interrogates plans and designs through structured questioning while generating ADRs and glossary entries.
grill-me
Runs a relentless interview session to sharpen a plan or design.
grilling
Interviews the user with sequential questions to stress-test plans and decisions.
tz-review
Reviews OpenSpec change proposals against codebase facts before implementation.
tz
Authors change requirements as OpenSpec change directories with proposals, spec deltas, and task checklists.
tz-implement
Implements OpenSpec change proposals through phased stop-gates, logical commits, and spec-delta archival.
Frequently Asked Questions About CybernetKZ
FAQPage SchemaWhat tasks can I accomplish using CybernetKZ's skills?▼
You can build and refine domain models with ubiquitous language, record architectural decisions as ADRs, process production incidents from Telegram reports to verified fixes, author and review OpenSpec requirement changes (ТЗ), and implement them through gated phases with logical commits and spec-delta archival.
Who are CybernetKZ's skills designed for?▼
They target software engineers and technical leads on the Cybernet team working on the HubTalk AI Conversation Flow project, particularly developers handling YouTrack WEB-* tickets, production incident response, and OpenSpec-based requirement authoring, review, and implementation.
How does the requirement implementation workflow operate?▼
The tz-implement skill executes an OpenSpec change through phases with stop-gates, prioritizing code over spec, producing logical commits referencing the ТЗ number, running make test and frontend builds after each commit, updating spec deltas and documentation, then archiving the change.
What does the tz-review skill check before implementation?▼
It mechanically reviews an OpenSpec change before implementation by verifying statements against actual code facts, enforcing anchors, checking consistency, numbering, and brand-cleanliness. Output is a list of issues with file paths and a verdict; the document itself is not modified.
What are the prerequisites for using these skills?▼
Skills assume a project using OpenSpec with an openspec/changes/ directory, YouTrack for task tracking, Telegram for incident reports, and a build setup supporting make test plus a frontend build. The grill-me and grill-with-docs skills have model invocation disabled.