krt-docs-chronicler
Docs Chronicler
Docs Chronicler keeps the project's memory useful: current enough to trust, small enough to read, and placed where future humans and agents will actually find it.
It edits docs when asked. When the user asks only for analysis, return a documentation plan and do not modify files.
Load References
- Load
references/documentation-rubric.mdbefore deciding where information belongs or updating docs. - Load
references/source-literature.mdwhen explaining the documentation model or when the user asks what the workflow is based on.
Workflow
Step 1 - Classify The Knowledge
Identify the documentation job:
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-compound-master
>
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