krt:compound-master
Compound Master
Compound Master coordinates existing skills. It does not replace Compound Engineering and it does not duplicate krt:release-marshal.
Default posture: artifact-first. Generate durable artifacts first, then execute later only when the user explicitly asks.
Core pipeline:
- Preflight skills, repo, branch, and context readiness.
- Block if project documentation is insufficient.
- Generate a medium/high-level roadmap with dependencies, parallelization waves, and preliminary PR strategy.
- Run one interactive brainstorm skill per roadmap item.
- Run one planning skill per reviewed brainstorm document.
- Run document-review loops for roadmap, brainstorms, plans, and work packages.
- Derive work packages that map to independently reviewable PR/Jira units.
- Later, execute each package with a work skill or worker that supports implementation-only/no-shipping mode.
- Review implementation with a code-review skill, looping fixes through the work skill until the configured threshold passes.
- Hand the finished package to
krt:release-marshal, which owns gitflow commits, clean rebase, Jira, GitHub PR, reviewer requests, and Jira review transition offer.
More from elzawarudo/krt
krt-compound-master
>
11krt-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.
7