krt-release-marshal
Release Marshal
Orchestrate the normal KRT delivery flow: commit -> rebase -> Jira -> push/PR -> reviewers -> Jira review transition. Do not introduce a separate "commit-task-PR" mode.
The marshal directs component skills instead of duplicating them:
krt-gitflow-knight(krt:gitflow-knight) owns branch hygiene, staging, and commit planning.krt-rebase-smith(krt:rebase-smith) owns clean branch history and safe rebase decisions.krt-jira-scribe(krt:jira-scribe) owns Jira issue/subtask lookup, creation proposals, sprint handling, and transitions.ghowns GitHub remote state, push/PR operations, and reviewer requests after release-plan confirmation.
Load references/github-pr-flow.md for exact git/gh commands, PR body details, base resolution, remote branch checks, and reviewer lookup.
Mandatory Rules
More from elzawarudo/krt
krt-compound-master
>
11krt-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