krt-compound-master
Compound Master
Compound Master coordinates existing skills. It does not replace Compound Engineering and it does not duplicate krt-release-marshal (krt:release-marshal in alias-friendly runtimes).
Default posture: artifact-first after discovery. Generate durable artifacts from explicit context and user decisions; execute later only when the user explicitly asks or mode:full reaches its execution gate. The brainstorm step is the main product-discovery gate, not a paperwork shortcut.
Core pipeline:
More from elzawarudo/krt
krt-release-marshal
Orchestrate the full delivery flow for the current project repository: direct krt-gitflow-knight for clean commits, krt-rebase-smith for clean branch history, krt-jira-scribe for Jira Server/Data Center issue work, then open a GitHub pull request with a factual body and Jira link. Use when the user asks to create/open a PR, prepare a pull request, ship current work, publish branch changes for review, or run the full gitflow + rebase + Jira + PR workflow. Runtime aliases may expose this as krt:release-marshal.
10krt-gitflow-knight
>
10krt-rebase-smith
>
8krt-jira-scribe
Manages Jira Server/Data Center issues on a Spanish-language instance. Verifies existing global issues and subtasks, checks whether new work belongs under an existing parent, proposes Spanish issue/subtask creation when missing, handles active sprint placement, and manages Spanish transitions. Runtime aliases may expose this as krt:jira-scribe.
8krt-ci-questor
Investigate CI/CD failures and produce concise cause reports. Use when a user asks why a GitHub Actions, GitLab CI, CircleCI, Jenkins, or other pipeline failed; needs log triage, flaky-test assessment, runner/dependency/config diagnosis, failed-check summaries, rerun guidance, or a simple report explaining what happened and what to do next. Runtime aliases may expose this as krt:ci-questor.
7krt-harness-wise
Build or review a compact, architecture-aware coding harness before implementation. Use when a user asks to prepare a coding agent before work, map task-relevant project structure, summarize repository conventions, curate context, reduce token waste, select relevant skills, review an existing harness, audit skill coverage, trim documentation context, or avoid premature coding on feature, bugfix, refactor, migration, integration, testing, documentation, security, or architecture work. Runtime aliases may expose this as krt:harness-wise.
7