Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

beeltec

@beeltec source repo

22 published skills

  1. ▌
    Glab · beeltec bundle
    Interact with GitLab from the command line — merge requests, issues, CI/CD pipelines, releases, repositories, variables, snippets, schedules, stacks, labels, milestones, incidents, auth, and raw API calls via glab.
    0
    installs
  2. ▌
    Wiki · beeltec bundle
    Manage the complete lifecycle of accepted project knowledge in a setup-project OKF wiki. Use for any read or mutation involving docs/wiki.
    0
    installs
  3. ▌
    Quick · beeltec
    Execute one user-declared small task — a tiny change or a deployment — directly, skipping the backlog/implement flow. User-invoked only; not for backlog work items or multi-file features — use `implement`.
    0
    installs
  4. ▌
    Discuss · beeltec bundle
    Stress-test a plan, decision, or idea one question at a time, then route confirmed conclusions. Use when the user wants to discuss or challenge their thinking.
    0
    installs
  5. ▌
    To Epic · beeltec bundle
    Plan one coordinated outcome end-to-end into a ready Epic under one standing approval. Use when asked to plan an Epic; not for standalone items — use to-backlog.
    0
    installs
  6. ▌
    To Wiki · beeltec
    Publish the conversation's confirmed durable knowledge to the wiki under one standing approval, including ADRs for decisions already in force. Not for unimplemented proposals — use to-backlog.
    0
    installs
  7. ▌
    Backlog · beeltec bundle
    Manage approved desired work from intake through refinement, ranking, execution state, cancellation, and archival. Use when creating or changing Epics, Stories, Tasks, or Bugs in docs/backlog.
    0
    installs
  8. ▌
    Guidance · beeltec
    Research and publish canonical technology and standards guidance pages under docs/wiki/engineering/, and refresh stale ones. Use when a subject's adopted rules must be persisted or a caller detects a missing, draft, or version-mismatched page.
    0
    installs
  9. ▌
    Research · beeltec bundle
    Research a proposed backlog record before readiness, attaching version and standards evidence to it. Only on explicit request for identified proposed work; never for general questions or wiki guidance.
    0
    installs
  10. ▌
    To Backlog · beeltec
    Intake the conversation's confirmed standalone work items and refine each to ready under one standing approval. Not for coordinated multi-item outcomes — use to-epic.
    0
    installs
  11. ▌
    To Product · beeltec bundle
    Run the whole delivery flow unattended from a PRD or plan to accepted primary-branch state, answering every owner gate as owner-proxy. Not for interactive shaping (use $discuss) or planning one outcome (use $to-epic).
    0
    installs
  12. ▌
    Implement · beeltec bundle
    Execute one ready backlog work item or Epic serially on its sole acceptance branch through claim, implementation, review, acceptance, and archival. Use with an explicit WORK-NNN, EPIC-NNN, backlog path, or unambiguous conversational selection.
    0
    installs
  13. ▌
    To Guidance · beeltec bundle
    Owner entry point that runs guidance under one standing approval for the named subjects. Use when asked to persist or refresh adopted technology or standards guidance.
    0
    installs
  14. ▌
    Codex Subagent · beeltec bundle
    Delegate a coding or implementation task to a nested Codex CLI agent through unattended, workspace-scoped `codex exec`. For non-Codex harnesses (Claude Code, OpenCode) only — never invoke from Codex itself. Use only when the user explicitly asks to use or delegate to a Codex subagent — not merely because a task involves code.
    0
    installs
  15. ▌
    Code Review · beeltec bundle
    Review changes since a fixed point on Standards and Spec axes with risk-tiered agents. Use for backlog-backed branches, PRs, work in progress, or Epic closure.
    0
    installs
  16. ▌
    Setup Project · beeltec bundle
    Initialize or safely upgrade a project's wiki, backlog, validation, and agent instructions; back-fill a foundation wiki on brownfield repositories. Use when creating or upgrading project governance.
    0
    installs
  17. ▌
    Bump Version · beeltec
    Bump a project version, choosing patch/minor/major increments, updating version files, generating changelog entries, and creating a release commit.
    0
    installs
  18. ▌
    Elementor Content · beeltec bundle
    Create, inspect, update, migrate, import, or delete Elementor content in exported JSON templates or WordPress post metadata via WP-CLI. Use for Elementor pages, library and Pro Theme Builder templates, containers, legacy sections/columns, widgets, responsive settings, global styles, and display conditions.
    0
    installs
  19. ▌
    Maestro E2e Testing · beeltec bundle
    Write, run, and debug Maestro E2E tests for mobile apps. Use for end-to-end testing, UI automation, test flows, smoke or regression tests, Maestro project setup, or Expo EAS Workflow integration.
    0
    installs
  20. ▌
    Parallel Execution · beeltec bundle
    Coordinate bounded parallel read-only work or independent verification processes for another delivery skill. Use only after a caller identifies at least two independent units; never for repository mutations or as an implementation entry point.
    0
    installs
  21. ▌
    Implement With Subagents · beeltec bundle
    Execute explicit ready Epics or work-item sets with fresh implementation subagents, one writer at a time on the sole acceptance branch, and manager-owned acceptance.
    0
    installs
  22. ▌
    Create Conventional Branch · beeltec bundle
    Enforce one local acceptance branch and its Conventional Branch lifecycle. Automatic only for $implement or $implement-with-subagents, or an explicit branch or PR request — never for planning, discussion, wiki, or research.
    0
    installs